I've even gone so far to delete it all and start over again. I've never has so many problems with FS9 in my life. It makes no sense to me now when I install fly tampa's San Fran, it makes the fly tampa Seattle take some of the default sceney back i.e. hangars and gates. Same thing is happening with my imagine simulation files. FSDreamteam and Mach 1 files are fine...It's like whatever of the two paywares I put in last will override their companions....FS9.1 is installed too....

Well, it can't be that bad! When was the last time you took a look at your scenery.cfg file...is it a mess? It sounds like it. Which Imagine Sim airports do you have installed? Below is a little info on the FlyTampa airports...The KSFO installs an effects file named flytampa_fountain.fx and that's the only piece of scenery that's not contained in the KSFO folder.The KSEA install can be a bit more complex if you've selected the flatten modification or you selected it and the installer messed up. Other then the flatten modification, all of the other scenery files are contained within the KSEA folder. A search of the folder below should yield 2 files if you've elected the flatten modification or it was done automatically on your behalf :)Search...Flight Simulator 9\Scenery\Namw\Scenery\FL915150*Results...(Maybe)FL915150.oriFL915150_flytampa_mod.bglMark

Well, it can't be that bad! When was the last time you took a look at your scenery.cfg file...is it a mess? It sounds like it. Which Imagine Sim airports do you have installed? Below is a little info on the FlyTampa airports...The KSFO installs an effects file named flytampa_fountain.fx and that's the only piece of scenery that's not contained in the KSFO folder.The KSEA install can be a bit more complex if you've selected the flatten modification or you selected it and the installer messed up. Other then the flatten modification, all of the other scenery files are contained within the KSEA folder. A search of the folder below should yield 2 files if you've elected the flatten modification or it was done automatically on your behalf :)Search...Flight Simulator 9\Scenery\Namw\Scenery\FL915150*Results...(Maybe)FL915150.oriFL915150_flytampa_mod.bglBoth of those showed up. I'm at a loss.....If I install the San Diego scenery, it shows up perfect, now if I go back and install San Fran, it will be fine but mess San Diego up. Same goes with SeaTak....Mark

btw I think I got the imagine airports right. I deleted and reinstalled the files and I think it fixed the config settings....I did the same with fly tampa but no good...besides the scenery folder where I found those 2 other files, where can I see the other settings??

Are you installing your sceneries one at a time?Starting FS9, adding the scenery to the library (if Needed). Shut down FS9 and restarting?What order are you installing?

Are you installing your sceneries one at a time?Starting FS9, adding the scenery to the library (if Needed). Shut down FS9 and restarting?What order are you installing?

I've tried it at the same time, one at a time it all ends up the same, whichever is the last one I install will work. The other ones mix back with the default textures. It's like the seatak , after I install San Fran it will have the default hangar sticking through the alaska airline hangar and the default games mixed in with the modded ones, and 2 control towers..... I got the imagine, fsdreamteam and cloud 9 working right now. Fly Tampa is giving me hell.....

It almost sounds as if you've got duplicate scenery.cfg entries for the same scenery. For instance, you should only have one scenery entry/block for KSFO...[Area.50] Title=FlyTampa San FranciscoLocal=Addon Scenery\FlyTampa\San FranciscoRemote=Active=TRUERequired=FALSELayer=50If you see another scenery block that has the same "Title" and "Local" but has a different "Area" and/or "Layer" number then it should be removed and only one should be kept. I try to keep my "Area" and "Layer" numbers the same as you should note from the scenery block above.Repeat, there should only be one scenery block for both the FlyTampa KSFO and KSEA airports. As I remember, there aren't any "Landclass" scenery files with the ImagineSim airports I've seen. So most likely their should be only be one scenery block for each of those airports too....probably. If you run into any issues with multiple scenery blocks for the ImagineSim stuff, post the airport ICAOs here as I'm sure someone will know if it's correct or not.Mark

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.

Jracer,You are having the worst luck lately with FS9 it seems. And a lot looks to be texture or scenery related. I really don't have a solution, but n4gix's point about making sure all the files are deleted in the Program Files folder is important.I have seen this problem with my Seoul Add-on scenery and the Overland RKSI airport. I had some objects overlapping. All I had to do was reorder them in the scenery library. That is all I know to help.

