Differences

This shows you the differences between two versions of the page.

--- products:settings [2017/08/02 17:59]
Andreas Breitschopp
+++ products:settings [2017/11/02 18:08] (current)
Andreas Breitschopp ↷ Links adapted because of a move operation
@@ Line 106: / Line 106: @@
 ==== Position ====
-These settings are related to the [[features:position]] module.
+These settings are related to the [[products:approach-training]] module.
 === General ===
@@ Line 118: / Line 118: @@
 ==== Conditions ====
-These settings are related to the [[features:conditions]] module.
+These settings are related to the [[products:conditions]] module.
 === Weather Engine ===
@@ Line 124: / Line 124: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/conditions-weather-engine.png?nolink|}}
-Let FS-FlightControl know here which software is used as weather engine to ensure all features of the [[features:conditions]] module work properly.
+Let FS-FlightControl know here which software is used as weather engine to ensure all features of the [[products:conditions]] module work properly.
-:i: Note: For Active Sky additional parameters need to be entered in the [[features:settings#third_party|Third Party]] settings first.
+:i: Note: For Active Sky additional parameters need to be entered in the [[products:settings#third_party|Third Party]] settings first.
 ==== Third Party ====
@@ Line 136: / Line 136: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-prosim.png?nolink|}}
-The host or IP as well as the port that should be used to connect to ProSim can be entered here. The ProSim connection then can be used in the [[features:flight-plan]] and [[features:failures]] modules.
+The host or IP as well as the port that should be used to connect to ProSim can be entered here. The ProSim connection then can be used in the [[products:flight-plan]] and [[products:failures]] modules.
 === AST ===
@@ Line 142: / Line 142: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-ast.png?nolink|}}
-The host or IP as well as the port that should be used to connect to AST (Aircraft Simulation Technology) can be entered here. The AST connection then can be used in the [[features:failures]] module.
+The host or IP as well as the port that should be used to connect to AST (Aircraft Simulation Technology) can be entered here. The AST connection then can be used in the [[products:failures]] module.
 === Project Magenta ===
@@ Line 148: / Line 148: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-project-magenta.png?nolink|}}
-The path to the ''NetDir'' of Project Magenta can be entered here. The Project Magenta connection then can be used in the [[features:flight-plan]] module; the [[features:failures]] module uses FSUIPC to connect to Project Magenta.
+The path to the ''NetDir'' of Project Magenta can be entered here. The Project Magenta connection then can be used in the [[products:flight-plan]] module; the [[products:failures]] module uses FSUIPC to connect to Project Magenta.
 === Flight Sim Labs ===
@@ Line 154: / Line 154: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-flight-sim-labs.png?nolink|}}
-The path to the ''FSLabs'' directory of Flight Sim Labs below the flight simulator directory can be entered here. The direct Flight Sim Labs connection then can be used in the [[features:flight-plan]] module.
+The path to the ''FSLabs'' directory of Flight Sim Labs below the flight simulator directory can be entered here. The direct Flight Sim Labs connection then can be used in the [[products:flight-plan]] module.
 === Brunner Elektronik ===
@@ Line 160: / Line 160: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-brunner-elektronik.png?nolink|}}
-The host or IP as well as the TCP port that should be used to connect to the ''CLS2Sim'' software by Brunner Elektronik can be entered here. The Brunner Elektronik connection then can be used in the [[features:motion]] module.
+The host or IP as well as the TCP port that should be used to connect to the ''CLS2Sim'' software by Brunner Elektronik can be entered here. The Brunner Elektronik connection then can be used in the [[products:motion]] module.
 :i: Note: ''CLS2Sim'' version v3.20.0 or newer is required.
@@ Line 170: / Line 170: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-active-sky.png?nolink|}}
-The host or IP as well as the port that should be used to connect to Active Sky 16 (SP1 required) can be entered here. The Active Sky connection then can be used in the [[features:conditions]] module.
+The host or IP as well as the port that should be used to connect to Active Sky 16 (SP1 required) can be entered here. The Active Sky connection then can be used in the [[products:conditions]] module.
 === PFPX ===
@@ Line 176: / Line 176: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-pfpx.png?nolink|}}
-You can enter the path to the PFPX documents directory here. The PFPX connection then can be used in the [[features:flight-plan]] module.
+You can enter the path to the PFPX documents directory here. The PFPX connection then can be used in the [[products:flight-plan]] module.
 === Aerosoft Airbus ===
