CFS2 Configuration file
The Aircraft CFG FILE

[FLTSIM.n] Section

The [FLTSIM.n] section of the CFG file denotes a different version, or configuration, of your aircraft, and is known as a configuration set.

Each aircraft defined by a configuration set will appear as a separate listing in the Select Aircraft dialog box. The fact that multiple “aircraft” share some components is hidden from the user.

From your perspective, they are distinct aircraft just as if all the common files were copied and pasted in distinct aircraft folders. From your perspective, the aircraft are really just different configuration sets of the same aircraft.

Configuration sets allow a single aircraft folder to represent several aircraft and allow those aircraft to share components.

In its most general form, the [FLTSIM.n] section contains the following parameters that define the details of the particular configuration set:

[FLTSIM.0]
title
sim
model
panel
sound
texture
KB_checklists
KB_reference

The parameters are ...

[FLTSIM.0]

version number. Each version, or configuration of your aircraft is given an identifying number. Most models contain only [FLTSIM.0] because there is only one configuration set. If there is more than one configuration set, each version is labeled [FLTSIM.1], [FLTSIM.2], [FLTSIM.3], etc., each referring to a different version of the aircraft.

title

The title of the aircraft that will appear in the Select Aircraft dialog.

Example ... title=My Airplane

If you are creating multiple versions of this model, you have to change the title parameter for each version so that all the planes show up as a separate entries in the menus.

sim

Specifies which .air (flight model) file (located in the AIRCRAFT folder) to use. This must be the same as the filename of the MDL file.

Example ... sim=myairplane

model

Specifies which model folder to use.

Example ... model=VX5

To create three versions of your aircraft, e.g. myairplane.mdl, simply duplicate the original model folder for each added version give each folder name a new extension. You can name the extensions whatever you want.

Under the folder "My Airplane," you'll see folders named ...

model
model.VMF244
model.VX5

The files in the model folders are all the same and can just be copy/pasted from the original model folder to the other two.

Each version has its own [FLTSIM.n] section. Your original model is listed in the [FLTSIM.0] section. The VMF244 version is listed in the [FLTSIM.1] section. The VX5 version is listed in the [FLTSIM.2] section as shown in the following example:

[FLTSIM.0]
title=My Airplane
sim=myairplane
model=
panel=
sound=
texture=
KB_checklists=my_airplane_check

[FLTSIM.1] title=My Airplane
sim=myairplane
model=VMF244
panel=
sound=
texture=
KB_checklists=my_airplane_check

[FLTSIM.2] title=My Airplane
sim=myairplane
model=VX5
panel=
sound=
texture=
KB_checklists=my_airplane_check

panel

Specifies which panel folder to use.

Example ... panel=IFR

Let's say each of your three aircraft versions of your aircraft use different panel designs. Simply duplicate the original panel folder for each added version give each folder name a new extension. You can name the extensions whatever you want.

Under the folder "My Airplane," you'll see folders named ...

panel
panel.IFR
panel.Radar

Once again, each version has its own [FLTSIM.n] section. Your original model is listed in the [FLTSIM.0] section. The IFR version is listed in the [FLTSIM.1] section. The Radar version is listed in the [FLTSIM.2] section as shown in the following example:

[FLTSIM.0]
title=My Airplane
sim=myairplane
model=
panel=
sound=
texture=
KB_checklists=my_airplane_check

[FLTSIM.1] title=My Airplane
sim=myairplane
model=VMF244
panel=IFR
sound=
texture=
KB_checklists=my_airplane_check

[FLTSIM.2] title=My Airplane
sim=myairplane
model=VX5
panel=Radar
sound=
texture=
KB_checklists=my_airplane_check

sound

Specifies which sound folder to use.

Example ... sound=

Let's say each of your three aircraft versions of your aircraft use different panel designs. simply duplicate the original panel folder for each added version give each folder a new extension. You can name the extensions whatever you want.

The parameters for each configuration set can refer to the same files, to different files, or to a mix of files. While you can certainly create separate sound files for each of your three aircraft versions, using the same naming convention as for model and panel folders, it's more common that you would use the same sound folder for each version. In this case, leaving the "sound" parameter undefined in each of the three [FLTSIM.n] sections above would point to the single “sound” folder in your My Airplane folder.

texture

Specifies which texture folder to use.

Example ... texture=BattlePaint

Let's say you create three paint schemes for your aircraft, a new paint scheme for the original model, a battle worn paint scheme and a racing scheme. Once again, you simply duplicate the original texture folder for each paint scheme and give each folder a new extension. You can name the extensions whatever you want.

Under the folder "My Airplane," you'll see folders named ...

texture
texture.BattlePaint
texture.RacePaint

Duplicate your texture folder for each version and give it an identifying extension before you start pasting alternate textures into the folder, overwriting existing files.

After you create the new texture folders for each version, copy and paste the new texture files into the appropriate texture folder, overwriting the old files.

Once again, each version has its own [FLTSIM.n] section. Your original model is listed in the [FLTSIM.0] section. The IFR version is listed in the [FLTSIM.1] section. The Radar version is listed in the [FLTSIM.2] section as shown in the following example:

[FLTSIM.0]
title=My Airplane
sim=myairplane
model=
panel=
sound=
texture=
KB_checklists=my_airplane_check

[FLTSIM.1] title=My Airplane VMF-244
sim=myairplane
model=VMF244
panel=IFR
sound=
texture=BattlePaint
KB_checklists=my_airplane_check

[FLTSIM.2] title=My Airplane VX-5
sim=myairplane
model=VX5
panel=Radar
sound=
texture=RacePaint
KB_checklists=my_airplane_check

In the above examples, we have created three distinct versions of the model, myairplane.mdl: the original model [FLTSIM.0], the VMF244 version with an IFR panel and a combat paint scheme [FLTSIM.1], and the VX-5 version equipped with radar and a racing paint scheme [FLTSIM.2]. Using this technique, you could also create even more versions ... a VMF244 version with radar and racing paint, a VX-5 version with combat paint, the original model with radar, etc..

NOTE
When creating and referencing multiple model, panel, sound, and texture directories, use the naming convention foldername.extension, where the extension is a unique identifier for that configuration set (e.g., .IFR or .RacePaint). To refer to the folder from the relevant parameter in the aircraft.cfg file, just specify extension (e.g., panel=IFR or texture=RacePaint). If no parameter is specified (as in the [FLTSIM.0] sections above), CFS2 automatically refers to the default folders, the ones without an extension.

CFG File CFG File [WEIGHT_AND_BALANCE]