I bought KSEA FT with much anticipation, as I already 5 other FT sceneries. But nothing but issues since I installed it last night and immediately had a major problem, every time I would start FS it would and the instant it load the startup screen CTD, after a number of attempts I new it had to be some thing with the FT KSEA scenery, so I opened the scenery.cfg file and manually disabled FT KSEA. Problem solved or so I thought, FS9 started up just fine I was able to load a flight anywhere with out an issues even default KSEA.
Then I went back into the scenery CFG to see if I could identify the problem, the first then I noticed was that the entery for FT KSEA in the scenery.cfg had a ' : ' before the aera number and layer number
I removed the ' : ', activated the scenery again manually and fired up the sim, viola FS started up just fine, load a flight with the default stat up flight, C172 @ KSEA on the active, immediately I noticed a problem, I had 2 sceneries load simultanously. I exited FS and started my search for duplicate AF2 file, found some in the form of UT AFCADs I removed all duplicate files I could find, loaded up the sim and still the same problem double scenery loaded for KSEA.
I then went into the scenery Lib and found that FT KSEA was at the very bottom of the list, move it up to the number one slot, exited FS, restarted load up default again, this nothing just a couple of default AI sitting in the middle of nowwhere, there was nothing but a flat patch of open land in front of me, no builds, no taxi ways, no runway, nothing. Exit flight, return to scenery lib, now my next problem starts, there are 2 entries for FT KSEA in my scenery Lib, so I delete one and restart fs9, once back in I check the scenery lib nad I notice that FT KSEA has move itself to priority level 164, OK, I load up the default, again duplicate scenery, exit flight, go back into scenery lib, and to my amazement, there are 2 entries for FT KSEA again in the scenery lib.
Now I am confused. I remove both form the scenery lib, close sim, open cfg, manually remove any entries there, restart FS load default flight again, only default scenery, exit, open FS9 again go into scenery lib and manually add the FT KSEA scenery, restat FS, go into default flight, again duplicate scenery, exit back to scenery lib and there are 2 entries again for FT KSEA.
Now I am confused, every time I remove the scenery, add one back start up default flight, exit flight, check scenery lib there are 2 entries for FT KSEA, well so FS is loading a second scenery itself everytime I access the scenery and exit.
When I look into the scenery.cfg, there are 2 entries for FT KSEA, one is
the other is
So my problem in short is this, every time I delete the aera form the Scenery lib (both instances), exit FS, restart, load FT KSEA back again, load default flight or any flight for that matter, I see a duplicate scenery, exit enter lib and find 2 instances of FT KSEA in the scenery lib, when open scenery.cfg ther are 2 entries on with the " aera.16 and "layer=16 and the other random. No matter how many time I delete the aera's in the scenery.cfg and from the scenery lib and from the sceney.cfg manually, open sim, load default flight, exit flight, there ae 2 instances of FT KSE in the scenery lib again, with out me re-adding the scenery in the scenery lib.
And everytime I go into KSEA there is duplicate scenery, if I move the scenery to the highest priority, stat up flight, there is nothing, just a coule of default AI and nothing else.
If I move the entry in the scenery lib that corresponds to the Aera.16 and Layer=16, when I then enter FS again and exit the default flight, it defaults the scenery priority to number 164 and adds a second entry for FT KSEA at 163.
I am at a loss now, I have tried everything I know, but with no solution, always double scenery, always 2 entries in scenery lib, always nothing if I move scenery to higher priority.
I have already tried a uninstall (manual uninstall, no uninstall function) and re-install, no change.
Please help, I would really love to have this resolved.