User's tweaks causing CTDs with NGX... needs help resolving...

[Brittfrog 3]

houston we got a problem!up till now i have not had many probs with the 737 ngx after realising there was a memory problem when using fsx i managed to trim things so all worked very well , i installed  the last horfix with no apparent changes and still all worked ok.tonight i installed sp1 , yes it is smoother yes it still works in fsx australia but i have now tried 5 approaches into ksea and never yet managed to get onto thr glideslope. i have tried a fully fmc managed flight, and a manual flight but i always get a ctd before getting established.what is infuriating is that ksea worked perfectly before sp1guys have you any ideas?

[linux731 264]

I hear a lot of customers complaining about KSEA not working for them.... I guess the plane doesn't want to go home.

[CT1 5]

did u uninstall the NGX, delete the leftover files in FSX and do a fresh install? or did u just install sp1 over your current ngx setup, i did a fresh install and so far i have had no trouble but it was time consumeing to get all my liveries and ezdok camera views setup again. Im sure its not your fault, SEA is like the bermuda triangle of fsx so stupid hopefully FLIGHT will get it right

[linux731 264]

did u uninstall the NGX, delete the leftover files in FSX and do a fresh install? or did u just install sp1 over your current ngx setup, i did a fresh install and so far i have had no trouble but it was time consumeing to get all my liveries and ezdok camera views setup again.Im sure its not your fault, SEA is like the bermuda triangle of fsx so stupid hopefully FLIGHT will get it right

This is exactly what I did, and everything works perfect.

[Brittfrog 3]

no i didnt do a fresh installation having read about so many having activation problems so simply deleted the add on liveries and installed sp1, but now you come to mention it i seem to remember someone saying ksea was the worst area in fsim. strange though that i never had an issue with it before sp1

[audiohavoc 23]

no i didnt do a fresh installation having read about so many having activation problems so simply deleted the add on liveries and installed sp1, but now you come to mention it i seem to remember someone saying ksea was the worst area in fsim. strange though that i never had an issue with it before sp1

Well there you go. PMDG recommends that you uninstall the NGX, delete any NGX related files in the FSXPMDG folder as well as the FSXsimobjectsaircraft folder. Then install the original NGX release followed by SP1, and then your liveries.

[Cras 5]

I hear a lot of customers complaining about KSEA not working for them.... I guess the plane doesn't want to go home.

Or the opposite, it very much wants to go home, so it sees you flying into KSEA and not KBFI, and it gets very angry. Don't make the 737NG angry, not if you want to finish your flight that is.

[Brittfrog 3]

Well there you go. PMDG recommends that you uninstall the NGX, delete any NGX related files in the FSXPMDG folder as well as the FSXsimobjectsaircraft folder. Then install the original NGX release followed by SP1, and then your liveries.

I will have to do as you say I read what pmdg said I was just trying to avoid grief starngely enough i can start a flight and fly touch and goes at ksea it happens only if I fly in to ksea from elsewhere

[Paul Deemer 13]

Also make sure your not using any saved panel states from before SP1 they are not compatible and will cause unexpected results. Do yourself a favor and start over from scratch.

[Brittfrog 3]

well I did as suggested and undeleted ngx via the windows uninstaller looked for anything else pmdg and deleted that as well, rebooted the pc reinstalled 737 with sp1 and i have now tried 8 flights in the US and Australia in all cases i never completed a flight. i have reduced the scenery bars and overclocked the cpu to no avail it is far worse than before sp1 so I am now about to undelete the whole mess again and bin Sp1 and just use the original prog with if i remember correctly hotfix 3 this is starting to be a bit of a joke.

[Mike T 52]

Pre SP1 CrashesCrash - KSEA with Orbxy PNW scenery about 100nm out (OOM error)Crash - KIAH with Blueprint KIAH scenery about 10nm out (OOM error)Crash - KLAX with FSDreamteam KLAX - 2nm out. Actually (OOM error but didn't CTD. All textures disappeared and 737NGX instruments wen't blank)Crash - KEWR with Aerosoft Manhattan, Imaginesim KLGA, FSDreamteam KJFK about 70nm out. (OOM Error)Fly the same routes with iFLY 737, QW 757, LDS 767...no problem. Crashes are always on approach or within the destination scenery area. Also running RC 4.1 and ASE.Will try KLAX to KEWR now that I've updated and see what happens. Just purchased the 737-6/7 anyway...

[Leffe 3]

Hi anonymous!Have you done this:1. Uninstalled the NGX via control panel?2. Deleted then all leftover maps and files, and also in >Your nameAppDataRoamingMicrosoftFSXSimconnect......."Pmdg files there"?3. Antivirus off, UAC off, Run as Adm right by right click>>>>>then install?4. Rebooted?5. Start FSX (FSX with Adm right) and then choose NGX in free flight?Also added a copy of the "UIAutomationcore.dll file to FSX Root? Version 6.0.5840.16386 (32-bit)?If so, then not sure why you have this probs when so many dosen´t have this./ Leffe

[Kosta 122]

Guys, would you please report your LOD_RADIUS setting in FSX.cfg?

[altstiff 71]

Yes as Word Not Allowed said LOD_RADIUS "tweaks" can cause crashes.I had mine at 5.5 and anythime I was flying the NGX with photo scenery I would get a g3d.dll error after 30mins. With it set back to default 4.5 I have had none.

[cparrott73 20]

I've noticed more CTD problems on my laptop, but I think they are memory-related. I was already pushing the envelope of memory usage with the initial release of the NGX. I think adding the 600/700 stuff with SP1 pushed the envelope a little too far. I had to dial back some of my detail settings even further, especially around big airports, and now it seems more stable.The trade-offs of playing FSX on a laptop...sacrifice some realism for the sake of portability.

[Brittfrog 3]

ok in answer to leffe,yes deleted via windows installer, did not find the files in simconnect, antivirus is left on, uac is off , fsx is configured to always start by admin, rebooted ,and as you say started in free flight say for example yhba, fmc programmed for a flight to ybbn as soon as i pass 11000 feet without exception i get a ctd, if i fly manually i can then get close to ybbn , if i then program the fmc to fly an approach it crashes at some point on the approach. it is definitely a memory issue because when i manage to land manually most of the runway and taxiway texture has disappeared and one has to wait several minutes for it to return. uiautomation thingy is the same one that worked perfectly before with version 2922. and is a good one that took some finding.Srdan the lod radius i use is 8.50000 this worked perfectly in 2922, i have not tried to return to 4.5 since installing sp1reducing the cockpit texture to low res has no effect at all, in fact i cant see any difference when changing from hi res to low.as a matter of observation the current version for me is far worse than the original version before hotfixes , i managed with a bit of fiddling to get that to work quite well with very few ctd's, if any

[Tabs 2,789]

8.5 is an absolutely *RIDICULOUS* lod radius setting. That setting MASSIVELY increases memory load, it's one of the worst setting to increase if you're having OOM crash problems (which is almost certain what this is).

[Kosta 122]

LOD 8.5 is WAY too much for usage in ORBX, NGX, addon airports etc.If you look into FSX forum, you will see my current thread on this subject.I have found out that some sceneries make calls, which I don't have any explanation for, if VAS goes in usage above 3.4GB, it will crash with some sceneries. G3D.dll error.Right now, I'm not sure if it's possible to run more than 5.5. It all depends on how much VAS usage goes up. If you reach around 3.5GB usage, you are in dangerous waters.And what I like so much about these complaints, is that they are completely uneducated! Like, my FSX is crashing with OOM, I am using high LOD and I don't care if then it only happens with NGX... there is a reason for everything.

[Brittfrog 3]

hi just tried the same flight set at 4.5 well at first it seemed better but it still ctd'd whilst making the turn onto final. so i managed another 10 minutes flight with far less visual qualityi hear what you are saying Ryan about 8.5 being high, but it worked perfectly in 2922 so why not Sp1???I am thinking i will going back to 2922 because i see no benefits of Sp1it will be interesting to see what others find i see there are a few others with ctd probs

