Differences

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

--- features:settings [2021/05/16 10:07]
Andreas Breitschopp
+++ features:settings [2024/12/11 10:34] (current)
Andreas Breitschopp
@@ Line 105: / Line 105: @@
 But if the automatic detection does not work for any reason, you can configure the connection manually here.
+:i: Note: The port is almost always the default port ''49000'', only change it if there is a specific reason for it.
 ==== Position ====
@@ Line 147: / Line 149: @@
 It is also possible to reduce the aircraft that are available to the user and show only relevant ones.
+Furthermore, you can force an [[dialogs:select-aircraft|aircraft selection dialog]] on program start.
 ==== Motion ====
@@ Line 183: / Line 187: @@
 The path to the ''A320FMGS'' directory of JeeHell can be entered here. The JeeHell connection then can be used in the [[features:flight-plan]] module; the [[features:failures]] and [[features:aircraft]] modules use FSUIPC to connect to JeeHell.
+:i: Note: Please make sure that JeeHell Hardware Interface is started. If FS-FlightControl runs on a different computer than JeeHell itself, you also need WideFS installed.
 === AST ===
@@ Line 206: / Line 212: @@
 {{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 P3D or XP can be entered here. The Active Sky connection then can be used in the [[features:conditions]] module.
+:i: Note: The old ''ASP4'' version is not fully supported as certain API features are missing. Please use Active Sky P3D (for Prepar3D) or XP (for X-Plane).
 === Aerosoft Airbus ===
@@ Line 227: / Line 235: @@
 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.
+=== EFIS Fly ===
+{{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-efis-fly.png?nolink|}}
+You can enter the path to the EFIS Fly ''G1000.panels.ini'' file here. The EFIS Fly connection then can be used in the [[features: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 EFIS Fly G1000 failures.
 === Flight1 ===
@@ Line 505: / Line 521: @@
 ^ Interface           ^ Reference                                                                                              ^
-| SimConnect Event    | [[http://www.prepar3d.com/SDKv5/sdk/references/variables/event_ids.html|Lockheed Martin Website]] for Prepar3D, [[https://docs.microsoft.com/en-us/previous-versions/microsoft-esp/cc526980(v=msdn.10)|Microsoft Website]] for FSX                                        |
+| SimConnect Event    | Lockheed Martin Website for [[http://www.prepar3d.com/SDKv5/sdk/references/variables/event_ids.html|Prepar3D]], Microsoft Website for [[https://docs.microsoft.com/en-us/previous-versions/microsoft-esp/cc526980(v=msdn.10)|FSX]] and [[https://docs.flightsimulator.com/html/Programming_Tools/Event_IDs/Event_IDs.htm|FS2020]]                             |
-| SimConnect Variable | [[http://www.prepar3d.com/SDKv5/sdk/references/variables/simulation_variables.html|Lockheed Martin Website]] for Prepar3D, [[https://docs.microsoft.com/en-us/previous-versions/microsoft-esp/cc526981(v=msdn.10)|Microsoft Website]] for FSX                                          |
+| SimConnect Variable | Lockheed Martin Website for [[http://www.prepar3d.com/SDKv5/sdk/references/variables/simulation_variables.html|Prepar3D]], Microsoft Website for [[https://docs.microsoft.com/en-us/previous-versions/microsoft-esp/cc526981(v=msdn.10)|FSX]] and [[https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Simulation_Variables.htm|FS2020]]                             |
 | X-Plane Command     | ''Commands.txt'' in ''Resources\plugins'' below X-Plane installation folder                            |
 | X-Plane DataRef     | ''DataRefs.txt'' in ''Resources\plugins'' below X-Plane installation folder                            |
@@ Line 539: / Line 555: @@
 === Use Third Party Aircraft Options ===
-{{https://www.fs-flightcontrol.com/img/manual/features/settings/third-party-aircraft-options.png?nolink|}}
+{{https://www.fs-flightcontrol.com/img/manual/features/settings/aircraft-third-party.png?nolink|}}
 You can choose which third party aircraft options should be used.
@@ Line 564: / Line 580: @@
 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.
+FS-FlightControl calculates the runway take-off position internally as the location of the very end of the runway plus 50 m towards the runway center. But optionally you can change this to use a defined starting position of the scenery (if available). As these starting positions are sometimes located at the holding point instead, this option is turned off, by default.
 === Flight Situation Presets ===
@@ Line 633: / Line 651: @@
 | {atc_airport_departure} | Departure airport as filed.                                                                |      | X1 | X      |
 | {atc_airport_arrival}   | Arrival airport as filed.                                                                  |      | X1 | X      |
+| {atc_airports}          | ''{atc_airport_departure} → {atc_airport_arrival}'', if both variables available.          |      | X1 | X      |
 | {atc_flight_rules}      | Flight rules as filed.                                                                     |      | X1 | X      |
 | {atc_airport_alternate} | Alternate airport as filed.                                                                |      |    | X      |
@@ Line 658: / Line 677: @@
 Additionally you can disable the automatic re-center of the map and clear aircraft trace (if enabled) after the aircraft position has been changed from the flight simulator itself (after there was a crash, for example).
+By default, true bearings are shown when the measure function is used. This can be changed to magnetic bearings here.
 There is also an option to enable or disable the display of scenery source files in the [[features/map#map_information|map information]] dialog: This might help with identifying issues during database build.
 If you do not like to see other aircraft on the map that are on ground while you are flying you can hide ground traffic above a certain altitude above ground level.
+=== Map Background Data Provider ===
+{{https://www.fs-flightcontrol.com/img/manual/features/settings/map-map-background-data-provider.png?nolink|}}
+You can select here either Bing Maps or OpenStreetMap as map background data provider.
+:i: Note: Please note that satellite map is only available with Bing Maps.
 === Online Networks ===
@@ Line 738: / Line 767: @@
 In this connection you can choose from NOAA (National Oceanic and Atmospheric Administration), VATSIM (Virtual Air Traffic Simulation), IVAO (International Virtual Aviation Organization) and PilotEdge.
+:i: Note: When Active Sky is used as weather engine for the active simulator this setting is ignored and always Active Sky itself used as real-time weather source.
 === Other ===
@@ Line 1208: / Line 1239: @@
 This will be used to slowly accelerate your aircraft after the simulator was unpaused through FS-FlightControl.
+To deactivate the unpause delay altogether just enter a ''0'' for both values.
 :i: Note: This option has no effect if you are connected to X-Plane.
@@ Line 1258: / Line 1291: @@
 If you would like to have also the altitude frozen, you can select this here.
+:i: Note: When X-Plane is used altitude is always frozen as well as it does not support freezing position only.

User Tools

Site Tools

Differences

Page Tools