Hey guys,I've had quite some time of investigation in a problem with the fantastic OrbX PNW scenery.In short:Using "complex" planes (A2A (Piper), Flight1 (Mustang), PMDG (MD11, 747X), FSLabs (Concorde X) and Carenado (Bonanza) so far) at or around Seattle (KSEA) leads to nearly reproducibly crashes ("fatal error") of FSX and I want to find out which configuration triggers this behavior as this might happen on some systems and on many others not.As I'm currently updating a thread in the FTX forums, I'm looking for some other people that have constant instabilities at and around this area. Found another one so far, but there might be more to come.See this thread at FTX (might need registration, but it's free of course)http://orbxsystems.com/forums/index.php?topic=23872.0Current status is (and was achieved with the help of the friendly FTX stuff), that disabling PNW or just one folder of it "solves" the problem as the crashes doesn't occur then.Big question is, what files in that folder are causing the trouble and why this only happens with the mentioned complex aircraft and e. g. not with FSX standard or other addons.There isn't just one "faulty" file but a combination of them. See my search for it in the FTX thread if your're interested.Things like clean fsx.cfg, disabled AV and checked loaded .dll files are already tested.Help and information is appreciated and of course you don't have to post at FTX if you don't want to.

System specs?Scenery/Autogen settings?Things like clean fsx.cfg, disabled AV and checked loaded .dll files are already tested.Help and information is appreciated and of course you don't have to post at FTX if you don't want to.

what about adding the highmem=1 line to the fsx.cfg file? searching for duplicate afcad files?

Ah, sorry ... as we are currently two guys the system specs loose their significance a bit.Both are on W7, 64bits, i7 at 4GHz+, settings from dense (autogen) to extr. dense (scenery complexity). I'm using a GTX275.Full details are in the FTX thread, also screenshots of the locations where the crashes usually happen.As I've tried various settings with especially autogen, water, clouds and so on and always receive a crash with enabled PNW, I think it's really related to this one folder inside its numerous scenery entries and not to the settings in FSX.Rest of the area (even the other dense ones) are working fine."FTX_NA_PNW05_SCENERY" enabled and your're a CTD target so far when flying the mentioned aircraft around KSEA. In fact, that's the one folder that triggers the crashes.Software setup is current. Meaning I've tried the last 4 final Nvidia drivers (257.21 currently running), have my PNW patched to 1.2 and going on flights with current service packs on e. g. the Concorde (SP2) or the older MD11 (1.2) and 747 (2.1). FSX is SP2 Acceleration, REX, ASE SP1, FSGlobal2010 SP1, UT2 (offline), FSInn (online) ... all working fine in the rest of the world. Go to KSEA with those aircraft and you'll loose FSX.Although help is really appreciated this is more some "who else has this problem thread". Hoping to find more people on this so that the devs get some input from various pilots instead of just two.I myself tried it with vanilla and tweaked fsx.cfg, meaning of course the ******* stuff including highmem.Duplicates are a good point ... I have no other scenery installed in this area except the CYYJ (2010) Freeware, Version 5.04 which is PNW compatible.I've also checked for duplicates with AFX demo, except the FSX stock airports there's nothing active.

Hey guys,I've had quite some time of investigation in a problem with the fantastic OrbX PNW scenery.In short:Using "complex" planes (A2A (Piper), Flight1 (Mustang), PMDG (MD11, 747X), FSLabs (Concorde X) and Carenado (Bonanza) so far) at or around Seattle (KSEA) leads to nearly reproducibly crashes ("fatal error") of FSX.Help and information is appreciated and of course you don't have to post at FTX if you don't want to.

FWIW, I have PNW scenery with latest updates and have flown the PMDG 747 and Carenado Mooney and PA-34 Seneca into Seattle (and in and around KSEA), and no crashes.Best regards,Jim

Ok, I hope not everyone with a working configuration now starts posting ... :( But thanks for the information and correction on my intentions: This is no complain about an error coming up on every system, but maybe on some (not just mine). I've corrected my first post on this, wasn't written very clear, sorry for that.So maybe you have some information about your installed addons so I can rule out some possible sources.Are you using FSGlobal for example?

Have you uninstalled/reinstalled PNW?

Do you have any Traffic addon installed?Try disabling it.

Yes, Sir. No change here. Entries in the scenery library are just fine, FTX Central reports no problems. It's even working fine (and looking great) when you use other planes as the mentioned ones.I have no idea how the complexity of some planes (e. g. Concorde X crashes, SimCheck A300 does not, never) refers to PNW at or around KSEA. There's another pilot at the FTX forums, using the Flight1 Mustang and PNW kicks him almost every time.Traffic is on when flying offline (UT2, showing "current" in the config screen) and off when online (sliders in UT to 0, disabled traffic, FSX sliders to 0 and the exe from UT doesn't get loaded). I even tried that zero traffic setting in offline mode, so no traffic interfering in one way or the other.I admit: If it comes up that no one at AVSIM or in other forums has this problem, there must be something wrong on two systems out of thousands running PNW. I will therefor stay silent and confident (and disable PNW when flying to KSEA with my beloved planes), but I don't think that only two guys around experience this thing.I also don't think that the standards like e. g. DirectX, fsx.cfg tweaks, scenery settings and maybe some doubled afcads cause this.Just looking for a clue and of course some other people that get this fatal error in this one area of the huge PNW. Fresh thread so far ... let's see what patience brings.Thanks for your help :)Additional information:This mainly happens when approaching from the North to KSEA area (therefor rw 16), overfly of the NOLLA NDB with e. g. Concorde X and your CTD awaits you - again: does NOT happen on all systems, don't get me wrong.PNW is working fine when you disable its "FTX_NA_PNW05_SCENERY" folder which of course is no solution but a proof that a "trigger file" is situated in there.

Yes, Sir. No change here. Entries in the scenery library are just fine, FTX Central reports no problems. It's even working fine (and looking great) when you use other planes as the mentioned ones.I have no idea how the complexity of some planes (e. g. Concorde X crashes, SimCheck A300 does not, never) refers to PNW at or around KSEA. There's another pilot at the FTX forums, using the Flight1 Mustang and PNW kicks him almost every time.Traffic is on when flying offline (UT2, showing "current" in the config screen) and off when online (sliders in UT to 0, disabled traffic, FSX sliders to 0 and the exe from UT doesn't get loaded). I even tried that zero traffic setting in offline mode, so no traffic interfering in one way or the other.I admit: If it comes up that no one at AVSIM or in other forums has this problem, there must be something wrong on two systems out of thousands running PNW. I will therefor stay silent and confident (and disable PNW when flying to KSEA with my beloved planes), but I don't think that only two guys around experience this thing.I also don't think that the standards like e. g. DirectX, fsx.cfg tweaks, scenery settings and maybe some doubled afcads cause this.Just looking for a clue and of course some other people that get this fatal error in this one area of the huge PNW. Fresh thread so far ... let's see what patience brings.Thanks for your help :)

ehm ... what exactly are you trying to say when quoting me completely, crn? :(

You may want to try using the config entry under [sCENERY] to see if there are missing textures or objects that should be loading, but are not. These can cause problems sometime's. I tried around KSEA area and would get this texture that was failing to load called WESTSIM_MASTER-GENERIC_1_LM.BMP, but I was only flying during dusk and dark which would stand to reason that is a LM texture. Here is what the config entry should look like.[sCENERY]// To show alerts or areas, set to = 1 // To hide alerts or areas, set to = 0 // Alert for missing texturesShowMissingTextureAlert=1// Alert for missing objectsMissingLibraryAlert=11 shows the alert, and 0 turns it off. Hope this helps.Bryan Farmer

ehm ... what exactly are you trying to say when quoting me completely, crn? :(

Sorry what I wrote seems to have disappeared into the ether. :-)After installing Vashon Island I found that Seattle airport was corrupted - roads going under the runway and trenches here and there.It was caused by me not installing the latest library files immediately after installing Vashon.OK there was no computer crash but maybe there is some remote connection.I had to restore an image taken before the Vashon install to fix it.CheersClive Norman

Thanks for your tips about the alert and the installation of Vashon and the needed library files, guys.Will try both.

I've done a fresh install of Vashon Island and the library objects and added the alert lines to my fsx.cfg.Here's what I gotI have no idea how to interpret this stuff and of course posted it too in the FTX forums (http://orbxsystems.com/forums/index.php?topic=23872.0).These alerts caused no CTD so far ... it came later at NOLLA NDB, without alerting for something missing there. So those pictures are just taken on my way to my most liked CTD point, approaching KSEA from the NW.