Greetings all,As a habit, I like to properly name the aircraft folders in my FS9 aircraft folder. For example, if I download a 737 and the folder name is B_737, or something like that, then I change the name to Boeing 737. I do the same in the aircraft configuration file so that it is properly labled in FS9. However, when I do this with the LDS 767 the autopilot will not function. Is there anyway around this, or am I stuck with a black sheep folder?-Jeremy

Renaming folders is asking for trouble I'm afraid. I've had users who do things like that, and it can easily turn into a support headache.I'd suggest sticking with the 'black sheep folder' as you put it (interesting phrase by the way :-) )Cheers,Bryan

Yep, that's what I thought I'd here. It's a shame though because my aircraft folder was looking so nice. Thanks,-Jeremy

I've been renaming aircraft folders to suit me for both FS9 and FSX for a long time.................never had a problem.

>Yep, that's what I thought I'd here. It's a shame though>because my aircraft folder was looking so nice. Thanks,>>-JeremyIt's just a name what is in the name lol :-)http://i5.photobucket.com/albums/y156/awf1/sign.jpg

Jeremy,Try renaming the folder, but NOT changing the information in the aircraft.cfg file. Does that work?

Looks like it's the other way around for me. I had no problem replacing "Level-D" with "Boeing" in the cfg file, but renaming the folder just screws up my universe. No big deal, at least it's the only ugly duckling in my A/C folder.....the folder name that is, not the aircraft.

You could hide the folder and get rid of that darn black sheep :-lol(visually that is)

Problems arise when renaming folders when said folders are referred to in "alias" situations, that is I renamed one of the default planes and another plane was using the default sounds. This created problems because the path noted in the sound.cfg no longer existed.Perhaps this is causing your problems as well.Just a thought.