I spent today confirming this - but every time I fly KSFO to KSEA, between BTG and the Olympia VOR in the NGX, the sim freezes just before the Olympia. I also set up a quick flight from KEUG to KSEA manually and it happened again - this time using the heading tool to get me to BTG then to the Olympia VOR. I flew from Vancouver to KSEA - no probs. I've been flying CYYZ to CYXU with default scenery for training - no probs. Thoughts? If I have time this weekend I'll turn off the ORBX and see how it works. Does anyone know how to uninstall completely the ORBX stuff then reinstall? There is no uninstaller as far as I can tell. Thanks! Colin Ware

I spent today confirming this - but every time I fly KSFO to KSEA, between BTG and the Olympia VOR in the NGX, the sim freezes just before the Olympia. I also set up a quick flight from KEUG to KSEA manually and it happened again - this time using the heading tool to get me to BTG then to the Olympia VOR. I flew from Vancouver to KSEA - no probs. I've been flying CYYZ to CYXU with default scenery for training - no probs. Thoughts? If I have time this weekend I'll turn off the ORBX and see how it works. Does anyone know how to uninstall completely the ORBX stuff then reinstall? There is no uninstaller as far as I can tell. Thanks! Colin Ware

you be better going the orbox forum and posting this problem since i have got all of the orbox scenery and i have no problems, there a thread in the orbox about this type of error and there has been no solution to it as of yet. As of uninstalling the orbox stuff theres a pinned thread in the orbox forum on how to remove and reinstall make sure you read it carefully

I concur,I get the CTDs 100% of the time approaching YXX from YYC Departing BFI, YYJ, YVR, YXX to YYC. 50% in the climbout of YYC as well as in the decent into YYC on 3 out of 4 published STARS. Aproaching YVR from various directions is also just as bad. Quite a pain when the airline I simulate the most is based in YYC, and the western part of canada is its stomping ground. When flying in these areas im getting about a 40% flight completion rate. When not in these areas im at 100%. I can confirm 100% of my CTDs are caused by ORBX. I get them quite often and have to avoid those scenery areas in the NGX. What makes me bitter, is they had a quite popular thread about these issues, and instead of helping the customers with this issue, they let them attempt various solutions that the customer could come up with. And then when everyone including myself suggested that it was perhaps time to just be done with the scenery they shut it down, locked it and suggested that its the customers problem with overstressing the sim. The only thing they could offer as advice was decreasing LOD_Radius to default, not using *******'s tweaks, upgrading the higher end PC's and overclocking the sim. Problem is most of us have done all the above and still can come up with a ORBX CTD on a consitant basis. Concidering my PC specs I took that as a huge slap in the face. As they stated they are not interested in entertaining the idea that something within their product causes this. Disable the scenery and the problems go away. For some reason they dont understand that. Good luck, I hope this gets fixed one day.

I concur,I get the CTDs 100% of the time approaching YXX from YYC Departing BFI, YYJ, YVR, YXX to YYC. 50% in the climbout of YYC as well as in the decent into YYC on 3 out of 4 published STARS. Aproaching YVR from various directions is also just as bad. Quite a pain when the airline I simulate the most is based in YYC, and the western part of canada is its stomping ground. When flying in these areas im getting about a 40% flight completion rate. When not in these areas im at 100%. I can confirm 100% of my CTDs are caused by ORBX. I get them quite often and have to avoid those scenery areas in the NGX. What makes me bitter, is they had a quite popular thread about these issues, and instead of helping the customers with this issue, they let them attempt various solutions that the customer could come up with. And then when everyone including myself suggested that it was perhaps time to just be done with the scenery they shut it down, locked it and suggested that its the customers problem with overstressing the sim. The only thing they could offer as advice was decreasing LOD_Radius to default, not using *******'s tweaks, upgrading the higher end PC's and overclocking the sim. Problem is most of us have done all the above and still can come up with a ORBX CTD on a consitant basis. Concidering my PC specs I took that as a huge slap in the face. As they stated they are not interested in entertaining the idea that something within their product causes this. Disable the scenery and the problems go away. For some reason they dont understand that. Good luck, I hope this gets fixed one day.

