How about the QC file?
Hi highpockets!
Have you checked that your QC file, stored in CFS2 root \QUICKCOMBAT folder, has the correct aircraft folder names in it? I suspect sound or panel aliasing is not your problem, since, if you had an incorrect aliasing, you shouldn't be able to see such aircrafts in Free Flight either. When there are neither valid panels nor sound files, aircrafts simply do not show up, while CFS2 runs normally.
I am saying this because the QC file is the main culprit for QC problems and error messages, after the exceeded limit of aircrafts installed. The latter is the primary cause of the obnoxious, and misleading, message we get after we install that only aircraft that exceeds CFS2 limit, which in my pc variates from 100 to 110 planes. I never understood why that number variates according to which install (I have a multi-theatre install) I am flying in at any given moment.
There isn't any corrupt file/folder, only one aircraft too many in CFS2 root \AIRCRAFT folder, MB goes beserk and cannot generate a Quick Combat mission. Simply removing that extra plane resolves the problem.
But the other snafu, that I incurred in several times when I was still a CFS2 and multi/install rookie, was deleting/renaming addon aircraft folders that were listed inside the QC list file, forgetting to edit the QC file to reflect the change. CFS2 never forgave me for overlooking this detail. In both cases you will not only be unable to fly Quick Combat, but your Mission Builder and none of your installed missions/campaings will work at all.
If you have an aircraft folder name listed in the QC file and such folder is not in CFS2 root \AIRCRAFT, maybe deleted for cleanup or simply renamed, QC starts having fits and sending all kinds of error messages, most of them not pointing to the actual problem and very confusing as to what to do next to cure it. Sometimes a simple typo broke all hell loose!
This is also the main problem in removing stock aircrafts that do not belong to dedicated theatre installs, like Japanese planes in Europe. Only removing them from the QC file as well ensures a clean, fully-functioning war theatre install.
A careful check that all aircrafts listed in the QC file were also present in CFS2 root \AIRCRAFT, and their folder names were spelled exactly the same in both places, always cured the problem for me and my CFS2 went back purring like a well fed kitten.
I hope this helps pinpointing the cause of your problem.
Cheers!
KH
:ernae: