Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
other:command-line-parameters [2021/09/30 18:44] Andreas Breitschopp |
other:command-line-parameters [2024/02/09 19:53] (current) Andreas Breitschopp |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| * ''/dataDirectory={path}''((This command line parameter only works with the commercial license of FS-FlightControl.)): Allows specifying a custom data directory. Please carefully read the additional information about this parameter [[other:command-line-parameters#custom_data_directory|below]] first. | * ''/dataDirectory={path}''((This command line parameter only works with the commercial license of FS-FlightControl.)): Allows specifying a custom data directory. Please carefully read the additional information about this parameter [[other:command-line-parameters#custom_data_directory|below]] first. | ||
| * ''/doNotSaveSettings''((This command line parameter only works with the commercial license of FS-FlightControl.)): If used settings can be changed by the user, but changes will be discarded on program close. | * ''/doNotSaveSettings''((This command line parameter only works with the commercial license of FS-FlightControl.)): If used settings can be changed by the user, but changes will be discarded on program close. | ||
| + | * ''/useSimulator={simulator_name}'': Start FS-FlightControl with a specific simulator by specifying its name here (surrounding quotes may be used if name contains spaces). | ||
| * ''/suppressFontScalingWarning'': If font scaling is enabled on Windows 7 or older an incompatibility warning is displayed on every program start. To suppress this warning at own risk you can use this command line parameter. | * ''/suppressFontScalingWarning'': If font scaling is enabled on Windows 7 or older an incompatibility warning is displayed on every program start. To suppress this warning at own risk you can use this command line parameter. | ||
| Line 18: | Line 19: | ||
| The command line parameter ''/dataDirectory={path}'' allows specifying a custom data directory defined with the placeholder ''{path}'' (surrounding quotes may be used if path contains spaces). | The command line parameter ''/dataDirectory={path}'' allows specifying a custom data directory defined with the placeholder ''{path}'' (surrounding quotes may be used if path contains spaces). | ||
| - | If such a custom data directory is defined FS-FlightControl no longer enforces single instance use and thus allows to start multiple FS-FlightControl instances on the same computer. This is only very rarely needed, but can make sense if a parallel connection to multiple simulators is needed from one instructor seat. | + | If such a custom data directory is defined FS-FlightControl allows to start multiple application instances on the same computer. This is only very rarely needed, but can make sense if in parallel a connection to multiple simulators is needed from one instructor seat. |
| - | :i: Note: It is very important to remember that every instance of FS-FlightControl requires a separate FS-FlightControl license! | + | :i: Note: It is very important to remember that every instance of FS-FlightControl requires a separate license! |
| - | For that reason the custom data directory defined is part of the hardware key during activation. | + | For that reason the custom data directory defined is part of the hardware key during license activation. |
| - | As a result you cannot just set or change such a custom data directory, but before every change or setting it the first time (or removing the parameter again) you are required to first deactivate your license in [[features/info#license_information|Info]] module. Not doing so will invalidate your license with the need to contact us for a manually license reset. | + | As a result you cannot just set or change such a custom data directory, but before every change or setting it the first time (or removing the parameter again) you are required to first deactivate your license in the [[features/info#license_information|Info]] module. Not doing so will invalidate your license with the need to contact us for a manually license reset. |
| + | |||
| + | So before enabling, disabling or changing the custom data directory please follow these steps: | ||
| + | |||
| + | - Start FS-FlightControl without ''/dataDirectory'' parameter (or the previously used one) and deactivate your license in the [[features/info#license_information|Info]] module. | ||
| + | - Add the (new) command line parameter ''/dataDirectory'' with the desired ''{path}'' to the application shortcut. | ||
| + | - Ensure that navigation data is present in the ''{path}\NavData'' sub directory: You can either copy this ''NavData'' directory from the default FS-FlightControl data directory (normally ''C:\Users\[UserName]\AppData\Roaming\FS-FlightControl\NavData'') or just use a fresh navigation data copy from Navigraph or NavDataPro. | ||
| + | - Start FS-FlightControl now using that shortcut and make sure to use a commercial license during license activation. | ||
| + | |||
| + | :i: Note: Every parallel instance of FS-FlightControl has to be started with a different custom data directory. | ||
| + | |||
| + | The same application executable ''FS-FlightControl.exe'' can be started multiple times. So while the custom data directory needs to be different for every instance, the application itself only has to be installed once on the same computer. | ||