# Legacy FLT File Properties On this page you can find references to the sections and parameters that are either considered as or . Sections and parameterd flagged as legacy can still be included in your aircraft as long as the aircraft is setup with the corresponding legacy system, however attempts should be made to update to use the newer systems as support for legacy items may be discontinued in the future. Items flagged as depreacted should not be used at all.     ### `[Hydraulic Parameters.N.i]` **NOTE** : This section is only required for aircraft using the legacy `[HYDRAULIC_SYSTEM]`. Defines one or more hydraulic system. Systems are defined from *N* upwards - starting from 0 - where each one first corresponds to an engine pump, then the subsequent ones correspond to an electric pump. For example if the aircraft has 2 engines and two electric pumps you would have the following sections: ``` codeblock [Hydraulic Parameters.0.0] [Hydraulic Parameters.1.0] [Hydraulic Parameters.2.0] [Hydraulic Parameters.3.0] ``` The second section value (*i*) corresponds to the aircraft number (0 for the user aircraft).   The available parameters are:   {{< table-wrapper >}} | Parameter | Description | Type | Required | |---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|:--------:| | `HydraulicPressure` | Sets the Hydraulic pressure (in {{< glossterm >}}psf{{< /glossterm >}}) of the hydraulic system `N`. When multiple systems are defined, engine pumps should be first then electrical pumps. | Float | No | {{< /table-wrapper >}}     ### `[Fuel.N]` {{< callout context="note" title="NOTE" icon="outline/bulb" >}} This section is only required for aircraft using legacy `[FUEL]`.There will be one fuel entry for each aircraft. The available parameters are: {{< /callout >}}   Parameter Description Type Required `TankSelector` Tank selector for the left engine(s), or for a single-engine aircraft Integer: 1. Off 2. All 3. Left 4. Right 5. Left Aux 6. Right Aux 7. Left Main 8. Right Main 9. Center 10. Crossfeed Left to Right 11. Crossfeed Right to Left 12. Center 2 13. Center 3 14. Drop 1 15. Drop 2 16. Right Tip 17. Left Tip 18. Crossfeed 19. Both 20. Drop All Yes `TankSelector1` Tank selector for the right engine(s). Same range of options as `TankSelector`. This entry will be present, but ignored, for a single-engine aircraft. Yes `Center` Percentage of fuel in tank. These parameters are only required if you are using the simplified fuel system as setup using the `[FUEL]` section for the aircraft. Float Yes `Center 2` Percentage of fuel in tank. Float Yes `Center 3` Percentage of fuel in tank. Float Yes `LeftMain` Percentage of fuel in tank. Float Yes `RightMain` Percentage of fuel in tank. Float Yes `LeftAux` Percentage of fuel in tank. Float Yes `RightAux` Percentage of fuel in tank. Float Yes `LeftTip` Percentage of fuel in tank. Float Yes `RightTip` Percentage of fuel in tank. Float Yes `External 1` Percentage of fuel in tank. Float Yes `External 2` Percentage of fuel in tank. Float Yes     ### `[ResourcePath]` If the saved flight is a mission, this will be the path to the mission resources, such as the audio and briefings files. If it is not a mission it will reference the flights\(other\)folder. Note that the path is relative to the install location for the application, and that resource paths must be sub-folders within the install location.   The available parameters are:   {{< table-wrapper >}} | Parameter | Description | Type | Required | |------------------------------------------------------------|-----------------------|--------|:--------:| | `Path` | The path to the files | String | Yes | {{< /table-wrapper >}}     ### `[Window.N]` This section deals with currently opened windows, where *N* is the window being referenced. Windows should always be numbered from 1 and there should always be at least 1 Window section. The available parameters are:   {{< table-wrapper >}} | Parameter | Description | Type | Required | |-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|:--------:| | `Order` | Set to 0 if the main window is in focus, or the number of the window if another is in focus. | Integer | Yes | | `Active` | Set to `True` if this is the active window or `False` otherwise. | Boolean | Yes | | `Undocked` | Set to `True` if the window has been undocked or `False` otherwise. If set to `True`, the window will be located at `UndocCoords`. | Boolean | Yes | | `Maximized` | Set to `True` if the window is maximized, or `False` otherwise. When `True`, this will override screen co-ordinates. | Boolean | Yes | | `ScreenUniCoords` | The current screen co-ordinates of the window. See the note on [Universal Screen Co-ordinates](flt-additional-information/#USC). The data for this parameter should be in a 4 value comma separated list, eg: `ScreenUniCoords=2968, 811, 4304, 3702` | 4 Floats | Yes | | `UndocCoords` | The co-ordinates of the window if it has been undocked. See the note on [Universal Screen Co-ordinates](flt-additional-information/#USC). The data for this parameter should be in a 4 value comma separated list, eg: `UndocCoords=0, 0, 0, 0` | 4 Floats | Yes | | `CurrentCamera` | The {{< glossterm >}}guid{{< /glossterm >}} of the current camera (this will match one of the GUIDs in a `[Camera.N.i]` entry). Note that if a view option such as "Top Down View" is selected, then the current camera will be the GUID of one of the camera entries down in the list. | String | Yes | | `InstanceN` | Optional entries, counted from 1. If the camera is pointing at - or is inside - an AI controlled aircraft, then the type and tail number of that aircraft is stored here. For example: `Instance1=C208B Grand Caravan` | String | No | {{< /table-wrapper >}}     ### `[Panels]` This section has the general panel control options. The available parameters are:   {{< table-wrapper >}} | Parameter | Description | Type | Required | |--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|:--------:| | `Panel.On` | `True` if the main panel is visible, either in 2D cockpit or Virtual Cockpit view mode, or `False` otherwise. | Boolean | Yes | | `HUD.On` | If the `panel.on` setting is `False`, and this setting is `True`, then the mini panel is visible. If both `panel.on` and `hud.on` are `False`, then no panel is visible. | Boolean | Yes | {{< /table-wrapper >}}     ### `[Multiplayer]` This section controls the multiplayer air-traffic in-sim for a flight. The available parameters are:   Parameter Description Type Required `Status` No longer used by the simulation. Bool Yes `RadiusAlpha` Float No `RadiusCreate` Float No `RadiusRemove` Float No     ### `[AirTraffic]` This section controls the live air traffic in-sim for a flight. The available parameters are:   Parameter Description Type Required `Status` No longer used by the simulation. Bool Yes `RadiusAlpha` Float No `RadiusCreate` Float No `RadiusRemove` Float No