September 25, 201114 yr I was pulling my short hair out this morning with this one, here's what fixed it for me....Ye ole saved situation problem. Question: Is your NGX saved as part of your default flight that loads with FSX? Mine was. What fixed it for me: Open fsx, and select a DEFAULT aircraft and save to your default flight. Close FSX. You MAY still get the crash when closing FSX. Restart FSX. Load the flight with the default aircraft. Now try switching to NGX. I have not crashed again since doing this, but if they start to occur again, I'll let you know. Thanks for all the other suggestions this morning. Chris Hicks
September 25, 201114 yr nice to hear u got it fixed.happy flying. Intel Q6600 2.4Ghz @ 3.12Ghz (390x8) | 4Gb (2x2Gb) OCZ Reaper 1066Mhz @ 1040Mhz Asus P5K-Deluxe | nVidia 295GTX 1.8Gb | Win7 64bit
September 25, 201114 yr Author nice to hear u got it fixed.happy flying. I appreciate your help this morning, UVW. Chris Hicks
September 25, 201114 yr I applied this fix also. Back in the air with the latest hotfix and all seems to be functioning normally. Ralph Walker
September 25, 201114 yr I thought starting FSX with default aircraft with any complex addon was standard procedure.Also never to start from a saved flight. Regards Luke M
September 25, 201114 yr Author I thought starting FSX with default aircraft with any complex addon was standard procedure.Also never to start from a saved flight. I've had fewer CTDs loading this way than by selecting the aircraft from the menu each time. I save at the end of each flight and get no problems...except today, but not under normal circumstances. Chris Hicks
September 25, 201114 yr I thought PMDG advised NOT to load a default flight before loading the 737ngx. So I always start with free flight and load my Ngx there.jos denis
September 25, 201114 yr You saved my evening...and my grey hair isn`t going to be white:)I had CTD after installing hotfix, never had CTD before...But with this hint to change the default flight, however it took me about an hour to change the default flight because FSX crashed before the new default plan could be saved.... Now FSX is stable with NGX loaded ...Andreas Andreas Riecken Aspire AX3300, Vista 64 bit, 925 quad core 2,8 Ghz, 8GB RAM DDR3, 1TB HDD, ATI Radeon HD4650 graphic with 1024 RAM FSX acc, Microsoft Force feedback joystick, unregistered fsuipc, some scenerie addons, TRACKIR 5, EZDOK,
September 25, 201114 yr Author I'm glad to hear it's working for you. I know technically PMDG recommends against saving it as a default flight, but it works for me in most circumstances and the only times I've had a problem doing so was when I performed maintenance/hotfixes on the plane, so we'll just have to remember this before hand when SP1 comes out so we can swap out a stock plane for our default flight ahead of time! Chris Hicks
September 25, 201114 yr Chris, That worked for me. Thanks a million. I can sped the rest of the day flying instead of tweaking. Ed
September 25, 201114 yr I thought starting FSX with default aircraft with any complex addon was standard procedure.Also never to start from a saved flight. Myself, I start up with a saved flight using the stock Lear 45 at a local airport.Then I decide which 737 to run and load it. Never had any trouble doing that.Myself, I don't really recommend using the NGX as the startup aircraft. It may well work, but.. I don't recommend it..I also don't switch liveries. I've had that cause issues. That's one reasonwhy I like to start up with a default FSX plane. If I decide to run a liverythat I usually don't run, I don't have to double load the NGX to get tothat livery.I run Southwest 95% of the time.. But every once in a while I'll run aContinental 800 or 900 if I want to run a flight that SW doesn't fly to..No matter which I decide, I'm loading a single fresh NGX, and neverhave any problems.My default startup flight plane is the Lear 45. Mark Keith
September 25, 201114 yr Check your aircraft.cfg files and I bet they show the old build number 2922 not the new one, 2987. Your hotfix has not been properly applied. Dennis Trawick Screen Shot Forum Rules
September 25, 201114 yr Author Check your aircraft.cfg files and I bet they show the old build number 2922 not the new one, 2987. Your hotfix has not been properly applied. Who? That's a separate issue. Chris Hicks
Create an account or sign in to comment