It's not whether we use QC or not....
I don't fly QC so I don't concern myslefl with anything that might effect it.....
Hi everybody!
The Quick Combat list file was never a problem up until the time when the necessity to have theatre-dedicated several installs came along. As a matter of fact, if we stick to the PTO, we'll only need to edit
qc_plane.qcb when we want to have a dogfight with a particular addon model. In this case the new addon will only appear in the Quick Combat list by adding it to
qc_plane.qcb.
The problem arises when we do not want to see Zeros over England, Stalingrad or Libya, or FW190s over the Solomon Sea. Deleting the stock aircraft folders to make room for theatre-dedicated aircrafts, will force us to edit
qc_plane.qcb, because CFS2 will look for the folder names listed in it upon startup.
To make an example, if "A6M2_Zero" folder name is not included in the \AIRCRAFT legacy folder, but it's listed in the stock
qc_plane.qcb, CFS2 will work only in Free Flight, providing one doesn't check the Advanced Info screen through a simple click on the Map Icon in the 2d panel.
This and any other CFS2 activity, like Mission Builder of flying any mission, will cause in CFS2 a dreaded lockup or Crash-To-the-Desktop, otherwise known among the initiated as "CTD".
Hence the need to edit
qc_plane.qcb and the great conversion plan suggested by Bearcat above.
I hope this will help understanding why we need so much extra work when we want to dedicate CFS2 to a specific WWII theatre of ops. I have a dedicated
qc_plane.qcb for every WWII scenarios (7) I have installed, plus one for Korea and one for the Spanish Civil War. Since I am toying with the idea to have WWI as well, I will need soon a WWI
qc_plane.qcb!
Cheers!
KH :ernae: