How to Add Your Model to CFS2 Quick Combat
With a little editing, you can add (or subtract) your own model or any add-on aircraft from the Quick Combat roster!

The file containing the Quick Combat aircraft roster is qc_plane.qcb, located in the QUICKCOM folder under the Combat flight Simulator 2 directory. It's a plain ASCII text file, which means you can edit the content using any text file editor such as Microsoft's WordPad.

Before you start making changes, make a copy of this file and rename it as, qc_planeORG.qcb just to protect yourself.

The qc_plane.qcb file organizes all Quick Combat aircraft in sections identified by [option.n].

Under each [option.n] header is the description of a unique category, or group, containing one or more aircraft. There is also a [strings] section which contains all the aircraft and category names used by Quick Combat.

The [STRINGS] section assigns names, or "text strings" to each aircraft category, each aircraft and each option. These are the strings displayed in the pull-down menus for "Enemy aircraft type" and "Bomber Type" on the Quick Combat "Enemies" page in CFS2. The strings can contain any words you like, so make them meaningful.

This section is normally found at the bottom of the QCB file, but may be placed anywhere. Placing it at the top of your QCB file makes it easier to define and locate the names for various aircraft and options.

There are three types of [STRINGS] you can define:

"categoryOption"    "aircraftOption"    "aircraftName"

   "categoryOption" is used to name an aircraft category or grouping,
   "aircraftOption" is the exact name of the aircraft folder, and
   "aircraftName" is used to name a specific aircraft.

Here are some typical examples for each string type ...

"JapaneseFightersOption" = Japanese Fighters
"AlliedFightersOption" = Allied Fighters
"FightersOption" = All Fighters
etc. ....

"A6M2_ZeroOption" = A6M2_Zero
"A6M5_ZeroOption" = A6M5_Zero
"B24D_LiberatorOption" = B24D_Liberator
etc. ....

"A6M2_ZeroName" = A6M2 Zero
"A6M5_ZeroName" = A6M5 Zero
"B24D_LiberatorName" = B24D Liberator
etc. ....

With the exception of the "aircraftName" entry, do not use blank spaces. If you want a blank space, use the underscore character.

In its most general form, an option entry looks like this ...



Here's a typical example ...



The parameters are ...


Option number. Used to reference the option from within the QCB file. Option numbers begin with "0" and continue in order for as many options as you need.


"categoryOption" The name assigned to this aircraft category.
If you use the placeholder, "%categoryOption%" here, CFS2 will replace it with the name you defined under [STRINGS] for this option. For example, using the string definitions above, CFS2 will automatically replace the string %FightersOption% with the string All Fighters.


aircraft number. Used to reference the aircraft under this option. Aircraft are numbered beginning with "0" and continuing in order for each aircraft listed under this option.


aircraft folder name. Used to identify the aircraft folder in CFS2. This must always be the aircraft's exact folder name, including any capitalization, spaces, underscores, and numbers. This is not the name of the aircraft itself.


aircraft type. An index value that designates the type of aircraft.
CFS2 Quick Combat Aircraft Types
   1 = fighter aircraft
   2 = bomber


"aircraftName". The name that will appear in the pull-down menu for "Enemy aircraft type" and "Bomber Type" on the Quick Combat "Enemies" page in CFS2.
If you use the placeholder, "%aircraftName%" here, CFS2 will replace it with the name you defined under [STRINGS] for this option. For example, using the string definitions above, CFS2 will automatically replace the string %F4F4_WildcatName% with the string F4F4 Wildcat.

Now that you have an understanding of the QCB file. Here's how to add your own model, or any other add-on aircraft to the Quick Combat roster. Let's say your model is called My Airplane, a single-seat fighter/bomber. Its folder name is My_Airplane.

First, add your aircraft to the [strings] section. The fighter/bomber category already exists, so you don't have to add a new aircraft category.

Add the follwing entry at the end of the "aircraftOption" list,

"My_AirplaneOption" = My Airplane

To give your model a specific name, add the following entry at the end of the "aircraftName" list,

"My_AirplaneName" = F11 Swifty

Scroll down the QCB file until you find the Fighter/Bomber option, identified as follows;


Under this option, scroll down to the last aircraft listed under Fighter/Bombers and add your aircraft as the next entry. If there are already 6 fighter/bombers listed, your aircraft will be number 7. Following the above descriptions, you would add the following:


You would use the above example to add your plane to any other "categories" [option.n] in the QCB file.

Now let's add My Airplane as an individual aircraft that can be selected. Whenever you select an individual aircraft, that aircraft will be your only opponent. It's a great way to practice against a particular aircraft type or to test your own model for combat damage effects.

The QCB file lists aircraft categories first, followed by individual aircraft. The [option.n] section for an individual aircraft contains only the OptionName entry and the entry for a single aircraft.

Scroll down the file until you see single aircraft entries, for example,



etc. ....

If the last entry for an individual aircraft is [option.24], then you will add your aircraft as [option.25]. Since there will be only one aircraft under this option, it becomes aircraft "0."



Save the edited QCB file and you're done.

The F11 Swifty should now appear in Quick Combat as an Axis Fighter/Bomber and as an individual selection.

Occasionally, CFS2 will not accept the airplane being added and when you attempt to fly it in Quick Combat, the simulator will freeze or reduce the number of enemy aircraft you selected to fly against. To correct his, simply remove the last aircraft you added to the QCB file and try again, or restore your copy of the original file, qc_planeORG.qcb.