I read in a post somewhere that you can add or adjust a certain line in the fsx.cfg to point the sim to the old aircraft directory used in fs9. So i was just wondering...If we created a fake fs9.exe in the fsx main folder, and then made that cfg tweak would we be able to install some of our fs9 planes directly into fsx using the installers that came with the planes instead of having to drag over?I suppose this question is more relavent for those of us who no longer have fs9 installed :-)Dave

The aircraft folder structure in FSX has changed somewhat from FS9 (aircraft are now located in the SimObjects/Aircraft folder for instance), so FS9 installers would not know where to put the files that are in the aircraft folder.

Hi,The answer is yes. If you edit the fsx.cfg file and add to the MAIN section:SimObjectPaths.6=AircraftThen FSX will look in an AIRCRAFT folder (that you create) for planes, just like FS9. Install your planes into FSX and they should install fine (no guarantees on how they run though!).BTW, I don't think it is a good idea to point FSX to the default FS9 folder - mine froze when I tried it.Hope this helps,--Tom GibsonCal Classic Propliner Page: http://www.calclassic.comFreeflight Design Shop: http://www.freeflightdesign.comDrop by! ___x_x_(")_x_x___

well i didnt mean to point it at the real fs9 directory...i meant to point it at the aircraft folder which i would create under the fsx root, after making the fsx.cfg entry.Are you saying you did this and it froze?...or are you saying you actually pointed to the real fs9 folders?Dave

I tried an experiment a while ago, pointing FSX Demo 1 to my FS9 aircraft folder, and it worked, but I got error messages complaining about duplicate title= lines for the aircraft that FSX had that are also in FS9. (Like the Baron and aircraft I'd copied over to the FSX aircraft folder.) But otherwise it did work. I tried moving the FS9 versions of the "duplicate" aircraft into a temporary folder and got rid of those error messages, but I decided a seperate FSX aircraft folder made more sense. Afterall, I'm likely going to have to edit the panels of most pre-FSX aircraft to get them to work right."Let me help you out. You're cleared to taxi any way you can to any runway you see."

The demo program had several 'stoppers' in it - to stop it being edited/changed; the cfg file being one!In the 'real' version you can add folders in the SimObjects folder and then add that folder to the list in the fsx.cfg found in your 'Documents & Settings' folder on your C-drive (I do a shortcut to the cfg file and pop it in the FSX folder then you don't have to hunt it down every time you want to edit it!).Viz:Under the heading [MAIN] in the fsx.cfg file you will find five lines, the last being:SimObjectPaths.5=SimObjectsMiscFor AI Aircraft ('cos if you put them in the Aircraft folder they show in your 'flyable' list) add this folder (suggest) "AI_Aircraft".Then ADD this line to your fsx.cfg file and SAVE the file:SimObjectPaths.6=SimObjectsAI_AircraftNot tried it yet but it seems logical you can add more folders to split your AI stuff down even further (pax, cargo, mil. etc.)?As for aliasing to a folder outside of the FSX route I don't know yet but you can for scenery as I have used some of my already installed FS2004 in FSX (but be careful which you choose)!!One other thing - I haven't managed to get window/logo night lighting to work in FSX yet using 'FS9' AI aircraft???Hope this helps someome :)

Actually, with Demo 1 (and presumably 2) the SimObjectPaths config entry works fine. The error messages I mentioned were telling me, for instance, that I had two aircraft with this title line:title=Beech Baron 58 Paint1(One was the FS9 default Baron, one was the FSX Demo 1 default Baron.) The title= lines are supposed to be unique for each aircraft variation. It shows that FSX actually does some error checking that FS9 didn't do, and actually showed me that I had a couple errors in FS9 aircraft. (Multiple aircraft in FS9 that had the same title= line, so one of them didn't show up in FS9.)I ended up using SimObjectPaths.6=Aircraft in my FSX Demo 1 config because the planes I copied over used FS98 style gauges (which of course don't work) so I ended up redoing one aircraft's panel and expect I'll end up doing more work on the other aircraft, replacing FS98 gauges with FSX default gauges or other gauges that work in FSX. (For example replacing some of the gauges in Steve Grant's Otter with gauges from the default FSX Beaver.)As far as using a path outside the FSX folder, you do that using something like this:SimObjectPaths.6=..Flight Simulator 9AircraftThe .. means "the folder above this folder" to Windows and dates back to the DOS days."Let me help you out. You're cleared to taxi any way you can to any runway you see."