This thread is about the GS3.dll CTF, not OOM...Cheers,- jahman.

Darn it, I thought I was in the OOm thread.....My age, nothing else

This thread is about the GD3.dll CTF, not OOM...Cheers,- jahman.

Yes, totally agree. OOM's are a completely different subject and can be easily fixed.Best regards,Jim

Hi Jim,Thank you for the great article. Like with you, this CTD business was spoiling all the fun. I was being bombarded by such an ever increasing litany of errors and CTDs, I bit the bullet and did a complete windows 7-64 and 80G of FSX reinstall on two separate SSDs. Afterward I counter intuitively increased, by a substantial margin, my AA settings with Nvidia Inspector (see Hardware Forum), installed the free ORBX Night/Day lights switcher, and left everything else cranked up to the max. Using my usual FSX.cfg modifications (which includes the small radius mod set to 2) I have been presented with what seems like a brand new and ultra smooth Sim.It has been almost a week now with a half dozen or so graphically intense, several hour long flights under my belt. I have had absolutely zero G3D.dll or any other error codes. I have managed to be able to rely on between 20 and 35 FPS doing circuits at SEATAC with 100% scenery settings and 100% UT2 AI traffic in the new version of Captain Sim's 767-300. Whatever is the prime reason for this relief, and it has got to be one of the above, it has given me a new lease on my simulation life. I am glad that you seem to have found your solution also. The good news is: there is hope for everyone who has been plagued with the G3D.dll error.Kind regards,

Yes, totally agree. OOM's are a completely different subject and can be easily fixed.Best regards,Jim

i know, I meant to post in this one http://forum.avsim.n...ory-cdt-in-fsx/Did not think I needed to be told twice, when i posted that I was in the wrong thread. can't an old fart like me make a mistake ?

Hi Jim,Thank you for the great article. Like with you, this CTD business was spoiling all the fun. I was being bombarded by such an ever increasing litany of errors and CTDs, I bit the bullet and did a complete windows 7-64 and 80G of FSX reinstall on two separate SSDs. Afterward I counter intuitively increased, by a substantial margin, my AA settings with Nvidia Inspector (see Hardware Forum), installed the free ORBX Night/Day lights switcher, and left everything else cranked up to the max. Using my usual FSX.cfg modifications (which includes the small radius mod set to 2) I have been presented with what seems like a brand new and ultra smooth Sim.It has been almost a week now with a half dozen or so graphically intense, several hour long flights under my belt. I have had absolutely zero G3D.dll or any other error codes. I have managed to be able to rely on between 20 and 35 FPS doing circuits at SEATAC with 100% scenery settings and 100% UT2 AI traffic in the new version of Captain Sim's 767-300. Whatever is the prime reason for this relief, and it has got to be one of the above, it has given me a new lease on my simulation life. I am glad that you seem to have found your solution also. The good news is: there is hope for everyone who has been plagued with the G3D.dll error.Kind regards,

Hi Stephen!Great to hear from you and that the SmallRadiusReject tweak worked for you too. I just noticed last night after installing Version 2 of KORD from FSDT that their addon manager adds the SmallRadius tweak as well as several other tweaks. That's evidently how I got all these tweaks in my original FSX.cfg because, as you know I try to limit tweaks to just the HIGHMEMFIX. With all those tweaks added by FSDT, I could only run fsx with just the basic textures (1024). Anything higher created a g3d crash. By accident, I started adding tweaks to a new config with the SmallRadiusReject tweak and that one got rid of my g3d errors. Since you have almost the exact same system as mine (I know because I copied your system when I started purchasing parts), I rushed over to the hardware forum and looked up your memory bios settings and set them exactly as you had them. I now have no more CTD's and my Event Viewer is totally error free for the first time in a long time. You the man! LOL! Hope all is well with you and thanks for letting me know your system/fsx was fixed too! Hopefully it will work for many others and we can all Go Fly....Best regards,Jim