[rsrandazzo 6,349]

Gents-When tweaking your FSX to get the performance/visual settings you want- please please please please PLEASE keep in mind that you are running a very advanced simulation in the NGX.It wants resources....It needs resources...There is a massive amount of computational work going on under the hood, and if you soak up all the available resources with really nice looking terrain and scenery, you are going to have to user your noggin' when it comes to things like LODs...I have a "decent" machine that I use for development and testing, but I am also a bit of a scenery 'ho thanks to the input of Dr. EV(il) and I love nothing more than flying the NGX in and out of medium sized fields all around the OrbX PNW. I do not have CTDs... and I have the added load of running the simulator AND the dubgger at the same time.But I have made realistic decisions regarding the LODs etc.I guess what I'm saying is: If you don't understand what you are doing with all the tweaks and configs- then you may just want to leave them alone. Just because you read in a forum that someone else has his LOD set to 2,853,291 () doesn't mean it is smart, nor does it mean that it will work on your particular machine...Thus far with SP1- nearly every CTD we have researched has been the result of the user doing something whacked out with the manual tweaking, or has been a problem unrelated to the NGX... I'm NOT saying the NGX is flawless- but I am saying that the NGX will push your tweaking into CTD territory if you don't REALLY understand what you are doing...Nigel-I have changed the title of this thread to put it a bit more on target... Lets see if we can't get some experienced tweakers to join the discussion and find you a solution...You shouldn't have the problems you are having around SEA... So we have to "undo" whatever problems you might have created there while striving for improvement.I'm sure there are enough experts around here to get you running...

[Brittfrog 3]

LOD 8.5 is WAY too much for usage in ORBX, NGX, addon airports etc.If you look into FSX forum, you will see my current thread on this subject.I have found out that some sceneries make calls, which I don't have any explanation for, if VAS goes in usage above 3.4GB, it will crash with some sceneries. G3D.dll error.Right now, I'm not sure if it's possible to run more than 5.5. It all depends on how much VAS usage goes up. If you reach around 3.5GB usage, you are in dangerous waters.And what I like so much about these complaints, is that they are completely uneducated! Like, my FSX is crashing with OOM, I am using high LOD and I don't care if then it only happens with NGX... there is a reason for everything.

I take exception to this last remark as you have no idea of my knowledge or experience with fsim it may surprise you to know that fsx runs at 8.5 for everything except ngx in fact I have run it higher but found that 7.5-8.5 was a sweet spot with 2922, but you would know that as you know it all it seems, ---notI also know and accept that as ryan says it increases memory usage enormously but it handles it!! and you get the added benefit of no shimmering scenery even with orbyx that is why i find it strange that sp1 cant handle it.

[rsrandazzo 6,349]

Nigel-Take exception to anything you like- but I think the results speak for themselves. You have been digging in with the personalized tweaks, and you have created a situation where the NGX pushes your setup beyond the limits...The folks that know this product the best are trying to help you- so you can take offense- or you can be open minded to the fact that maybe you've got something bunged up...We've all got everything to gain by helping you sort this out- but you have to be willing to accept the fact that the problem AND the solution both involve you.This whole forum is here to help if you want it.

[Brittfrog 3]

Gents-When tweaking your FSX to get the performance/visual settings you want- please please please please PLEASE keep in mind that you are running a very advanced simulation in the NGX.It wants resources....It needs resources...There is a massive amount of computational work going on under the hood, and if you soak up all the available resources with really nice looking terrain and scenery, you are going to have to user your noggin' when it comes to things like LODs...I have a "decent" machine that I use for development and testing, but I am also a bit of a scenery 'ho thanks to the input of Dr. EV(il) and I love nothing more than flying the NGX in and out of medium sized fields all around the OrbX PNW.I do not have CTDs... and I have the added load of running the simulator AND the dubgger at the same time.But I have made realistic decisions regarding the LODs etc.I guess what I'm saying is: If you don't understand what you are doing with all the tweaks and configs- then you may just want to leave them alone. Just because you read in a forum that someone else has his LOD set to 2,853,291 () doesn't mean it is smart, nor does it mean that it will work on your particular machine...Thus far with SP1- nearly every CTD we have researched has been the result of the user doing something whacked out with the manual tweaking, or has been a problem unrelated to the NGX... I'm NOT saying the NGX is flawless- but I am saying that the NGX will push your tweaking into CTD territory if you don't REALLY understand what you are doing...Nigel-I have changed the title of this thread to put it a bit more on target... Lets see if we can't get some experienced tweakers to join the discussion and find you a solution...You shouldn't have the problems you are having around SEA... So we have to "undo" whatever problems you might have created there while striving for improvement.I'm sure there are enough experts around here to get you running...

