Simviation Forums

Eureka! I actually got my act together and fixed this mess (Much thanks to Hagar, Happ, and James)! And what a stupid mess it was...

...So if it can help spare any of my miserable anguish to others, I'll try, for a moment, to give something back and share a few hard learned lessons:

#1). If you replace 3rd party aircraft to CFS in a situation like this, make sure that both their FOLDER NAMES and their TITLES in the CFG files are identical to the originals. I studiously copied the CFG titles, but neglected to accurately reproduce my folder names (Duh...). MB apparently recognizes aircraft based on their folder names as they appear in the CFS2 AIRCRAFT folder, while CFS itself seems to read the titles from the CFG file in the individual aircraft data. This explains why the

Whew ! Mongoose, glad you've sorted it, the sad part is we'll all probably do the same things again 6 months down the line when we forget about it
I make notes of any changes i do & then promptly go and loose 'em ! if only we could clip in some new memory banks in the brain for the important stuff

Thanks, Happ. I think there's an old saying somewhere which tells us that pain is the source of all memory. And with that little nugget in mind, I don't think I'm going to forget anything about THIS particular episode anytime soon!

Regards,

Mongoose

Eureka! I actually got my act together and fixed this mess

Well done old chap. It does seem a tad complicated.
Glad you finally figured it out. Thanks for the feedback.

If you replace 3rd party aircraft to CFS in a situation like this, make sure that both their FOLDER NAMES and their TITLES in the CFG files are identical to the originals.

One further complication. Aircraft are generally recognised in CFS1 & CFS2 missions by their folder names. I believed this to be a hard & fast rule for years. After troubleshooting some 3rd party campaigns I found this is not always the case. Some missions/campaigns seem to cause far more problems than others. People were always mailing me about the same ones & on investigation I finally found out why. Some 3rd party aircraft commonly used in missions have been configured with several different variations on one folder.* In this case they are identified in the missions by their Aircraft.cfg title= names. Your advice is still good. Don't change anything. Install all the files, including the aircraft, as they were originally configured. Then the missions should work as advertised.

*PS. I don't see any advantage to this method. If anyone has problems this just makes it more difficult to troubleshoot.

Thanx, Hagar. I know exactly what you mean about aircraft folders with multiple variations. I used to have several of those specimens in my collection before my Hard Drive went south. Fortunately for me, I now realize, they never happened to make it into any of my missions! I will definitely keep this in mind...

Thanx again,

Mongoose