OK, I found another scenery.cfg in my fs9.cfg folder. I removed the 1st one I found and the game didn't load. Should I delete the other (FS9.cfg)? Neither of them have the fly tampa cfg's so I don't know where they're going when I install....

I've found some more scenery's....scenery program files Microsoft Games FS 9. 9.1 and OLD scenery. What do I need to get rid of?

J...Here's the first thing you should do...Go into your registry and find the following key...HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0\EXE Path\???Which ever value is where the ??? should be the path to the Scenery.cfg you're going to want to keep...it's the one FS9 is using. All other Scenery.cfg files can be deleted or better, moved to a safe location in case you want to pull a value from them later. You can take a look in the folder and verify that it is the proper path to your FS9 install too. The Scenery.cfg file should be there as well as the FS9.exe etc...After you've done that, it gets a bit more complicated. At some point in time you're going to either have to know what you've got installed or find what you've got installed. The sceneries have to get into the Scenery.cfg file...and...I know I'm stating the obvious but it might be easier if we work through it this way. But you're lucky you're working through this now and because both the FlyTampa and ImagineSim installs are really straight forward and self contained. Hat's off to both scenery designer's for that fact!So in the same folder that you've got the working copy of Scenery.cfg, (which you found in step 1 with the registry key), you have a folder named "Addon Scenery". That is where all of the sceneries installed themselves...I think. You can verify this fact by simply navigating to the "Addon Scenery" folder in Windows Explorer and looking and counting. Look at all of the scenery folder names and count how many there are of them. If the scenery folder names and count match the number of sceneries you've installed then you've found all of your installs.OK, let's recap. Hopefully at this point you know where your working copy of the Scenery.cfg file is, you know that it is in the same folder as your FS9.exe, you've found all of you aftermarket scenery installs, and now...The next step is to verify that all of the after market FlyTampa and ImagineSim sceneries are in your Scenery.cfg file and have only one Scenery Block entry for each scenery. The proper way to verify this would be to check the "Local=" entry in the scenery block. The "Local" entry is the Windows folder path to your scenery. You should not have any "Local=" path duplicated for the sceneries that you've installed. If you have 2 entries with the same "Local=", even if they have a different "Title=", then one of them must go. Important *** Remember, there a many entries in the Scenery.cfg file that are not part of your FlyTampa or ImagineSim installs. They are default Microsoft FS9 sceneries and objects or possibly other sceneries that you forgot to mention here. So the following information is important...read on...The last scenery block for the Microsoft default stuff is...[Area.038]Title=Addon SceneryLocal=Addon SceneryLayer=38Active=TRUERequired=FALSEAfter this block, you can start entering the sceneries that you've installed. The next block could be...[Area.039]Title=FSDreamTeam Fort Lauderdale-HollywoodLocal=FsDreamTeam\KFLLActive=TRUERequired=FALSELayer=039[Area.040]Title=Imagine Simulation - KCLT CharlotteLocal=Imagine Simulation\KCLT CharlotteRemote=Required=FALSEActive=TRUELayer=40Flatten.0=748,N35 14.01,W80 57.56,N35 14.01,W80 55.40,N35 11.68,W80 55.40,N35 11.68,W80 57.56[Area.041]Title=Imagine Simulation - KATL AtlantaLocal=Imagine Simulation\KATL AtlantaRemote=Required=FALSEActive=TRUELayer=41[Area.042]Title=Imagine Simulation - KDTW DetroitLocal=Imagine Simulation\KDTW DetroitRemote=Required=FALSEActive=TRUELayer=42Flatten.0=646,N42 14.70,W83 23.69,N42 14.70,W83 19.29,N42 11.14,W83 19.29,N42 11.14,W83 23.69*** Now note how the Area and Layer numbers are ascending as you add sceneries to the Scenery.cfg file. If you were to add another scenery to this list the Area and Layer number would be 43. Just make sure that the path that the "Local=" is pointing to is unique for the FlyTampa and ImagineSim airports in the entire Scenery.cfg file...there can't be 2 or you will have duplicate scenery entries and hangers hanging out of control towers and the like!Mark

