Well so far no G3D. I got an OOM though doing a heavy cfg setting with NGX through Orbx land, via a heavy scenery route. Departed freeware HQM, for BTG (near pdx) then north to join the OLM7 into KSEA. Got the OOM near TIW hehe... oh well I'll do some more testing to make sure a g3d even doesnt happen.

Well so far no G3D. I got an OOM though doing a heavy cfg setting with NGX through Orbx land, via a heavy scenery route. Departed freeware HQM, for BTG (near pdx) then north to join the OLM7 into KSEA. Got the OOM near TIW hehe... oh well I'll do some more testing to make sure a g3d even doesnt happen.

Keep lowering the LOD_RADIUS to manage OOM, I found out that running 7.5 is already dangerous with NGX. So I settled to 5.5 or 6.5, depending on where I fly. I observe VAS very often... it's mostly open beside my FSX when doing windowed.

I was on 6.5 for the record. Unfortunately the NGX is heavy on VAS (along with orbx) and I may just have to put up with 4.5 I'm going to test more without the NGX but still in PNW/NRM and use LOD 6.5. I once had a crash in some podunk town out in the wilderness, but it was heavily forested with LOD 6.5. I was using Mike's L39 which is really efficient as far as modeling goes.

Especially worry-free flying, knowing everything's gonna be fine and try once again enjoy approaches and landings.

You know what ? This is exactly my feeling: coming back again to enjoy approaches and landings..!!!

You know what ? This is exactly my feeling: coming back again to enjoy approaches and landings..!!!

Knowing that my heart use to race when approaching EGKK (UK200) on final that FSX would CTD, and now it does not, well it is a great feeling indeed.

It's a surprise at first, isn't it? Approaching with 'meh, it will CTD either way, but it was a nice flight so far' and then 'it does not crash! LANDING CHECKLIST!'

'it does not crash! LANDING CHECKLIST!'

Hahaha, yes, indeed, exactly what happened to me 2 days ago! LOL.

It's a surprise at first, isn't it? Approaching with 'meh, it will CTD either way, but it was a nice flight so far' and then 'it does not crash! LANDING CHECKLIST!'

After Landing checklist is even better.

Enjoy the OOM's and CTD's while you can. I would imagine that Microsoft Flight will have FAR less tweaking ability (less sliders, with less range for those that remain and very tightly controlled cfg files). In other words, Microsoft will save us from ourselves!

at http://forum.avsim.n...me/page__st__50Just to add my 2 cents worth:I've been purposely running 1 of my FSX development test systems with a very low powered 512 MB VRAM PCI-E add-in video card.I cannot personally recall ever experiencing a G3D.DLL error, and I almost never use any AI traffic. BUT....Despite an otherwise fairly optimized system setup and implementing selected FSX.CFG file tweaks (such as HIGHMEMFIX=1 etc.), when flying GA "bush" type aircraft in ORBX FTX PNW scenery for greater than about 15 minutes, I would incur black textures on part or all of my aircraft, followed later by similar intermittent texture losses on static scenery objects and/or Multi-Player aircraft.After installing the FSUIPC updated base package and latest FSUIPC DLL file today, the "texture loss" problem has not shown up on today's 45 minute Multi-Player flight, and the FTX terrain textures appear to be rendering with greater speed and sharpness. Many thanks to Pete Dowson for this workaround... and for all his other generous contributions to the FS Community over the years ! Regards,GaryGB

Sorry about the duplicate post, but IMHO, the kudos for Pete Dowson extend to his also apparently fixing a problem not directly involving a G3D.DLL CTD or AI Traffic on my system... so this FSUIPC update merits being tested for other issues that affect FSX performance as well ! Happy Flying ! GaryGB

