Maybe last update ...Second flight now with autogen to only "normal" - no CTDs. Strange "low" setting to use on that beautiful scenery but I must admit that it brought stability back when flying to KSEA (other areas weren't a problem so far, even on high settings).Thanks to all who helped, quite a few people :(

Glad you might have discovered your problem. Autogen with the slider set to Dense is the recommended setting for your system unless it's overclocked and that's around city/urban areas and Very Dense for the Wilderness areas (this according to the manual). You should try it at those settings and see if you can still fly around without crashing. You had missing scenery objects with higher autogen settings and I think the objects are there but could not be rendered and that caused the crash(es).Best regards,Jim

From the FTX PNW .002 Release notes:"PNW.002 Release NotesThe following lists in detail the changes made with this PNW.002 patch.Bug FixesNew version of KSEA. Note that we have identified "ADE_FTX_PNW_KSEA_Seattle-Tacoma_Intl.BGL", in\FTX_NA_PNW05_SCENERY\scenery, as the file triggering the ai_player.dll crashes when exiting FSX for somepeople . Unfortunately, we've been unable to nail down the actual cause despite many days of debugging andcreating a new KSEA version from scratch. However, we've also reset KSEA to its default elevation so that PNWusers affect by the crashes can deactivate the KSEA files only without leading to odd plateaus."jja

Thanks for quoting ...That's what I've read and thought about a solution to "my" problem. Patch 2 is installed since day one or its release and although the autogen-"normal"-approach seemed promising I just had a CTD again, but the location changed: Still KSEA but south of it now. Event log always shows good ol' g3d.dll which means nearly everything although some people always say "graphics driver".Awaiting the feedback from the other guys how "normal" autogen did on their systems.Thanks again for your help.

Thanks for quoting ...That's what I've read and thought about a solution to "my" problem. Patch 2 is installed since day one or its release and although the autogen-"normal"-approach seemed promising I just had a CTD again, but the location changed: Still KSEA but south of it now. Event log always shows good ol' g3d.dll which means nearly everything although some people always say "graphics driver".Awaiting the feedback from the other guys how "normal" autogen did on their systems.Thanks again for your help.

It seems that the 'trigger' issue causes a 'soundcfg' app error to get logged in Win 7 64bit. It could be a Creative app or service - still digging.jja

First, I have to say thank you again, jjjallen.Because you've posted the patch notes lately I went on and searched for more "KSEA" files to be disabled, as the normal ones in the "FTX_NA_PNW05_SCENERY" weren't culprits at all and btw look extremely good (I like that parked Concorde at Seattle very much, thumbs up for OrbX again).As you can see, I'm still searching a cause to our CTDs. The reduction of the autogen to a quite low setting of only "normal" helped shortly but not long.I'm currently testing another file and had already posted this in the FTX forums.If you are crashing at KSEA and around with the complex aircraft mentioned, this might help you (quoting myself now, quite unappealing, I know)

Forget about all the other tips from me, set up FSX like it was and like it is on scenery where you also love to fly and just do one thing:Go to Scenery\World\Scenery and disable ADE_FTX_PNW_KSEA_elevation_adjustment.bgl

Give that a try if you like and go on with that sound stuff - Creative lost some of its reputation about delivering stable hardware and drivers, especially since Win7. I'm using a X-Fi Fatality (PCI) with modded drivers from Daniel K and despite the good sound on my system there are still some flaws.Feedback on disabling that file would be appreciated, as always. One FTX member already had some good and stable flights and I can tell about some of those too.

just to add:You have to MOVE or DELETE (not recommended) that file because when you switch the FTX modes, it gets renamed from .off back to .bgl and will be active again, so CTDs come back.

First, I have to say thank you again, jjjallen.Because you've posted the patch notes lately I went on and searched for more "KSEA" files to be disabled, as the normal ones in the "FTX_NA_PNW05_SCENERY" weren't culprits at all and btw look extremely good (I like that parked Concorde at Seattle very much, thumbs up for OrbX again).As you can see, I'm still searching a cause to our CTDs. The reduction of the autogen to a quite low setting of only "normal" helped shortly but not long.I'm currently testing another file and had already posted this in the FTX forums.If you are crashing at KSEA and around with the complex aircraft mentioned, this might help you (quoting myself now, quite unappealing, I know)Give that a try if you like and go on with that sound stuff - Creative lost some of its reputation about delivering stable hardware and drivers, especially since Win7. I'm using a X-Fi Fatality (PCI) with modded drivers from Daniel K and despite the good sound on my system there are still some flaws.Feedback on disabling that file would be appreciated, as always. One FTX member already had some good and stable flights and I can tell about some of those too.

Whatever dude! I have been flying error free outside of PNW and will see what happens tonight (if anything) when I land at 1S2.There is no love in messing with the autogen setting. I leave it at normal with a max buildings fsx.cfg switch set to 800.jjajja

Still no more CTDs around Seattle with the disabled elevation file - I'm happy as can be.

Everything was cool flying south of PNW for a day. Flew a hotdog landing into 1S2, everything was looking great and no blurries. Saved my flight. Existed FSX and then a BlueScreen.I'll try the elevation bgl exclusion.jja

Still no more CTDs around Seattle with the disabled elevation file - I'm happy as can be.

Seems to have fixed my BlueScreens also.jja

Glad to hear.Remember to move or delete (not recommended without a backup in another folder) the file because FTX Central corrects every disabling via renaming on a mode switch and therefore re-enables the file.I'm currently into the other elevation files in that mentioned folder as some of you reported CTDs on other places around PNW.Again, this is no regular PNW bug and might also not be a design flaw - the CTD could arise in certain configurations of different addons and extra mesh could be one cause of getting in trouble with the elevation files.I'm no expert on this but I definitely want to make sure that nobody starts to blame those talented FTX guys without looking at the details.

Glad to hear.Remember to move or delete (not recommended without a backup in another folder) the file because FTX Central corrects every disabling via renaming on a mode switch and therefore re-enables the file.I'm currently into the other elevation files in that mentioned folder as some of you reported CTDs on other places around PNW.Again, this is no regular PNW bug and might also not be a design flaw - the CTD could arise in certain configurations of different addons and extra mesh could be one cause of getting in trouble with the elevation files.I'm no expert on this but I definitely want to make sure that nobody starts to blame those talented FTX guys without looking at the details.

I flew all the way through PNW from Darrington to Alaska. Saved, exited FSX, no probs.I dragged the file into my junk folder (c:\temp)Also, there is a reason for all those DirectX, nVidia driver and .Net updates.jja

Hi all- I just posted the same problems over on the Orbyx forums.

Flying happily till I discovered

Carenado and Milviz planes!

Fall City to Vashon Island,Israels Field to Veronia and Cresswell to Darrington particularly difficult flights to complete

Some Autogen reduction allowed flights to be completed but not always.

Some increased flickering around Payware airports too

Can fly all planes over Tongass Fjords!

i5 3570K over locked to 4.5GHz

8GB PC3-10666 1333MHz DDR3 Memory(2x4GB sticks)

Nvidia GeForce GTX 660 2048MB Graphics Card

1000GG Hard Disc-6Gbs

Win 7 Home Premium 64 bit

Hi all- I just posted the same problems over on the Orbyx forums.

Flying happily till I discovered

Carenado and Milviz planes!

Fall City to Vashon Island,Israels Field to Veronia and Cresswell to Darrington particularly difficult flights to complete

Some Autogen reduction allowed flights to be completed but not always.

Some increased flickering around Payware airports too

Can fly all planes over Tongass Fjords!

i5 3570K over locked to 4.5GHz

8GB PC3-10666 1333MHz DDR3 Memory(2x4GB sticks)

Nvidia GeForce GTX 660 2048MB Graphics Card

1000GG Hard Disc-6Gbs

Win 7 Home Premium 64 bit

xxd 09

Hi all- I just posted the same problems over on the Orbyx forums.

Flying happily till I discovered

Carenado and Milviz planes!

Fall City to Vashon Island,Israels Field to Veronia and Cresswell to Darrington particularly difficult flights to complete

Some Autogen reduction allowed flights to be completed but not always.

Some increased flickering around Payware airports too

Can fly all planes over Tongass Fjords!

i5 3570K over locked to 4.5GHz

8GB PC3-10666 1333MHz DDR3 Memory(2x4GB sticks)

Nvidia GeForce GTX 660 2048MB Graphics Card

1000GG Hard Disc-6Gbs

Win 7 Home Premium 64 bit

xxd 09

Apologies for duplicated post!

xxd09