Hi Jim,Thank you for the great article. Like with you, this CTD business was spoiling all the fun. I was being bombarded by such an ever increasing litany of errors and CTDs, I bit the bullet and did a complete windows 7-64 and 80G of FSX reinstall on two separate SSDs. Afterward I counter intuitively increased, by a substantial margin, my AA settings with Nvidia Inspector (see Hardware Forum), installed the free ORBX Night/Day lights switcher, and left everything else cranked up to the max. Using my usual FSX.cfg modifications (which includes the small radius mod set to 2) I have been presented with what seems like a brand new and ultra smooth Sim....

Good moment to make a disk image of your entire FSX PC!

...I just noticed last night after installing Version 2 of KORD from FSDT that their addon manager adds the SmallRadius tweak as well as several other tweaks.

Oh, the "silent tweaking" syndrome! Why does most every add-on developper think they can tweak someone's FSX setup without even asking? That's my pet peeve I hope Flight will fix.Cheers,- jahman.

I didn't notice any SmallRadius CFG tweak on my recent KORD upgrade. I checked the cfg and it was not there. I had to add it manually.

Oh, the "silent tweaking" syndrome! Why does most every add-on developper think they can tweak someone's FSX setup without even asking? That's my pet peeve I hope Flight will fix.Cheers,- jahman.

The addon manager will only add the tweaks it if you tell it too.

I didn't notice any SmallRadius CFG tweak on my recent KORD upgrade. I checked the cfg and it was not there. I had to add it manually.

Totally agree. I did add it manually but was wondering how I got all those tweaks in my original FSX.cfg. I'm just stating that I recently discovered FSDT added those tweaks (forgot to say if you click the save to fsx button). Best regards,Jim

The addon manager will only add the tweaks it if you tell it too.

I wonder how many people like me hit that save to fsx.cfg button.Jim

Not that this is any help to the OP but I'm officially wrong about G3D's having to do with lack of virtual memory... arghI got a G3D today flying into KPDX. VAS was below 3GB and whammo, CTD g3d.Back to square one. Nobody knows exactly what causes them and we probably never will.On another note: Is anyone flying Orbx PNW without a OOM or G3d ctd? And I read I think in the orbx forums there's a program that checks for corrupt airport scenery and/or double airport files. Does anyone know the name of the program?

Not that this is any help to the OP but I'm officially wrong about G3D's having to do with lack of virtual memory... arghI got a G3D today flying into KPDX. VAS was below 3GB and whammo, CTD g3d.Back to square one. Nobody knows exactly what causes them and we probably never will.

Having ORBX?

Yeah it's Orbx. I guess I'm just a bit ######... they say Orbx scnenery doesn't cause these issues. Yet when I disable orbx I have no issues....What they really mean is "we don't know what causes the crashes with out scenery so we'll just claim it's not our fault."FWIW I was flying KAST AST V112 BTG KPDX at 7000, with the Flight1 T182. about 20 west of BTG I got the crash.

Yeah it's Orbx. I guess I'm just a bit ######... they say Orbx scnenery doesn't cause these issues. Yet when I disable orbx I have no issues....What they really mean is "we don't know what causes the crashes with out scenery so we'll just claim it's not our fault."FWIW I was flying KAST AST V112 BTG KPDX at 7000, with the Flight1 T182. about 20 west of BTG I got the crash.

ORBX is causing them issues.Yeah, that's their way of making business, apparently.I think they do know what the problem is, but can't solve it, and to solve it, probably would need to do a lot of background work or it's not even possible... but hey, let's make the money.

G3D.dll crash when trying to fly PANC-KSEA with NGX and ORBX, everytime i try, just after YYJ. I'm done with ORBX so far when flying IFR, they don't match at all....!!!Picture of crash site, here i'm waiting for that little window you know so well, MS FSX have crash bla bla bla... No warning at all, just blupp and total crash, no up's or down's on ram usage at all, just blupp. CTD...Everytime, same spot, i have give up on this one...Edit: for info, same route without ORBX, nice and steady landings at KSEA without trouble at all, even autogen set to very dense and 5m mesh with ASE producing weather....

Guys, there is an easy way to avoid g3d.dlls. Just see if a scenery uses lots of textures, that means it's gonna have a crash-tendency. And ORBX, since it does use lots of textures.