Yes, that's a different matter altogether, and does sound like corrupt data someplace in your files rather than the overload situation which appears to cause the one I worked on. Is yours also an access violation error (0xC0000005 error code)? It looks like it crashes when trying to access a floating point value from an incoming data set -- one of the files it needs to read appears corrupted or probably truncated.You might be able to identify it by installing ProcMon from www.sysinternals.com, and running it whilst starting FSX. It will log all sorts of things -- best set the Filter to include operation "CreateFile" and nothing else, with Process name including "FSX" -- i.e. add those two filter lines in the Filter dialogue. When FSX crashes see what the last file was.

Will check it out some morefull error log:

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: g3d.dll, version: 10.0.61472.0, time stamp: 0x475e180cException code: 0xc0000005Fault offset: 0x00063581Faulting process id: 0x11f8Faulting application start time: 0x01cca418fae7730fFaulting application path: C:Flight Simulator Xfsx.exeFaulting module path: C:Flight Simulator Xg3d.dllReport Id: c28a3d9e-100f-11e1-a02f-002522dc92f5

scott s..

Hmm. I've not used FS9 since FSX came out. But if you have details of the crashes (I need module, offset and error code), I can look to see if it's the same thing. If it isn't i'm afraid I really can't spend time on it. It'd be a whole new ball game.RegardsPete

Hi Pete,This is from a FS9 g3d.dll crash when entering a detailed area (FZ KPDX):Faulting application name: fs9.exe, version: 9.1.0.40901, time stamp: 0x4135a208Faulting module name: G3D.DLL, version: 9.1.0.40901, time stamp: 0x4135a88eException code: 0xc0000005Fault offset: 0x0004384bFaulting process id: 0xdd4Faulting application start time: 0x01ccafcd93ec6c85Faulting application path: C:Program Files (x86)Microsoft GamesFlight Simulator 9fs9.exeFaulting module path: C:Program Files (x86)Microsoft GamesFlight Simulator 9MODULESG3D.DLLReport Id: c41c948e-1bc6-11e1-9b04-e0cb4e816464 procmon with the "fs9" and "createFile" filter didn't net anything during the event.Hope the work-around for FSX can be used for FS9.Thanks,Pat

Wow, I'm amazed. Awesome to see that the famous g3d.dll might be "fixed"! I find it so nice how now and then, the community gets together and thanks to the bright minds of one or more people, FSX is slowly by slowly patched and fixed, and all major errors are vgery slowly worked around. I myself have not had a g3d.dll error in a long time, to be honest, getting the occasional ntdll.dll CTD in what seems to be really dense scenery (got it last night when I overflew VFR London X with max settings for review purposes). But, I will for sure install the new FSUIPC version, in hopes that I will never have to get the g3d.dll CTD again.A thousand thanks to Pete on this!

Faulting module name: G3D.DLL, version: 9.1.0.40901, time stamp: 0x4135a88eException code: 0xc0000005Fault offset: 0x0004384b...Hope the work-around for FSX can be used for FS9.

Well, I'll have a look, but if it isn't pretty much the same problem I doubt it. I'll let you know. Could you send me this message on my Support Forum please? I think it deserves its own thread and I don't look at the AVSIM FS9 one.RegardsPete

I'm very excited to hear about this fix. For years, I have always had the g3d.dll crash over AS EBBR or EDDF, but was never able to find others with the same issue, so I just gave up and accepted the fact that there was a chance of a crash, but thanks to registered FSUIPC's auto-save function I'd just pick up where I left off at the time of the CTD.Now, if only someone could solve the ENBseries/Windows 7 64bit full-windowed screen mode CTD once and for all, that for me will take care of the last of my most frequent and frustrating FSX crashes that have yet to be solved.This solution to a very long standing glitch gives us FSX fanatics hope, and breathes new life into the old sim, considering that there must be some who have given up on FSX because of this specific CTD.Many thanks to Pete Dowson, you have just further proven your "Lifetime Achievement Award" status among the flightsim community. I hope everyone who is saved by this new discovery buys the registered version of FSUIPC.