@@ Line 182: / Line 182: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-aerosoft-airbus.png?nolink|}}
-Now you can enter the path to the Aerosoft Airbus documents directory (also the older Extended Version is supported) here. The Aerosoft Airbus connection then can be used in the [[features:flight-plan]] module.
+Now you can enter the path to the Aerosoft Airbus documents directory (also the older Extended Version is supported) here. The Aerosoft Airbus connection then can be used in the [[products:flight-plan]] module.
 === Wilco Airbus ===
@@ Line 188: / Line 188: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-wilco-airbus.png?nolink|}}
-You can enter the path to the Wilco/FeelThere Airbus directory here. The Wilco Airbus connection then can be used in the [[features:flight-plan]] module.
+You can enter the path to the Wilco/FeelThere Airbus directory here. The Wilco Airbus connection then can be used in the [[products:flight-plan]] module.
 === Mindstar ===
@@ Line 194: / Line 194: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-mindstar.png?nolink|}}
-You can enter the path to the Mindstar ''G1000.ini'' file here. The Mindstar connection then can be used in the [[features:failures]] module.
+You can enter the path to the Mindstar ''G1000.ini'' file here. The Mindstar connection then can be used in the [[products:failures]] module.
 Additionally the offset for the SimConnect event IDs need to be specified as hex value. Starting from this ID the SimConnect events will be assigned to the Mindstar G1000 failures.
@@ Line 202: / Line 202: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-flight1.png?nolink|}}
-The host or IP as well as the port that should be used to connect to Flight1 VISPRO flight simulator plug-in can be entered here. The Flight1 connection then can be used in the [[features:failures]] module.
+The host or IP as well as the port that should be used to connect to Flight1 VISPRO flight simulator plug-in can be entered here. The Flight1 connection then can be used in the [[products:failures]] module.
 :i: Note: To be able to trigger the Flight1 G1000 failures from FS-FlightControl not only the Flight1 G1000 plug-in needs to be installed in flight simulator, but also the Flight1 VISPRO plug-in.
@@ Line 236: / Line 236: @@
 ==== Position ====
-These settings are related to the [[features:position]] module.
+These settings are related to the [[products:approach-training]] module.
 === Final Position ===
@@ Line 280: / Line 280: @@
 ==== Map Colors ====
-These settings are related to the [[features:map]] module.
+These settings are related to the [[products:moving-map]] module.
 === Colors and Text Settings ===
@@ Line 325: / Line 325: @@
 ==== Map Other ====
-These settings are related to the [[features:map]] module.
+These settings are related to the [[products:moving-map]] module.
 === Auto Zoom ===
@@ Line 331: / Line 331: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/map-auto-zoom.png?nolink|}}
-The [[features:map]] module also features an auto zoom function which will zoom the map in and out according to the current aircraft altitude.
+The [[products:moving-map]] module also features an auto zoom function which will zoom the map in and out according to the current aircraft altitude.
 You can configure this feature here by first entering the maximum zoom level (fully zoomed in) that should be reached if the aircraft is below the entered altitude above ground.
@@ Line 350: / Line 350: @@
 Additionally so called afterglows - dots behind the aircraft - can be enabled or disabled for user and/or AI aircraft. In this case you can enter an interval as well as the number of dots that should be displayed.