Robert, thank you as well for your answer, and I agree with all you say , however I am not some 16 year old that has no fsim experience i also am an atpl that flies airbuses in europe (my other 1179 is a 727 adv) , i have also used fsim since fs2 and there are not many on this site that can say that!I agree completely with the fact that increasing lod causes problems but it worked in 2922 I have over the years arrived at a level of knowledge by trying what others suggest , a suck it and see approach i guess , and perhaps i dont have your technical knowledge, but i am a lot better than some of your beta testers given the snags they didnt pick up in the first issue of ngx.But I am not here to criticise your product , i think it is marvelous and praise it wherever i go with other pilots I would just like a solution that has raised its head since installing sp1and as for those that criticise a high lod i have run much higher than 8.5 with other peoples add on scenery with spectacular results.I will try going back a few steps and see what happens i will re-uninstall ngx with spi and go back to 2922 and see if that works as it did if i use the windows uninstall should i also remove any mention of pmdg in the registry or leave that alone?

[Kosta 122]

I take exception to this last remark as you have no idea of my knowledge or experience with fsim it may surprise you to know that fsx runs at 8.5 for everything except ngx in fact I have run it higher but found that 7.5-8.5 was a sweet spot with 2922, but you would know that as you know it all it seems, ---notI also know and accept that as ryan says it increases memory usage enormously but it handles it!! and you get the added benefit of no shimmering scenery even with orbyx that is why i find it strange that sp1 cant handle it.

Sorry, that last remark was NOT targeted directly at you. The remark was general, just like Robert said, I read lots of posts, and I see often people complaining about OOMs, CTDs, but then I put a simply question about some tweak, usually targeted to pick what in my opinion would be the cause, not revealing the solution and often real bull comes out...I am not saying that YOU don't know what you're doing. I have no idea about that.That out of the way...Of course sim is going to run with 8.5, but apparently YOU don't know that there are only "places" that cause problems. Which I found out about just today.And running 7.5 or 8.5, yes, you were successful with 2922, but it doesn't have ANYTHING to do with the aircraft.It all comes down to the VAS usage and where you fly. And how you fly.And I tested from NGX, 747 and default 737, and I have been able to cause the errors on those places with all 3 aircraft.While they happen in one situation, they don't happen in the 2nd flight... all because of what you do and if you manage to make the VAS go over approx. 3.4GB.I would suggest you keep an eye on your VAS. If you know how to read it?Trust me on this one, I just spent 2 days testing and tweaking, searching for an answer... and I have found it.You will not be able to run LOD 7.5 with NGX without the risk of OOM and/or g3d.dll error. While OOM won't happen that often, g3d.dll is surely going to, especially in FTX areas.LOD does not benefit to shimmering, it benefits to further sharper textures. Sharp textures don't mean less shimmering, if anything, than more.You are clearly wrong, even Robert has told you, I pray that you accept it.

[rsrandazzo 6,349]

Nigel-Okay mate- I've tried.I'm an ATP that is rated on the 744... That doesn't mean a hill of beans when it comes to FSX, computers or tweaking. It means precisely nothing.I'm trying to help you find a solution and you are hurling insults at the folks who invest thousands of hours helping to make this product great.I understand that you are frustrated- but Ryan and I are both trying to help you- but it appears you aren't interested.Best of luck- I hope someone here can talk you through a solution.