J...Here's the first thing you should do...Go into your registry and find the following key...HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0\EXE Path\???Which ever value is where the ??? should be the path to the Scenery.cfg you're going to want to keep...it's the one FS9 is using. All other Scenery.cfg files can be deleted or better, moved to a safe location in case you want to pull a value from them later. You can take a look in the folder and verify that it is the proper path to your FS9 install too. The Scenery.cfg file should be there as well as the FS9.exe etc...After you've done that, it gets a bit more complicated. At some point in time you're going to either have to know what you've got installed or find what you've got installed. The sceneries have to get into the Scenery.cfg file...and...I know I'm stating the obvious but it might be easier if we work through it this way. But you're lucky you're working through this now and because both the FlyTampa and ImagineSim installs are really straight forward and self contained. Hat's off to both scenery designer's for that fact!So in the same folder that you've got the working copy of Scenery.cfg, (which you found in step 1 with the registry key), you have a folder named "Addon Scenery". That is where all of the sceneries installed themselves...I think. You can verify this fact by simply navigating to the "Addon Scenery" folder in Windows Explorer and looking and counting. Look at all of the scenery folder names and count how many there are of them. If the scenery folder names and count match the number of sceneries you've installed then you've found all of your installs.OK, let's recap. Hopefully at this point you know where your working copy of the Scenery.cfg file is, you know that it is in the same folder as your FS9.exe, you've found all of you aftermarket scenery installs, and now...The next step is to verify that all of the after market FlyTampa and ImagineSim sceneries are in your Scenery.cfg file and have only one Scenery Block entry for each scenery. The proper way to verify this would be to check the "Local=" entry in the scenery block. The "Local" entry is the Windows folder path to your scenery. You should not have any "Local=" path duplicated for the sceneries that you've installed. If you have 2 entries with the same "Local=", even if they have a different "Title=", then one of them must go. Important *** Remember, there a many entries in the Scenery.cfg file that are not part of your FlyTampa or ImagineSim installs. They are default Microsoft FS9 sceneries and objects or possibly other sceneries that you forgot to mention here. So the following information is important...read on...The last scenery block for the Microsoft default stuff is...[Area.038]Title=Addon SceneryLocal=Addon SceneryLayer=38Active=TRUERequired=FALSEAfter this block, you can start entering the sceneries that you've installed. The next block could be...[Area.039]Title=FSDreamTeam Fort Lauderdale-HollywoodLocal=FsDreamTeam\KFLLActive=TRUERequired=FALSELayer=039[Area.040]Title=Imagine Simulation - KCLT CharlotteLocal=Imagine Simulation\KCLT CharlotteRemote=Required=FALSEActive=TRUELayer=40Flatten.0=748,N35 14.01,W80 57.56,N35 14.01,W80 55.40,N35 11.68,W80 55.40,N35 11.68,W80 57.56[Area.041]Title=Imagine Simulation - KATL AtlantaLocal=Imagine Simulation\KATL AtlantaRemote=Required=FALSEActive=TRUELayer=41[Area.042]Title=Imagine Simulation - KDTW DetroitLocal=Imagine Simulation\KDTW DetroitRemote=Required=FALSEActive=TRUELayer=42Flatten.0=646,N42 14.70,W83 23.69,N42 14.70,W83 19.29,N42 11.14,W83 19.29,N42 11.14,W83 23.69*** Now note how the Area and Layer numbers are ascending as you add sceneries to the Scenery.cfg file. If you were to add another scenery to this list the Area and Layer number would be 43. Just make sure that the path that the "Local=" is pointing to is unique for the FlyTampa and ImagineSim airports in the entire Scenery.cfg file...there can't be 2 or you will have duplicate scenery entries and hangers hanging out of control towers and the like!Mark

I deleted any scenery cfg file I could find and reinstalled it again and it's still screwed up. I'm about to stop playing this.....I'm not technical enough to pick through all these files to try and figure it out....ugh

When you reinstalled, did you manually delete ALL of the files that're stored in the Users/AppData folder?If not, you are simply making a bigger mess. In fact, you should NOT be "reinstalling" FS9 at all, as there's absolutely no reason to!Go find your scenery.cfg file, delete it, and allow FS9 to build a fresh copy with only the default scenery configured.Now start adding in your addon scenery, one at a time, testing in between for correct behavior.

where is the users/appdata folder located? I tried to delete everything off my computer that had to deal with FS2004 and reinstalled again and it still doesn't work right.....When I look in my scenery.cfg folder in the FS9 folder none of the fly tampa airports are showing up. When I do a search of the scenery.cfg files on my cpu, that file and the FSX one only shows up. The installer is checked for adding the scenery to the database, so where is it going?

I am running XP (as are others reading this). I moved my scenery.cfg and oldscenery.cfg out of the main FS9 folder and FS9 would not start.

Of course it wouldn't start! The scenery.cfg file in the main FS9 folder is the template copy!When you first start FS9, one of the first operations of FS9 is to create fresh "working copies" of the fs9.cfg and scenery.cfg files. Under WinXP, the scenery.cfg (working copy) should be here:C:\Documents and Settings\All Users\Application Data\Microsoft\FS9To "repair" a scenery.cfg file, try Steve Greenwood's utility program: http://www.home.earthlink.net/~smgreenwood...s/fsscenery.zip