-=== Reposition ===
-{{https://www.fs-flightcontrol.com/img/manual/features/settings/map-reposition.png?nolink|}}
-In this section you can define if certain map features are automatically turned on after the map reposition function was used.
 === Compass Rose ===
@@ Line 373: / Line 367: @@
 ==== Pushback ====
-These settings are related to the [[features:pushback]] module.
+These settings are related to the [[products:pushback]] module.
 === Speed Options ===
@@ Line 383: / Line 377: @@
 ==== Failures ====
-These settings are related to the [[features:failures]] module.
+These settings are related to the [[products:failures]] module.
 === Failures Source ===
@@ Line 389: / Line 383: @@
 {{https://www.fs-flightcontrol.com/img/manual/features/settings/failures-source.png?nolink|}}
-Here you can choose the source of the failures that are displayed in the [[features:failures]] module.
+Here you can choose the source of the failures that are displayed in the [[products:failures]] module.
-:i: Note: For some options additional parameters need to be entered in the [[features:settings#third_party|Third Party]] settings first.
+:i: Note: For some options additional parameters need to be entered in the [[products:settings#third_party|Third Party]] settings first.
 ==== Aircraft ====
-These settings are related to the [[features:aircraft]] module.
+These settings are related to the [[products:aircraft]] module.
 === Aircraft Warnings ===
@@ Line 409: / Line 403: @@
 Additionally you can define maximum speeds below certain altitudes above mean sea level (MSL).
-These settings are used to change the color of the corresponding value to red on the [[features:aircraft]] module and also to shown warning indicators when exporting graph data to Google Earth on the [[features:statistics]] module.
+These settings are used to change the color of the corresponding value to red on the [[products:aircraft]] module and also to shown warning indicators when exporting graph data to Google Earth on the [[products:flight-recorder]] module.
 === Aircraft-Specific Options ===
@@ Line 417: / Line 411: @@
 For some third-party add-ons there are some additional options available. You can enable this support here.
-:i: Note: Some third-party add-ons require additional parameters to be entered in the [[features:settings#third_party|Third Party]] settings first.
+:i: Note: Some third-party add-ons require additional parameters to be entered in the [[products:settings#third_party|Third Party]] settings first.
 === Other ===
@@ Line 427: / Line 421: @@
 ==== Statistics ====
-These settings are related to the [[features:statistics]] module.
+These settings are related to the [[products:flight-recorder]] module.
 === Google Earth Export ===
@@ Line 445: / Line 439: @@
 ==== Position ====
-These settings are related to the [[features:position]] module.
+These settings are related to the [[products:approach-training]] module.
 === General ===
@@ Line 455: / Line 449: @@
 First choose if position freeze or pause should be enabled after aircraft move.
-Additionally you can define if the program should automatically switch to the [[features:map]] module after a position change respectively to the [[features:statistics]] module when an approach is started.
+Additionally you can define if the program should automatically switch to the [[products:moving-map]] module after a position change respectively to the [[products:flight-recorder]] module when an approach is started.
 === Flight Situation Presets ===
@@ Line 465: / Line 459: @@
 ==== Map ====
-These settings are related to the [[features:map]] module.
+These settings are related to the [[products:moving-map]] module.
 === Data Update Rate ===
@@ Line 535: / Line 529: @@
 ==== Conditions ====
-These settings are related to the [[features:conditions]] module.
+These settings are related to the [[products:conditions]] module.
 === Real-Time Weather Source ===
@@ Line 555: / Line 549: @@
 ==== Failures ====
-These settings are related to the [[features:failures]] module.
+These settings are related to the [[products:failures]] module.
 === Color Settings ===
@@ Line 573: / Line 567: @@
 ==== Statistics ====
-These settings are related to the [[features:statistics]] module.
+These settings are related to the [[products:flight-recorder]] module.
 === Color Settings ===
@@ Line 611: / Line 605: @@
 ==== Network ====
-These settings are related to the [[features:network]] module.
+These settings are related to the [[products:network]] module.
 === FS-FlightControl Client ===
@@ Line 768: / Line 762: @@
 Furthermore you have the option here to activate an additional confirmation message before the program is really closed - in case of accidental clicks on the ''Exit'' button.
+=== Online Network Status URLs ===
+{{https://www.fs-flightcontrol.com/img/manual/features/settings/other-online-network-status-urls.png?nolink|}}
+Here you can change the URLs where FS-FlightControl gets the status updates for VATSIM, IVAO and PilotEdge from.
+This might be useful if you operate your own multi-player server. If you use, for example, the VATSIM format for providing online client information, you can inject this information into FS-FlightControl by pointing the VATSIM URL here to your own server.
+You can also reset these URLs to their defaults.
 === Color Settings ===
@@ Line 776: / Line 780: @@
 You can also use the button ''Reset to Defaults'' to revert all your color changes.
+=== Unpause Delay ===
+{{https://www.fs-flightcontrol.com/img/manual/features/settings/other-unpause-delay.png?nolink|}}
+You can configure the unpause delay to your needs here.
+This will be used to slowly accelerate your aircraft after the simulator was unpaused through FS-FlightControl.
+:i: Note: This option has no effect if you are connected to X-Plane.

User Tools

Site Tools

Differences

Page Tools