Go find your scenery.cfg file, delete it, and allow FS9 to build a fresh copy with only the default scenery configured.

Did you mean FS9.cfg?FS9 will not start without a scenery.cfg.Better to backup your existing scenery.cfg and extract the original file from your FS discs. They are located on disc #4, there are 2 of them. One for a full install and one for a compact install.regards,Joe

Mark, I looked in the cities/san fran folder and I see one fly tampa bgl file. Where is this area.50 file? I did look in my fs9 config and it appears that I have 2 config files. Would this cause that problem??

Did you mean FS9.cfg?FS9 will not start without a scenery.cfg.

No, I meant what I wrote. If you are running Vista or Win7, the "working copy" of the scenery.cfg file is kept in the User's AppData Roaming folder:K:\Users\Bill\AppData\Roaming\Microsoft\FS9\scenery.cfgThe "stock" scenery.cfg file is in the root folder of FS9:L:\FS9\scenery.cfgWhen loading the sim, if the "working copy" of scenery.cfg file is missing, FS9 will copy the stock scenery.cfg file to the User's AppData Roaming folder.If you are running WinXP, the same applies but the absolute path to the "working copy" is slightly different.Whatever the case, you MUST manually delete the "working copies" of all .cfg files, because they are NOT removed automatically during an uninstall... :(

If you are running WinXP, the same applies but the absolute path to the "working copy" is slightly different.

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.Can't speak for Vista or 7, but it will not work in XP.

Whatever the case, you MUST manually delete the "working copies" of all .cfg files, because they are NOT removed automatically during an uninstall... :(

Agreed.regards,Joe

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.Can't speak for Vista or 7, but it will not work in XP.Agreed.regards,Joe

Never mind....

It almost sounds as if you've got duplicate scenery.cfg entries for the same scenery. For instance, you should only have one scenery entry/block for KSFO...[Area.50] Title=FlyTampa San FranciscoLocal=Addon Scenery\FlyTampa\San FranciscoRemote=Active=TRUERequired=FALSELayer=50If you see another scenery block that has the same "Title" and "Local" but has a different "Area" and/or "Layer" number then it should be removed and only one should be kept. I try to keep my "Area" and "Layer" numbers the same as you should note from the scenery block above.Repeat, there should only be one scenery block for both the FlyTampa KSFO and KSEA airports. As I remember, there aren't any "Landclass" scenery files with the ImagineSim airports I've seen. So most likely their should be only be one scenery block for each of those airports too....probably. If you run into any issues with multiple scenery blocks for the ImagineSim stuff, post the airport ICAOs here as I'm sure someone will know if it's correct or not.Mark

[Area.040]Title=FSDreamTeam Fort Lauderdale-HollywoodLocal=FsDreamTeam\KFLLActive=TRUERequired=FALSELayer=40[Area.041]Title=Imagine Simulation - KCLT CharlotteLocal=Imagine Simulation\KCLT CharlotteRemote=Required=FALSEActive=TRUELayer=41Flatten.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.042]Title=Imagine Simulation - KATL AtlantaLocal=Imagine Simulation\KATL AtlantaRemote=Required=FALSEActive=TRUELayer=42[Area.043]Title=Imagine Simulation - KDTW DetroitLocal=Imagine Simulation\KDTW DetroitRemote=Required=FALSEActive=TRUELayer=43Flatten.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.69Now the flytampa installer said that it updated the cfg but none of those scenery's are shown in here.....

No, I meant what I wrote. If you are running Vista or Win7, the "working copy" of the scenery.cfg file is kept in the User's AppData Roaming folder:K:\Users\Bill\AppData\Roaming\Microsoft\FS9\scenery.cfgThe "stock" scenery.cfg file is in the root folder of FS9:L:\FS9\scenery.cfgWhen loading the sim, if the "working copy" of scenery.cfg file is missing, FS9 will copy the stock scenery.cfg file to the User's AppData Roaming folder.If you are running WinXP, the same applies but the absolute path to the "working copy" is slightly different.Whatever the case, you MUST manually delete the "working copies" of all .cfg files, because they are NOT removed automatically during an uninstall... :(

I have one scenery cfg file for fs9.....

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....