Aircraft DAT File Variables
YSFlight Community Edition (YSCE), like YSFlight, uses a data file (.dat) that defines the performance and handling characteristics of an aircraft along with available weaponry and predefined viewpoints for the player. Specific information is assigned to DAT Variables (DATVARs) which is interpreted by YSCE. Many DATVARs are required in a DAT File, otherwise YSCE cannot properly understand the aircraft's properties. Other DATVARs are optional as YSCE will use default values if absolutely necessary for performance calculations.
This page will introduce new YSCE Users and Modders to the specifics of the DATVARs and how they need to be defined in the DAT file, however this page does not go into depth on how the performance and handling DATVARs are used by YSCE calculations.
A DAT Variable (DATVAR) is an eight-character alpha-numeric code (some exceptions) that defines a particular aspect of YSCE Aircraft. Depending on the DATVAR, different inputs of the correct data type and units are required to fully define the DATVAR. YSCE retains the legacy YSFlight DATVARs, even if no longer in use in order to maintain backwards compatibility with many older YSFlight Addons.
There are many DATVARs that require positional coordinates or a particular 3D angle to be defined.
When defining a position, YSCE expects the three pieces of positional information in the following order. This will be defined with length units, but the actual units will only be a factor if different units are used for different coordinates.
- Left/Right, Positive Right
- Up/Down, Positive Up
- Fore/Aft, Positive Forward
When defining a 3D Angle, YSCE expects three pieces of angle information in the following order with angular units:
- Rotation about Vertical Axis (Positive Left)
- Rotation about Horizon (Positive Up)
- Rotation about Fore-Aft Axis (Positive Left Roll)
There are some instances where YSCE requires a 3D vector to be defined. In these instances, YSCE will interpret the inputs to be a Unit Vector with the coordinates in the same order as the Position Coordinate Input. While YSCE will accept vectors with magnitudes other than 1, these are for the most part normalized and converted to a unit vector.
Many of the DATVARs defined in the stock aircraft DAT files will include a brief end-of-line comment explaining what the variable is used for. YSCE separates these comments from the rest of the DATVAR inputs by the "#" character. Anything after the "#" character in a DAT line is treated as comment. Some exceptions like the HRDPOINT DATVAR apply, so please review the specific DATVARs for any known issues.
Any line in the DAT File that beings with "REM" will be treated as a full line comment. Many modders will use this to add Modding instructions or credits to the top of a DAT File.
The last line in a DAT File should be "AUTOCALC" this is an instruction to YSCE to begin compiling the DATVARs in the Aircraft DAT File and calculating the performance characteristics of the aircraft.
This page organizes DATVARs into different categories based broadly speaking what the DATVAR is used for.
These DATVARs are used by YSCE in order to manage and sort aircraft and define basic expectations for performance and purpose.
The IDENTIFY DATVAR is a required for all Aircraft DAT files and provides the name of the aircraft as it should be displayed to the user in menus and in-game HUD circle overlays. This is YSCE's unique identifier for an aircraft, so when defining this variable, it should be completely unique. YSCE only recognizes the first 32 characters in the IDENTIFY string. If there are multiple aircraft where the IDENTIFY string is identical in the first 32 characters, YSCE will load the same aircraft with the same name it first encountered in all the air*.lst files combined.
While not required, it is highly Recommended to encapsulate the IDENTIFY string in quotation marks as shown in the examples below:
IDENTFIY "F-16C_FIGHTING_FALCON"
IDENTIFY "(HQP)A-4G_[RAAN/NO.805]"
A common practice to ensure a unique IDENTIFY string, even for common aircraft type/model/series and/or airline, is to use a unique Tag at the beginning to indicate the author or pack of origin. This serves a dual purpose as it makes searching for addons from a particular author or pack much easier.
The SUBSTNAM DATVAR is a recommended Aircraft DATVAR, and is highly Recommended for optimal user experience. This DATVAR is only used in server-play as a way for the addon author to define the IDENTIFY name of an alternate Aircraft to render in place of this Aircraft for any user that does not have this Aircraft installed. The name provided must be an exact match to another aircraft's IDENTIFY name.
SUBSTNAM "F-18C_HORNET"
Because most YSCE users do not uninstall the default aircraft that come with YSCE, these are the most common choices for use in the SUBSTNAM line as most users will have something representative of the missing aircraft to look at. Since YSCE does not have all possible aircraft types that might need a default replacement for the SUBSTNAM, most modders will choose something of similar size or type as the Aircraft they are creating. For example, since there is no default F-35 in YSCE, a modder releasing an F-35 aircraft might select the stock F-22 as a replacement since it is a stealth fighter aircraft, or perhaps the stock F-16 since it is a single-engine multi-role fighter aircraft.
The CATEGORY DATVAR is a required Aircraft DATVAR. The CATEGORY is used for two primary purposes:
- Filtering or limiting aircraft of similar types to appear in search results or simulations
- Defining general autopilot performance
The table below shows all of the available CATEGORY values and some of the common ways YSFlight and YSCE modders assign the CATEGORY options.
| CATEGORY | Typical uses |
|---|---|
| NORMAL | Most transport and cargo aircraft, whether civilian or military |
| FIGHTER | Jet or rocket powered Fighter and Fighter-Bomber aircraft |
| UTILITY | Helicopters |
| ATTACKER | Subsonic Attack aircraft |
| AEROBATIC | Airshow aircraft that don't fit into one of the above CATEGORY options |
| HEAVYBOMBER | Jet-powered dedicated bomber aircraft |
| TRAINER | Jet-powered trainer aircraft that should be more stable |
| WW2FIGHTER | Propeller-powered small combat aircraft |
| WW2ATTACKER | Propeller-powered attack or small bomber aircraft |
| WW2BOMBER | Larger multi-engine propeller bombers |
| WW2DIVEBOMBER | Rarely used outside of propeller-powered dive bombers |
The AIRCLASS DATVAR is not a required Aircraft DATVAR for airplanes, but is required for Helicopters. YSCE uses the Helicopter AIRCLASS to calculate certain ground and thrust characteristics unique to helicopters.
AIRCLASS AIRPLANE
AIRCLASS HELICOPTER
This section covers the DATVARs common between Jet and Propeller engines. The two engine models mostly use different DATVARs. YSCE only supports a single engine type for an aircraft and so only one set of DATVARs should appear in a DAT file.
The FUELMILI DATVAR is a required DATVAR for all aircraft. This defines the maximum fuel consumption (weight per second) when the jet engine is operating at 100% throttle without afterburner. For propeller aircraft this defines the maixmum fuel consumption (weight per second) when the propeller engine is operating at 100% throttle.
FUELMILI 5.0kg
FUELMILI 2lb
The THRSTREV is optional for all aircraft. This defines the percentage of the engine's thrust that can be reversed, as a decimal percent (0 to 1 representing 0 to 100%), when the reverse thrust command is engaged. YSCE will accept all numeric values but will bound the interpreted input to between 0 and 1. If this DATVAR is not included in the DAT File, there will be no reverse thrust for the aircraft.
THRSTREV 0.1
The AFTBURNR DATVAR is a required Aircraft DATVAR for aircraft with jet engines. When set to TRUE, it permits after-burning jet engine operation. When set to FALSE it keeps jet engines to non-after-burning operation. The general practice is to leave this set to FALSE for propeller aircraft.
AFTBURNR FALSE
AFTBURNR TURE
The THRAFTBN DATVAR is a required DATVAR for aircraft with after-burning jet engines (AFTBURNR TRUE). This defines the maximum thrust of the Jet Engine when operating at 100% Afterburner at sea level.
THRAFTBN 30.0t
THRAFTBN 5000lb
The THRMILIT DATVAR is a required DATVAR for aircraft with jet engines. This defines the maximum thrust of the Jet Engine when operating at 100% thrust without afterburner at sea level.
THRMILIT 15.0t
THRMILIT 2000lb
The FUELABRN DATVAR is a required DATVAR for aircraft with after-burning jet engines. This defines the fuel consumption (weight per second) when the jet engine is operating the afterburner. The fuel flow does not change with throttle, only when the afterburner is engaged.
FUELABRN 9.0kg
FUELABRN 10lb
While YSFlight has the REALPROP propeller engine model, this is being depreciated in YSCE. The basic (legacy YSFlight) Propeller engine model is the only one allowed for YSCE and uses the DATVARs in this section.
The PROPEFCY DATVAR is optional for propeller aircraft and should be excluded from DAT Files for jet engine aircraft. This variable defines the overall efficiency of the propeller as a decimal percent (0 to 1 representing 0 to 100%). If not defined in the DAT file, YSCE will use a default value of 0.7, or 70% efficient.
PROPEFCY 0.825
The PROPEFCY DATVAR is required for propeller aircraft and should be excluded from DAT Files for jet engine aircraft. This variable defines the rated power of a propeller engine. If an aircraft has multiple propeller engine, this variable should be the sum of all the engines rated powers.
PROPELLR 15000.0HP
PROPELLR 5000 J/s
The PROPVMIN DATVAR is optional for propeller aircraft and should be excluded from DAT Files for jet engine aircraft. This defines the speed at which will change the method for calculating propeller thrust. Below this speed, YSCE will use a static thrust model. Above this speed YSCE will account for the airspeed of the aircraft and how that influences thrust. If not defined, YSCE will assume a default 30 meters per second.
PROPVMIN 30kt
This section covers the DATVARs that control cockpit views, HUD, Alerts, and Instrument Panel.
The COCPITP DATVAR is required for all aircraft. This defines the location of Cockpit view position that the user will first see in the F1 View mode. This DATVAR requires three Float inputs with Length Units. It is permissible to mix and match Length Units for each input.
COCKPITP -0.553m 1.04m 27.08m
The COCKPITA DATVAR is optional for all aircraft. This defines the neutral angle for the Cockpit View. This is analogous to the angles defined in the EXCAMERA DATVAR line. If this DATVAR is not included in a DAT File, YSCE will default to an equivalent to "COCKPITA 0deg 0deg 0deg".
COCKPITA 0deg -3deg 0deg
The INSTPANL DATVAR is not required for any aircraft. If this DATVAR is included then YSCE will default to not showing the HUD and show the default Instrument Panel, an example of which is shown in the image below.
If a filepath to an .ist file is included after the INSTPAL DATVAR, then YSCE will use the custom defined instrument panel instead of the default instrument panel, as shown in the stock A6M5 Zero Aircraft Model, a screenshot of which is shown below.
INSTPANL
INSTPANL aircraft/a6m5.ist
A more detailed breakdown of the Cockpit Instrument (IST) file; how it is formatted and the type of instruments that YSCE supports, can be found at this page.
The ISPNLPOS DATVAR is recommended if an Instrument Panel is being used (INSTPANL included in DAT). This DATVAR defines the origin of the displayed instrument panel relative to the COCKPITP position. YSCE expects three floats with Length units.
ISPNLPOS 0m 1.03m 0.819348m
ISPNLPOS -0.502163m -0.818m 24.372308m
If an instrument panel is being used, but ISPNLPOS is not defined, YSCE will default to the equivalent of "ISPNLPOS 0.0m 0.0m 1.12m".
The ISPNLSCL DATVAR is optional if an Instrument Panel is being used (INSTPANL included in DAT). This DATVAR defines a scaling factor that should be applied to the instrument panel. If an instrument panel is defined but this DATVAR is not used, then YSCE will use the equivalent of "ISPNLSCL 1.00". This DATVAR takes a decimal percent, so 1.0 would equal 100 percent, 2.0 would be 200%, etc.
ISPNLSCL 0.38
If an instrument panel is being used, but ISPNLSCL is not defined in the DAT File, YSCE defaults to the equivalent of "ISPNLSCL 1.0".
The ISPNLATT DATVAR is optional if the Instrument Panel is being used (INSTPANL included in DAT). This DATVAR controls the rotation of the Instrument Panel about its origin, allowing the instrument panel to sit flush against an angled mesh face in the cockpit.
ISPNLATT 0deg -9.999828deg 0deg
The ISPNLHUD DATVAR is optional. It allows both the HUD and an instrument panel to be displayed at the same time if the variable is set to TRUE.
The EXCAMERA DATVAR is optional. It allows additional viewpoints to be defined for the player to cycle through by pressing F1 multiple times. There are four general pieces of information that needs to be defined.
- Name (Not used for anything in-game, only for DAT File clarity)
- Position
- Neutral view direction
- Inside or Outside the aircraft
EXCAMERA "CO-PILOT" 0.45m -0.65m 23.95m 0deg 0deg 0deg INSIDE
EXCAMERA "VTAIL" 0m 5.1m -20m 0deg 0deg 0deg OUTSIDE
| Location | What Happens |
|---|---|
| INSIDE | Inside the Cockpit, where the cockpit visual file will be rendered. |
| OUTSIDE | Outside the aircraft, where the cockpit visual file will NOT be rendered. |
| CABIN | Same as INSIDE, with Instrument Panel and HUD disabled. |
| NOHUD [1] | Disables the HUD for INSIDE or OUTSIDE options |
| NOINSTPANEL [1] | Disables the instrument panel for INSIDE or OUTSIDE options |
[1] These can be added to another option, but combined is the same as the CABIN option.
The SCRNCNTR DATVAR is not a required DATVAR for YSCE Aircraft. This DATVAR allows the modder to fix the center point of the screen so that the Instrument Panel or HUD does not shift it. The first value controls the horizontal position of the center and the second controls the vertical.
SCRNCNTR 0.0 0.5
The LOOKOFST DATVAR is not a required DATVAR for YSCE Aircraft. This DATVAR influences the F7 and F8 View Modes.
LOOKOFST 0m -0.661863m 1.293641m
Editor's Note: This DATVAR is not well understood and this section will be revisited when more is known and a better explanation can be provided.
The INITZOOM DATVAR is not a required DATVAR for YSCE Aircraft. This DATVAR defines the initial zoom state when switching to the Cockpit (F1) Viewpoint. If not defined in the DAT File, YSCE use the equivalent of "INITZOOM 1.0".
INITZOOM 1.7
To Make HUD available in only one of EXCAMERAs, it can be hidden in the default cockpit view.
CKPITHUD TRUE
Editor's Note: This DATVAR will be updated later
To Make inst panel available in only one of EXCAMERAs, it can be hidden in the default cockpit view.
CKPITIST FALSE
Editor's Note: This DATVAR will be updated later
This is an optional DATVAR which will allow modders to control if the "radar" gunsight is enabled (the default) or disabled. Radar gunsight. If GUNSIGHT is not defined, YSCE defaults to the equivalent to "GUNSIGHT TRUE".
GUNSIGHT FALSE
GUNSIGHT TRUE
YSCE needs to know the location of the landing gear/skids and arresting hook in order to properly position the aircraft when on ground and carrier decks.
The LEFTGEAR DATVAR is an optional variable for all YSCE Aircraft. This defines the 3D location of the aircraft's left main landing gear wheel/skid. If LEFTGEAR is not defined in the DAT File, YSCE will use the equivalent of "LEFTGEAR -3.0m -1.0m -3.0m".
LEFTGEAR -1.2m -1.70m -1.65m
When defining LEFTGEAR, make sure the first variable is always negative. Failure to do so may cause an aircraft to flip 180 degrees onto its back when landing.
The RIGHGEAR DATVAR is an optional variable for all YSCE Aircraft. This defines the 3D location of the aircraft's right main landing gear wheel/skid. If RIGHGEAR is not defined in the DAT File, YSCE will use the equivalent of "RIGHGEAR 3.0m -1.0m -3.0m".
RIGHGEAR 1.2m -1.70m -1.65m
When defining RIGHGEAR, make sure the first variable is always negative. Failure to do so may cause an aircraft to flip 180 degrees onto its back when landing.
The WHELGEAR DATVAR is an optional variable for all YSCE Aircraft. This defines the 3D location of the aircraft's Nose wheel center, or tail dragger wheel/skid center. If WHELGEAR is not defined in the DAT File, YSCE will use the equivalent of "WHELGEAR 0.0m -1.0m 2.0m".
WHELGEAR 0.0m -1.65m 3.15m
The ARRESTER DATVAR is an optional variable for all YSCE aircraft. This defines the 3D location of the arresting hook when deployed and capable of catching an aircraft carrier's arresting wire. This is used to render the arresting wire "connected" to the aircraft at the appropriate location. If ARRESTER is not defined in the DAT File, YSCE will use the equivalent of "ARRESTER 0.0m -3.0m -1.0m".
ARRESTER 0.0m -1.70m -5.57m
The TIREFRIC DATVAR is an optoinal variable for all YSCE aircraft. This defines the Coefficient of Friction of the wheels which influences how much drag the wheels creates while on the ground when the brakes are not on. This is then combined with the aerodynamic drag to determine how fast the aircraft will slow down. If not defined, YSCE will use the equivalent of "TIREFRIC 0.0".
TIREFRIC 0.09
RETRGEAR is an optional DATVAR which tells YSCE if the aircraft's landing gear are retractable. If not defined in the DAT File, YSCE defaults to the equivalent of "RETRGEAR TRUE".
RETRGEAR FALSE
RETRGEAR TRUE
CDBYGEAR is an optional DATVAR which tells YSCE how much the aircraft's Drag Coefficient is changed by deploying the landing gear. When the landing gear is retracted, the aircraft's Drag Coefficient is reduced. If CDBYGEAR is not defined in a DAT File, YSCE will default to the equivalent of "CDYBYGEAR 0.0".
CDBYGEAR 0.5
GEARHORN is an optional DATVAR which will enable YSCE to sound a "gear not down" alert in the aircraft is descending, below 500ft, with the gear not down, slow near the landing speed, and with flaps down as if intending to land. If you are creating an acrobatic Aircraft, you may consider setting this to FALSE in order to reduce the number of distractions while performing low-altitude aerobatics. If GEARHORN is not defined in the DAT File, YSCE will default to the equivalent of "GEARHORN TRUE"
GEARHORN FALSE
GEARHORN TRUE
YSCE provides the option to define one or more smoke generation points with different colors of smoke set to default. The player must select smoke during the aircraft selection process, but Smoke can be added
SMOKEGEN is an optional DATVAR for YSCE. It is used to define a 3D position for a smoke generator. YSCE will read in the first 8 SMOKEGENs defined in the DAT File. Each Smoke Generator is assigned an index, starting at zero, based on the order in which they appear in twh DAT File. If not defined, YSCE will default to the equivalent of "SMOKEGEN 0.0m 0.0m 0.0m" if the user adds smoke to the aircraft in the aircraft selection menu.
SMOKEGEN -0.3m -0.35m -7.75m
SMOKECOL is an optional DATVAR for YSCE and provides the option of defining a default smoke color (YSCE uses the RGB Color Model to define colors) to specific smoke generators. SMOKECOL expects four inputs in the following order:
- The Smoke Generator id (starts at zero) that the smoke color is for, or "ALL" to define the smoke color for all generators.
- The Red RGB Color level (0-255)
- The Green RGB Color level (0-255)
- The Blue RGB Color level (0-255)
SMOKECOL 0 128 32 32
SMOKECOL ALL 128 32 128
One recomended technique for defining SMOKEGEN and SMOKECOL is to alternate between them as such:
SMOKEGEN -7.92m -2.22m 6.60m #SMOKE GENERATOR POSITION
SMOKECOL 0 128 32 32
SMOKEGEN 7.92m -2.22m 6.60m #SMOKE GENERATOR POSITION
SMOKECOL 1 32 32 128
If SMOKECOL is not defined, YSCE will default to the equivalent of "SMOKECOL ALL 255 255 255", and let the player overwrite smoke color in the aircraft selection menu.
SMOKEOIL is an optional DATVAR for YSCE and allows modders to account for the weight of the smoke oil system on the aircraft. This weight is added to the aircraft's gross weight. Once Smoke is added to an aircraft in the Aircraft selection, it always has the ability to generate smoke and will not consume smoke oil.
SMOKEOIL 100.0kg
YSCE provides the ability for an aircraft to have the engine's nominal thrust direction in one other than the centerline of the aircraft. While some real-life aircraft have thrust vectoring that is integrated with the flight controls system (F-22, Su-57, etc.) in YSCE the thrust vectoring is either fixed (in the case of helicopters) or player-controlled between two DAT File defined vectors. The player-controlled YSCE Thrust Vectoring is most similar to the Harrier or V-22 where the nozzles or engines themselves are changing direction relative to the aircraft's fuselage.
For Helicopters, the thrust vectoring section of the DAT File should generally have the same TRSTVCTR0 and TRSTVCTR1 values like such:
TRSTVCTR TRUE
TRSTDIR0 0.0m 8.0m 0.4m
TRSTDIR1 0.0m 8.0m 0.4m
TRSTVCTR is an optional DATVAR for YSCE aircraft which indicates if an aircraft has player-controlled engine thrust vectoring capabilities. When TRSTVCTR is set to TRUE YSCE will permit the player to control the aircraft's thrust direction by swinging between two vectors defined in TRSTDIR0 and TRSTDIR1. When TRSTVCTR is not defined, YSCE defaults to the equivalent of "TRSTVCTR TRUE".
TRSTVCTR FALSE
TRSTDIR0 is an optional DATVAR for YSCE aircraft and is only used when TRSTVCTR is set to TRUE. This vector defines the direction of the aircraft's normal engine thrust output (when not in reverse thrust) and usually corresponds with the high-speed engine or nozzle position. If TRSTDIR0 is not defined in the DAT File, or TRSTVCTR is set to FALSE, YSCE will use the equivalent of "TRSTDIR0 0.0m 0.0m 1.0m".
TRSTDIR0 0.0m 8.0m 0.4m
TRSTDIR1 is an optional DATVAR for YSCE aircraft and is only used when TRSTVCTR is set to TRUE. This vector defines the direction of the aircraft's engine thrust output when the aircraft is configured for off-normal thrust direction (when not in reverse thrust). If TRSTDIR1 is not defined in the DAT File, or TRSTVCTR is set to FALSE, YSCE will use the equivalent of "TRSTDIR1 0.0m 0.0m 1.0m".
TRSTDIR0 0.0m 1.0m 0.0m
YSFlight and YSCE have the option for Variable Geometry Wings (VGW), like the F-14 or Tu-160. If the aircraft visual model (.dnm file) is properly animated, then certain components will move with the VGW specifications in the DAT File.
VARGEOMW is not a required DATVAR for YSCE aircraft. It controls whether or not the aircraft has VGW and if YSCE should enable VGW performance and animations. If VARGEOMW is not defined in the DAT File, YSCE defaults to the equivalent of "VARGEOMW FALSE".
VARGEOMW TRUE
VAPORPO0 is an optional DATVAR for YSCE aircraft. It indicates where the wing tip is when fully swept back. This position is used as the origin of wing tip vorticies when the aircraft is above 4g. YSCE assumes a symmetric wing tip position and so only one side is defined. When not defined, YSCE uses the equivalent of "VAPORPO0 5.0m 0.0m 0.0m".
VAPORPO0 5.1m 0.55m -5.60m
VAPORPO1 is an optional DATVAR for YSCE aircraft. It indicates where the wing tip is when fully swept forward. This position is used as the origin of wing tip vorticies when the aircraft is above 4g. YSCE assumes a symmetric wing tip position and so only one side is defined. When not defined, YSCE uses the equivalent of "VAPORPO1 5.0m 0.0m 0.0m".
VAPORPO1 8.6m 0.55m -3.20m
NOTE: For aircraft without Variable Geometry Wing, VAPORPO0 and VAPORPO1 should be set to the same value.
VGWSPED1 is an optional DATVAR for YSCE aircraft with VGW. It defines the automatic wing sweep speed at which the wings start to sweep back. If the aircraft is at or below this speed, the wings will be fully swept forward.
VGWSPED1 200kt
VGWSPED1 0.5MACH
NOTE: If this variable is defined with a MACH speed, then it will be converted to meters per second (m/s) assuming ground level Mach to speed conversion.
VGWSPED2 is an optional DATVAR for YSCE aircraft with VGW. It defines the automatic wing sweep speed at which the wings will be fully swept back. If the aircraft is at or above this speed, the wings will be fully swept back.
VGWSPED2 400kt
VGWSPED2 0.7MACH
NOTE: If this variable is defined with a MACH speed, then it will be converted to meters per second (m/s) assuming ground level Mach to speed conversion.
VRGMNOSE is an optional DATVAR for YSCE aircraft which permits the VGW animation and player controls to be used without a performance change and just control slow-speed/high-speed VGW animations. If this DATVAR is not defined in the DAT File, YSCE will default to the equivalent of "VRGMNOSE FALSE".
VRGMNOSE TRUE
CTLATVGW is an optional DATVAR in YSCE and defines if the Aircraft's VGW wings will be automatically controlled by YSCE or if the player must control the VGW sweep angle. If not defined in the DAT File, YSCE will use the equivalent of "CTLATVGW TRUE".
CTLATVGW FALSE
CTLINVGW is an optional DATVAR in YSCE and defines the initial state at which the VGW sweep will be set when an aircraft is spanwed in at, regardless of the aircraft's airspeed. YSCE reads the input as a decimal percent between 0 and 1 and will bound inputs to this range if outside of it, where 0 defines fully swept back and 1 defines fully swept forward.
CTLINVGW 0.5
CLVARGEO is an optional DATVAR for YSCE Aircraft which defines the change in the aircraft's Lift Coefficient when the VGW sweeps from full aft to full forward. When at an intermediate mid-sweep position, the change in Lift Coefficient is linearly interpolated. When not defined in the DAT File, YSCE uses the equivalent of "CLVARGEO 0.0".
CLVARGEO 0.6
CLVARGEO is an optional DATVAR for YSCE Aircraft which defines the change in the aircraft's Drag Coefficient when the VGW sweeps full forward. When at an intermediate mid-sweep position, the change in Drag Coefficient is linearly interpolated. When not defined in the DAT File, YSCE uses the equivalent of "CDVARGEO 0.0".
CDVARGEO 1.2
YSCE has the ability to model the lift and drag charactaristics of landing flaps.
CLBYFLAP is an optional DATVAR in YSCE which defines how much the Lift Coefficient increases when the flaps are deployed to 100%. If this DATVAR is not defined in a DAT File, YSCE defaults to the equivalent of "CLBYFLAP 0.0".
CLBYFLAP 0.2
CDBYFLAP is an optional DATVAR in YSCE which defines how much the Drag Coefficient increases when the flaps are deployed to 100%. If this DATVAR is not defined in the DAT File, YSCE defaults to the equivalent of "CDBYFLAP 0.0"
CLBYFLAP 0.3
FLAPPOSI is an optional DATVAR in YSCE which allows for custom flap position settings to be defined. If FLAPPOSI is not defined in the DAT File, YSCE defaults to the traditional 5 step flap progression which is the equivalent of:
FLAPPOSI 0
FLAPPOSI 0.25
FLAPPOSI 0.5
FLAPPOSI 0.75
FLAPPOSI 1.0
However with FLAPPOSI, an unlimited number of Flap Position can be defined through which the player can step through. Flap position values (decimal percent) must start at zero and end at one, and increase with each additional FLAPPOSI entry.
FLAPPOSI 0.0
FLAPPOSI 0.4
FLAPPOSI 1.0
CTLIFLAP is an optional DATVAR for YSCE aircraft which defines the initial Flap position when an aircraft spawns in. When not defined in a DAT File, YSCE defaults to the equivalent of "CTLIFLAP 0.0".
CTLIFLAP 0.25
There are a variety of depreciated weapon DATVARs that YSCE still recognizes. They are listed at the end of this page. This section focuses on the current DATVARs that are not for machine guns or turrets. Both turrets and machine gun DATVARs are handled in separate sections.
YSCE uses a shorthand notation for the differernt weapons. Refer to the YSCE Weapons page for more information.
HRDPOINT is an optional DATVAR for YSCE aircraft but is required if the aircraft will carry weapons except for guns. The core of the moddern YSCE weapon defintion is the Hardpoint. This DATVAR tells YSCE where weapons should be positioned and what weapons and how many are allowed on the hardpoint. While multiple weapon types can be defined as "allowed" for a hardpoint, the hardpoint can only carry one type of weapon in-game. This DATVAR uses YSCE Weapon Codes to denote specific weapons.
NOTE: Unlike other YSCE DATVARs, HRDPOINT lines cannot have an in-line comment at the end of the line. This will cause the game to crash.
HRDPOINT 4.1m -1.2m -1.5m AGM65 B500 B250 B500HD
HRDPOINT -4.1m -1.2m -1.5m AGM65 B500 B250 B500HD
NOTE: Duplicate weapon codes on a HRDPOINT defnition does not do anything. If multiple weapons of the same type are allowed on a hardpoint, the following notation is used:
HRDPOINT 1.0m 1.0m 1.0m B500*3
Fuel tanks can be added, and custom fuel quantities can be defined for each hardpoint using the following notation. If No fuel quantity value is defined, it will default to 800. Note that the units for this is Kilograms.
HRDPOINT 1.0m 1.0m 1.0m FUEL&500
HRDPOINT -1.0m 1.0m 1.0m FUEL&2000
To define Hardpoints in Internal Weapons Bays that require the weapons bay to be open to release, add the "$INTERNAL" tag to the end of the Hardpoint definition line.
HRDPOINT -5.0m 1.0m 1.0m B500*4 $INTERNAL
The order that the HRDPOINT DATVARs are defined in controls which Hardpoints get weapons first when adding weapons during the pre-flight setup. It is recommended that HRDPOINTs be defined in mirrored left/right pairs, so that weapons are loaded roughly symmetrically. This will support players trying to get realistic weapon configurations on the aircraft they want to fly in-game.
WPNSHAPE is an optional DATVAR in YSCE that allows a custom weapon "skin" to be used inplace of the default weapons "skins". YSCE provides two states, STATIC and FLYING, which allows for the appearance of weapons to change between when they are carried vs when they are flying. Often this is used to "deploy" wings or add a rocket exhaust flame when a weapon is flying.
WPNSHAPE AIM120 STATIC users/HQPGAC/weapons/aim-120a_static.srf
WPNSHAPE AIM120 FLYING users/HQPGAC/weapons/aim-120a_flying.srf
WPNSHAPE [CODE] [STATE] [filepath]
A common use for these custom shapes is to make the static rocket appear like a rocket pod and the flying rocket look like the actual projectile.
LMTBYHDP is an optional DATVAR which will limit the number of weapons that can be loaded to the total number of slots available in HRDPOINT definitions (the one exception is rockets). When all HRDPOINT slots are filled, no further weapons of that type can be loaded. If LMTBYHDP is set to FALSE, then the DATVARs which define the maximum number of a weapon that can be loaded will control the maximum number of a weapon type allowed to be loaded.
LMTBYHDP TRUE
LMTBYHDP FALSE
LOADWEPN is an optional DATVAR which allows for the aircraft to have a default weapon loadout with the weapons filling the first available HRDPOINT slots. This DATVAR uses the Weapon Codes to indicate which weapons are used. Whether loading weapons or fuel, the first available HRDPOINT capable of accepting that weapon type will be loaded.
LOADWEPN B500 2
LOADWEPN AGM65 2
The one difference is with external fuel tanks, where the tanks' fuel load will be defined for each instance of "LOADWEPN FUEL". In the situation where 3 external fuel tanks are defined, two underwing and one center line which is larger, and the underwing HRDPOINTs are defined before the Centerline HRDPOINT, then this is how it would be defined:
LOADWEPN FUEL 800
LOADWEPN FUEL 800
LOADWEPN FUEL 1000
In addition to weapons, LOADWEPN can also be used to add Smoke automatically.
LOADWEPN SMK 100kg
While HRDPOINT, LMTBYHDP, and LOADWEPN are the prefered method to define weapon quantities and visibility, YSCE retains some legacy weapon loading and configuring DATVARs that are broadly categorized into three areas outlined below:
- Initial quantity of a weapon defined, filling the first available HRDPOINT slot suitable for the weapon type.
- The maximum number of a weapon that can be loaded by the aircraft, even if there are extra HRDPOINTs that could hold them.
- If the weapon type is invisible across all HRDPOINTs.
| Weapon | Init DATVAR | Max # DATVAR | Weapons Visible |
|---|---|---|---|
| AIM9 | INITIAAM | MAXNMAAM | AAMVISIB |
| AIM9X | INITAAAM | MAXNAAMM | AAMVISIB |
| AIM120 | INITAAMM | MAXNAAMM | AAMVISIB |
| AGM65 | INITIAGM | MAXNMAGM | AGMVISIB |
| B250 | INITB250 | MAXNB250 | BOMVISIB |
| B500 | INITBOMB | MAXNBOMB | BOMVISIB |
| B500HD | INITHDBM | MAXNBOMB | BOMVISIB |
| FLR | - | - | - |
| IFLR | INITFLR [1] | MAXNMFLR | - |
| RKT | INITRCKT | MAXNMRKT | RKTVISIB |
| FUEL | INITFUEL [2] | - | - |
| GUN | INITIGUN | MAXNMGUN | - |
[1] Defaults to 20 if not defined in the DAT File
[2] Require individual LOADWEPN FUEL calls for each fuel tank with custom fuel values.
As shown, not all weapon types have DATVARs for all options and some share DATVARs. This is a function of the advances with the HRDPOINT system, which overtook and repaled the old weapon slot system, which is now depreciated in YSCE.
While Turrets could be considered a sub-set of Weapon DATVARs, Turrets are formatted differently and are self-contained. Besides NMTURRET, all of the turret DATVARs can be defined multiple times in total in the DAT File, but only once per Turret definition block.
Turret definitions rely on the turret index number which will appear after the DATVAR but before any DATVAR inputs.
This DATVAR defines the total number of turrets that are defined in the DAT File. This is a required DATVAR when turrets are defined in a DAT File. The one point of confusion that may arrise is that Turrets are defined by an index which starts at zero. Therefore the NMTURRET should always be one higher than the index of the last turret.
NMTURRET 5
TURRETPO is a required DATVAR when defining a turret and defines the center position about which the turret will rotate, along with the initial orientation of the object in the DNM file. Information is defined in the following order
- Turret Index number (integer)
- Position of the Turret
- Angle Orientation of the Turret
TURRETPO 0 0m -0.7m 2.8m 0deg 0deg 0deg
TURRETPT is a required DATVAR when defining a turret and specifies the pitch angle properties of the turret in the following order:
- Minimum pitch angle (most down)
- Maximum pitch angle (most up)
- Neutral pitch angle
NOTE: The angles are relative to the angle specified in TURRETPO.
The Neutral angle is used when there are either (a) the turret is being controlled by the computer and no targets are within range or (b) the aircraft spawns in and uses the neutral pitch angle as the default pitch angle on startup.
TURRETPT 0 -40deg 0deg 0deg
TURRETHD is a required DATVAR when defining a turret and specifies the heading angle properties of the turret in the following order:
- Minimum heading angle (most left)
- Maximum heading angle (most right)
- Neutral heading angle
NOTE: The angles are relative to the angle specified in TURRETPO.
The Neutral angle is used when there are either (a) the turret is being controlled by the computer and no targets are within range or (b) the aircraft spawns in and uses the neutral heading angle as the default heading angle on startup.
TURRETHD 0 -80deg 80deg 0deg
TURRETAM is an optional DATVAR when defining a turret and specifies the starting ammunition count of the turret. If the value is set to zero, then the currently loaded machine gun ammunition will be used. If TURRETAM is not specified, YSCE will default to a value of 1000.
TURRETAM 0 3000
TURRETIV is an optional DATVAR when defining a turret and specifies the minimum interval between turret firing events. This is most commonly used for simulating larger caliber turrets, but also for missile turrets to simulate the longer reload times. If this DATVAR is not defined, YSCE defaults to the equivalent of "TURRETIV # 0.5sec".
TURRETIV 0 0.5sec
TURRETRG is an optional DATVAR when defining a turret and specifies the range at which the computer-controlled Turrets will engage an enemy. If this DATVAR is not defined, it will default to 3000m.
TURRETAR is an optional DATVAR when defining a turret and specifies that the computer-controlled turret can target airborne enemies when within range. If not specified, YSCE defaults to the equivalent of "TURRETAR # FALSE".
TURRETAR 0 FALSE
TURRETAR 0 TRUE
TURRETGD is an optional DATVAR when defining a turret and specifies that the computer-controlled turret can target ground enemies when within range. If not specified, YSCE defaults to the equivalent of "TURRETGD # FALSE".
TURRETGD 0 FALSE
TURRETGD 0 TRUE
TURRETCT is a required DATVAR when defining a turret and specifies if the player "PILOT" or computer "GUNNER" will control a turret's angle and firing status.
TURRETCT 0 PILOT
TURRETCT 0 GUNNER
TURRETNM is a required DATVAR if the turret will by synced to a visual model element and move it. TURRETNM is used when a single visual model element will be moved in heading and pitch.
TURRETNM 0 GUN
TURRETNM 1 GUN_BARREL
TURRETNM is a required DATVAR if the turret will by synced to a visual model element and move only in pitch. This is often combined with TURRETNH to achieve a synchronized movement.
TURRETNM 0 GUN_BARREL
TURRETNM is a required DATVAR if the turret will by synced to a visual model element and move only in heading. This is often combined with TURRETNP to achieve a synchronized movement.
TURRETNM 0 GUN_BASE
Because turrets are unlike just about all other DATVARs, here is an example of how an airplane with two turrets might define the turrets in the DAT File.
NMTURRET 2
TURRETPO 0 0m 1.82m 10.91m 0deg 0deg 0deg # TURRETID x y z h p b
TURRETPT 0 0deg 90deg 0deg # TURRETID MinPitch MaxPitch NeutralPitch
TURRETHD 0 -180deg 180deg 0deg # TURRETID MinHdg MaxHdg NeutralHdg
TURRETAM 0 5000 # TURRETID Ammo
TURRETIV 0 0.2sec # TURRETID ShootingInterval
TURRETNM 0 TURRET1 # TURRETID DNM Node Name
TURRETAR 0 # TURRETID Turret is Anti Air Capable
TURRETCT 0 GUNNER # TURRETID Controlled by PILOT or GUNNER
TURRETRG 0 1500m # TURRETID Range
TURRETPO 1 0m -1.67m 10.46m 0deg 0deg 0deg # TURRETID x y z h p b
TURRETPT 1 -90deg 0deg 0deg # TURRETID MinPitch MaxPitch NeutralPitch
TURRETHD 1 -180deg 180deg 0deg # TURRETID MinHdg MaxHdg NeutralHdg
TURRETAM 1 5000 # TURRETID Ammo
TURRETIV 1 0.2sec # TURRETID ShootingInterval
TURRETNM 1 TURRET2 # TURRETID DNM Node Name
TURRETAR 1 # TURRETID Turret is Anti Air Capable
TURRETCT 1 GUNNER # TURRETID Controlled by PILOT or GUNNER
TURRETRG 1 1500m # TURRETID Range
YSCE uses several DATVARs to define critical angles and speeds that control the Lift and Drag characteristics of the aircraft. To learn how these DATVARs will influence performance, refer to the Physics page.
CRITAOAP is a required DATVAR and defines the positive angle of attack (nose above velocity vector) at which the aircraft will transition to the positive post-stall regieme. When designing a DAT File, it is important to note that if MXIPTAOA is greater than CRITAOAP, then it will be possible to immediately enter a stall just by inputting maximum pitch-up control commands.
CRITAOAP 25deg
CRITAOAM is a required DATVAR and defines the negative angle of attack (nose below the velocity vector) at which the aircraft will transition to the negative post-stall regieme. CRITAOAM must be less than CRITAOAP. When designing a DAT File, it is important to note that if MXIPTAOA is greater than the absolute value of CRITAOAM, then it will be possible to immediately enter a stall just by inputting maximum pitch-down control commands.
CRITAOAM -10deg
FLATCLR2 is an optional DATVAR and defines the portion of the Lift Coefficient Curve in the negative post-stall regieme between CRITAOAM and when the Lift Coefficient decays to zero. In this region the lift coefficint retains the same value as calculated for CRITAOAM. Refer to the YSCE Physics Wiki Page Lift Coefficient definition. If FLATCLR2 is not defined, YSCE will use the equivalent of "FLATCLR2 0deg".
FLATCLR2 3deg
FLATCLR1 is an optional DATVAR and defines the portion of the Lift Coefficient Curve in the positive post-stall regieme between CRITAOAP and when the Lift Coefficient decays to zero. In this region the lift coefficint retains the same value as calculated for CRITAOAP. Refer to the YSCE Physics Wiki Page Lift Coefficient definition. If FLATCLR1 is not defined, YSCE will use the equivalent of "FLATCLR1 0deg".
FLATCLR1 3deg
CLDECAY2 is an optional DATVAR that defines the portion of the Lift Coefficient Curve in the negative post-stall regieme at angles of attack below the FLATCLR2 region. In this region the lift coefficint linearly decays to zero. Refer to the YSCE Physics Wiki Page Lift Coefficient definition. If CLDECAY2 is not defined, YSCE will use the equivalent of "CLDECAY2 0deg".
CLDECAY2 10deg
CLDECAY1 is an optional DATVAR that defines the portion of the Lift Coefficient Curve in the negative post-stall regieme at angles of attack below the FLATCLR1 region. In this region the lift coefficint linearly decays to zero. Refer to the YSCE Physics Wiki Page Lift Coefficient definition. If CLDECAY1 is not defined, YSCE will use the equivalent of "CLDECAY1 0deg".
CLDECAY1 15deg
MAXCDAOA is an optioanl DATVAR that defines the Angle of Attack at which maximum drag coefficient is reached. Beyond this Angle of Attack, the drag coefficient does not increase as a function of Angle of Attack. If MAXCDAOA is not defined in a DAT File, YSCE will use the equivalent of "MAXCDAOA 45deg".
MAXCDAOA 35deg
WINGAREA is an optional DATVAR in YSCE and is used in a number of equations to define the aerodynamic properties. However, the affect is canceled out, so that as long as a non-zero WINGAREA value is defined in the DAT File, it will have no affect on aircraft performance. Legacy YSFlight versions would crash if WINGAREA was not defined. If WINGAREA is not defined in a DAT File, YSCE will use the equivalent of "WINAREA 1m^2"
WINGAREA 25m^2
WINGAREA 100000in^2
CRITSPED is an optional DATVAR which is used to simulate transonic and supersonic drag. It should be between REFVCRUS and MAXSPEED. Should CRITSPED be faster than MAXSPEED, an error will be generated. If CRITSPED is not defined in a DAT File, YSCE will calulate CRITSPED as the following:
CRITSPED 500kt
MAXSPEED is a required DATVAR which defines the theoretical maximum speed of an aircraft. It must be faster than both REFVCRUS and CRITSPED.
MAXSPEED 1.4MACH
REFVCRUS is a required DATVAR and one of three DATVARs which defines the reference cruise conditions used to calculate lift and drag coefficient curves. REFVCRUS represents the speed at which the aircraft will fly at zero angle of attack at the "cruise" condition.
REFVCRUS 0.7MACH
REFACRUS is a required DATVAR and one of three DATVARs which define the reference cruise conditions used to calculate lift and drag coefficient curves. REFACRUS represents that altitude of the "cruise" conditions.
REFACRUS 35000ft
REFTCRUS is an optional DATVAR and one of three DATVARs which define the reference cruise conditions used to calculate lift and drag coefficients. REFTCRUS represents the throttle position required to maintain non-accelerating level flight at REFACRUS while flying at REFVCRUS. If REFTCRUS is not defined in the DAT File, YSCE will use the equivalent of "REFTCRUS 1.0".
REFTCRUS 1.1
REFTCRUS 0.5
REFVLAND is a required DATVAR and one of four DATVARs which define the reference landing conditions used to calculate lift and drag coefficients. REFVLAND represents the speed at which the aircraft is designed to land at.
REFVLAND 136kt
REFAOALD is a required DATVAR and one of four DATVARs which define the reference landing conditions used to calculate lift and drag coefficients. REFAOALD represents the angle of attack at which the aircraft is designed to land at.
REFAOALD 10deg
REFLNRWY is a required DATVAR and one of four DATVARs which define the reference landing conditions used to calculate lift and drag coefficients. REFLNRWY represents the distance the aircraft is designed to stop in.
REFLNRWY 1500m
REFTHRLD is a required DATVAR and one of four DATVARs which define the reference landing conditions used to calculate lift and drag coefficients. REFTHRLD represents the throttle required to fly at the conditions defined by REFVLAND and REFAOALD.
REFTHRLD 0.7
This table provides a summary of the YSCE Aircraft DATVARs and their expected data types and default units.
| DAT Variable | Data Type | Definition / Purpose | Unit Type(s) | Required? | Category |
|---|---|---|---|---|---|
| IDENTIFY | String | The name of the aircraft as it should be displayed in YSCE | N/A | Yes | Admin |
| SUBSTANM | String | The name of the aircraft that should be rendered in place of this aircraft if the user does not have it installed. | N/A | Recommended | Admin |
| CATEGORY | String | Provides basic sorting and similar performance matching for simulations and Autopilot performance buckets | N/A | Yes | Admin |
| AIRCLASS | String | Unlocks helicopter-unique performance and handling. | N/A | Yes (Helicopters) | Admin |
| --- | --- | --- | --- | --- | --- |
| FUELMILI | Float | The fuel consumption (weight per second) of a propeller or jet engine when operating at 100% throttle without afterburner. | Weight | Yes | Engine |
| THRSTREV | Float | The percentage of the engine's thrust that can be produced in reverse | N/A | No | Engine |
| AFTBURNR | Boolean | Indication if the aircraft has an after-burning jet engine | N/A | Yes (Afterburner) | Engine |
| THRAFTBN | Float | The maximum thrust of a jet engine when the afterburner is engaged at 100% throttle at sea level. Requires AFTBURNR TRUE. | Weight | Yes (Afterburner) | Engine |
| THRMILIT | Float | The maximum thrust of a jet engine when operation 100% throttle without the afterburner engaged at seal level. | Weight | Yes (Jets) | Engine |
| FUELABRN | Float | The fuel consumption (weight per second) of a jet engine when operating with the afterburner engaged at any throttle setting | Weight | Yes (Afterburner) | Engine |
| PROPEFCY | Float | The percent efficiency (decimal) of a propeller engine's propeller | N/A | Recommended (Propeller) | Engine |
| PROPELLR | Float | The power of a propeller engine | Power | Yes (Propellers) | Engine |
| PROPVMIN | Float | The speed above which static propeller thrust calculation is disabled | Speed | Recommended (Propeller) | Engine |
| --- | --- | --- | --- | --- | --- |
| COCKPITP | Float | The position of the cockpit F1 View point | Length | Yes | Cockpit |
| COCKPITA | Float | The neutral view direction of the Cockpit F1 View Point | Angle | No | Cockpit |
| INSTPANL | String | If an instrument panel should be displayed in place of the HUD and the filepath to a custom instrument panel. | N/A | No | Cockpit |
| ISPNLPOS | Float | The position of the instrument panel relative to the COCKPITP coordinates. | Length | No | Cockpit |
| ISPNLSCL | Float | Controls the scale of the instrument panel | N/A | No | Cockpit |
| ISPNLATT | Float | Controls the rotational attitude of the instrument panel | Angle | No | Cockpit |
| ISPNLHUD | Boolean | Allows both HUD and instrument panel | N/A | No | Cockpit |
| EXCAMERA | String Float Tag |
Provides additional fixed viewpoints the player can cycle through by pressing F1. | Length Angle |
No | Cockpit |
| SCRNCNTR | Float | Controls where the view point is relative to the screen. | N/A | No | Cockpit |
| LOOKOFST | Float | Modifies the F7 and F8 view points | Length | No | Cockpit |
| INITZOOM | Float | Defines the initial zoom level | N/A | No | Cockpit |
| --- | --- | --- | --- | --- | --- |
| LEFTGEAR | Float | Location of Left Landing Gear | Length | No | Landing Gear |
| RIGHGEAR | Float | Location of Right Landing Gear | Length | No | Landing Gear |
| WHELGEAR | Float | Location of Nose/Tail Wheel | Length | No | Landing Gear |
| ARRESTER | Float | Location of Arresting Hook Point | Length | No | Landing Gear |
| RETRGEAR | Boolean | Indication if the Aircraft's landing gear are retractable | N/A | No | Landing Gear |
| CDBYGEAR | float | The change to the Aircraft's Drag Coefficient by extending the landing gear | N/A | No | Landing Gear |
| GEARHORN | Boolean | Suppresses the audio que that the landing gear are not extended when in a landing configuration | N/A | No | Landing Gear |
| --- | --- | --- | --- | --- | --- |
| SMOKEGEN | Float | Location of Smoke Generator | Length | No | Smoke |
| SMOKECOL | Integer String |
Default color of smoke generator(s) | N/A | No | Smoke |
| SMOKEOIL | Float | Weight of Smoke Generation Equipment | Weight | No | Smoke |
| --- | --- | --- | --- | --- | --- |
| TRSTVCTR | Boolean | Indication if the aircraft has off-centerline thrust directions | N/A | No | Thrust Vectoring |
| TRSTDIR0 | Length | The neutral / normal conventional flight thrust direction vector | Length | No | Thrust Vectoring |
| TRSTDIR1 | Length | The diverted thrust direction vector | Length | No | Thrust Vectoring |
| --- | --- | --- | --- | --- | --- |
| VARGEOMW | Boolean | Controls if an Aircraft has Variable Geometry Wings | N/A | No | VGW |
| VAPORPO0 | Float | Wingtip position when wings are fully swept back | Length | No | VGW |
| VAPORPO1 | Float | Wingtop position when wings are fully swept forward | Length | No | VGW |
| VGWSPED1 | Float | Speed at which wings automatically begin to sweep back | Speed | No | VGW |
| VGWSPED2 | Float | Speed at which wings automatically reach fully swept back | Speed | No | VGW |
| VRGMNOSE | Boolean | If the VGW definition is for a nose (concorde) | N/A | No | VGW |
| CTLATVGW | Boolean | If the VGW is controlled by YSCE | N/A | No | VGW |
| CTLINVGW | Percent | The initial VGW position | N/A | No | VGW |
| CLVARGEO | Float | The change in Life Coefficient due to VGW | N/A | No | VGW |
| CDVARGEO | Float | The change in Drag Coefficinet due to VGW | N/A | No | VGW |
| --- | --- | --- | --- | --- | --- |
| CLBYFLAP | Float | Increase in Lift Coefficient due to full flaps | N/A | No | Flaps |
| CDBYFLAP | Float | Increase in Drag Coefficient due to full flaps | N/A | No | Flaps |
| FLAPPOSI | Float | Defines custom flap positions | N/A | No | Flaps |
| CTLIFLAP | Float | Defines the intial flap position when the aircraft spawns. | N/A | No | Flaps |
YSFlight evolved over nearly 2 decades of development. As such Captain YS found different and sometimes better ways to acomplish the same thing, leading to some DATVARs no longer being the YSFlight & YSCE Community standard. You may see these DATVARs in various older DAT Files, but they should not be used for YSCE.
Editor Note: This section is still being developed.
- AAMSLOT_
- AGMSLOT_
- BOMBSLOT
- RKTSLOT_