Hey guys, unknown whether this topic has been brought up before. I recently installed a clean install of fs9.1 and installed some of my addon scenery. I then installed Flightscenery KPDX and Flytampa KSEA. I also have ultimate terrain and have installed the UT patch. I now get a CTD upon loading either KSEA or KPDX. I have never run into this problem before with other re-installations. The FlightZone website is down, so I thought I would try my luck here. If anyone can help or knows a fix for this problem I would be very thankful.L.P

Firstly, you need to add the scenery to your simulator from the 'addon scenery' folder.Secondly, if your still getting problems, check your 'scenery.cfg folder and check that the numbers run consequtively and that there is no sceneries with the same number as others. This is the most common cause for CTD's. Your system sometimes gives false numbers.Good luck. ;)

While I have doubts that your scenery.cfg is causing your problem, I suggest that you do not attempt to manually straighten out any layer or area entries. It is just easy too mess things up.I use, and highly recommend a small utility by Steve Greenwood which will do the job automatically and safely. (It works in FS2004 and FSX also). :( http://home.earthlink.net/~smgreenwood/resources-g.shtml It is the third item down in the list.Read the documentation carefully - the exe file must be in the same folder as your scenery.cfg file is. A backup of your scenery.cfg file is always made before the program works it's magic.I run it once a week and it keeps my scenery.cfg well organized.Hope that is helpful. :(

Thank you so much for the replies. David I will try that link and post the outcome.L.P.

Since you are getting a CTD at Seattle also have you tried looking at the Fly Tampa forums? Maybe someone has had this problem and asked about it over there?

Hey guys, I just wanted to say that I still get the error. David, I liked the utility you suggested and used it to no avail. I ended up disabling KPDX and noticed the CTD went away. There's obviously a problem with Flightscenery KPDX. The only way I can load KPDX is after loading loading a default flight from Meigs Field. Wierd. Can't figure why it won't load initially and why ie causes CTD to KSEA when it is enabled.There has to be a fix somewhere for this. Hope someone can help...L.P.

There is a PDX Landclass file that is needed for PDX and FT SEA to work together. Since FZ website is down, I have no idea of how to get that file. I have had to do a fresh re-install of Fs9 myself and I need that file too. Just make sure that PDX is on a higher level in your add-on scenery library in FS. With PDX being high quality photoscenery it needs to be on the highest level. With doing this, you should be able to fly just fine from PDX to SEA. If you try SEA to PDX you should get a CTD half way through the flight, just right about when you're crossing HELNS intersection. Hope this helps. Hopefully FZ website gets back online!

Thanks for your response Matt. I'll try and hunt around for the fix. If anyone who reads this has what Matt's talking about, can you be so kind as to help.....ThanksL.P.

I have UT, FT Seattle, and FZ02 KPDX installed and have no issues whatsoever and I never installed any PDX landclass file unless it was part of the FZ02 UT upgrade. I've done dozens of flights between SEA and PDX with no problems and no crashes. You mentioned the "UT Patch", what exactly is this? Are you talking about the official "Compatibility upgrade for Ultimate Terrain USA" (FZ02-UTUSA.zip) for use with FZ02 KPDX that was available from the Flightscenery site or the UT USA v1.3 patch (UtUsaPatchV130.exe) from the Scenery Solutions UT site?It's a frickin' mess, that's for sure and it gets worse when you add Holger's Columbia River Gorge package on top of it all. There's an FZ02 compatibility upgrade and a UT compatibility upgrade for that too. I have it all working together so it can be done.Jim

I have UT, FT Seattle, and FZ02 KPDX installed and have no issues whatsoever and I never installed any PDX landclass file unless it was part of the FZ02 UT upgrade. I've done dozens of flights between SEA and PDX with no problems and no crashes. You mentioned the "UT Patch", what exactly is this? Are you talking about the official "Compatibility upgrade for Ultimate Terrain USA" (FZ02-UTUSA.zip) for use with FZ02 KPDX that was available from the Flightscenery site or the UT USA v1.3 patch (UtUsaPatchV130.exe) from the Scenery Solutions UT site?It's a frickin' mess, that's for sure and it gets worse when you add Holger's Columbia River Gorge package on top of it all. There's an FZ02 compatibility upgrade and a UT compatibility upgrade for that too. I have it all working together so it can be done.Jim

I only have PDX installed and it gives an CTD when descending into the area. I came from Mt. Rainier and got the crash when I descended to 3800. I flew with PMDG 737. A search for the bug learnt that more people are having problems with this scenery. I managed to find a thread in the FlightScenery with Google cache dated 2006 on the problem. It sucks, and I would be thrilled to have it solved! I flew five hours from BOS twice to found out I couldn't finish my flight.

Jim, I too have run them all with no issues prior to recently doing a clean install of fs9.1. Afetr my clean install, I started having problems, so i do know what it feels like to fly from KSEA to KPDX without any issues. That's wy I'm so frustrated. Aside from a clean re-install of fs9.1 nothing on my system had changed, It's really annoying. I have the Flightscenery KPDX UT patch which removes the UT roadways in FT KSEA from the water. The only way, as I said before, to go directly to KSEA is to uninstall Flightscenery KPDX. I don't want to do that but I might have to. If there is another patch that I need I would be interested if you have it.L.P.

Well I thought I'd do a "dir" of some of my scenery folders that might affect FZ02, FT KSEA, etc. so you could have a look and maybe gain a clue to what's wrong but it's such a mess I doubt you'll be able to make head nor tail of it. It's a damn wonder any of this works at all. If I had to fix something in this mess I'm afraid the only way to do it would be to delete my Flight Simulator 9 folder and start over :( .Anyway, here it is. I pasted my Scenery.cfg in first so you could check priorities, and then I added the directories one by one after that. Maybe if you open it with a text editor and use "find" to search out "FZ02" you can find a .bgl that's been deactivated on mine where it's still active on yours or something. Here it is:FZ02.zipDon't know of any other patches or updates but I have copies of everything I've downloaded if you find you're missing something that's not available anymore.Hope that helps,Jim

Hey thanks Jim. As I write this, I'm doing another clean install of fs9, so I hope this scenery works this time around. We'll see. I also took a look at your fs9.cfg, I remember when mine use to look like that not too long ago.I'll try starting from scratch and see what I come up with.Lyndon

Finally found a solution through trial and error, and it's so simple. Apparently my set up did not like the disabling or romoving of the traffic.bgl file. Anyone know of a modified traffic.bgl, which reduces or eliminates the default ai traffic or should I use ttools? Thanks in advanceL.P.

why not just alter the setting?