i must be one of the lucky one since i havnt had any ctd in this area at all

It may not be the scenery in itself. Sounds like you are running out of memory.The easy way to test for that is to see if the default FSX planes also ctd there.If not, the scenery is probably OK. If it still crashes.. :( The scenery is the issue.I imagine the combo of the dense scenery, and the NGX is quite a load..Heck, until I switch to Win7 64, I can't even run the default FSX scenery at maxsliders without eventually running out of memory.I dunno why they would say to overclock. That would have no effect on the issue.All that does is improve loading times, and frame rate. Nothing else..Sure won't cure memory issues.

Here is a thought :- You fire up FSX, and go to select the PMDG 737, from the mass of aircraft and helicopters you have in your FSX.You see them all in your selection menu -- so, they are ALL loaded into FSX !!! What would happen if you temporarily removed all the aircraft except the ONE PMDG 737 you wanted to fly, from your FSX. ? Might this reduce the amount of memory that FSX is using, holding all those aircraft ?? May, may not -- not tried it -- but it might be worth thining about all the unwanted stuff that may be loaded in FSX, that you do not need. Certainly, if you have GA & Airline AI traffic turned on, those planes are loaded and taking up memory. Maybe the reality is, one just "CANNOT HAVE IT ALL"

<< PMDG 737NNGX User's Theme song ??? If so, its up to YOU to decide what is important to you - AI Aircraft, Addon Scenery, High Autogen, "Not Crashing with an OOM" etc etc A 64 Bit Flight Sim would certainly help. FSX is stuck at 32 bit, P3D is 32 bit and will take a lot to make it 64 bit, which leaves the Mysterious "MS FLIGHT". Will there be a 64 bit version of MS Flight, that one will be able to run the PMDG 737NGX in ??( Like asking what the Megga Million Lottery numbers will be for next weekend's drawing !! )

Thanks all for your replies. I'll move over to the ORBX forums later. It's not memory and it's not overheating - the computer has no idea where I am flying - and I monitored both on my last flight. It is definitely something in the scenery. It's the only thing that makes any sense at all. Thanks. Colin Ware

Thanks all for your replies. I'll move over to the ORBX forums later. It's not memory and it's not overheating - the computer has no idea where I am flying - and I monitored both on my last flight. It is definitely something in the scenery. It's the only thing that makes any sense at all. Thanks. Colin Ware

I disagree with you. I believe it's memory. PMDG themselves mentioned that freezes are mostly due to memory issues and for now the course of action (besides the hotfix) is to lower autogen and/or scenery settings. Hopefully you've tried the same scenarios in different aircraft. Namely other complex add on aircraft. You said you can reproduce the freeze, but you haven't gone through a deductive test by changing settings, aircraft, etc. Yet you claim that you know what the problem couldn't be.

It's not memory - its a dll problem. I looked it up in the event log. And it happens in the same place every time. This is a "fatal error FSX is restarting" crash, not technically a freeze. Colin

It's not memory - its a dll problem.  I looked it up in the event log.  And it happens in the same place every time.   This is a "fatal error FSX is restarting" crash, not technically a freeze. Colin

Just try what I mentioned  in my post before you make that claim.  Lower autogen and scenery and try the approach.  Also change the texture_max_load in your .cfg to 1024.

Maybe this applies to you, too: http://forum.avsim.net/topic/347148-olm7-arrival-ksea-ctd-with-orbx/page__hl__ksea+vashon__fromsearch__1

Maybe this applies to you, too: http://forum.avsim.n...__fromsearch__1

I took a look at that thread and indeed it looks interesting enough for me to try a flight into KSEA and see if FSX crashes. If it does, then i will see if disabling ORBX Vashon Strip works. Incidentally, the only crash i have ever had was approaching KPDX with ORBX PNW and their downtown Portland freebe installed. Didn't think much of it because it was my first test flight after purchase of NGX and i hadn't even finished setting up my rig.