Hi,I think many of you out there know how frustrating the (in)famous "g3d.dll" error can be. I'm still suffering from this error regularly especially with the MD11 over FTX-territory. Neither turning down the autogen, reducing Ai-traffic nor updating my nvidia drivers could solve fsx crashing after around 20 minutes in these areas (mostly PNW, but sometimes even near YSTW). It only happens with the (amazing) complex PMDG-aircraft, however not with "other" complex planes like the A2A B17 (accusim) or the FSlabs Concorde. I know that this is a very difficult error to trace and appears to apply only to some (even though quite a few) system configurations. Since I will spend a lot of time testing the new NGX in airport environments like KBFI, KPAE and KMWH (FTX is to release CRM within hours! :( ) I fear that this error is going to occur again, or even more with the NGX being even more complex than the MD11 or B747. Maybe somebody from the beta tester team (who is familiar with this problem) could tell whether he experienced a "g3d.dll -ctd" with the new NGX over some FTX-territory (i assume that many of you use it)?Thank you very much in advance!Regardschristopher Volle

Christopher,I've used the NGX over Orbx's terrain and airports for a ton of the alpha and beta process and I have never seen this crash. I've never seen it in our other products either. g3d.dll is the sim's main renderer library - it's what draws the 3D world. A crash in that (at least that I've seen in support here over the years) is usually indicative of some sort of system issue - an overheat, an unstable overclock, driver issues etc, not the aircraft. Not sure what else to tell you unfortunately.

Christopher,I've used the NGX over Orbx's terrain and airports for a ton of the alpha and beta process and I have never seen this crash. I've never seen it in our other products either. g3d.dll is the sim's main renderer library - it's what draws the 3D world. A crash in that (at least that I've seen in support here over the years) is usually indicative of some sort of system issue - an overheat, an unstable overclock, driver issues etc, not the aircraft. Not sure what else to tell you unfortunately.

Thanks you for your response. I know that many use your products without a problem. It's just that I only experience this error with the MD11 and occasionaly with the 747, so - for me - there appears to be some incompatibility between your products and my system, and I'm definitely not blaming PMDG for it. Since nobody came up with a solution yet, I think i can just cross my fingers and hope that the NGX won't be affected since it has a completely new coding (or are there some parts transfered from the MD11 code?) - apparently i don't have this problem with the Bae41 so there might be some hope (on the other hand the 41 appears to be much less complex...). a never ending story!christopher volle

Christopher,Do you by any chance have the ORBX Libraries installed in FSX (check your scenery library layer). I too had been experiencing G3D.dll issues here and there, actually it was pretty rare and I did some digging, one of the users over at ORBX's forum suggested that the ORBX libraries should be placed at the top (above all ORBX/FTW sceneries). I did this and I have not had any G3D.dll crashes since then (so FAR)... BUT - as Ryan says, check your hardware, especially your video card. Chances are ORBX sceneries plus high end aircrafts might be pushing temps high. So check the temps on the card and if possible, increase the card's fan RPM.Cheers,

Christopher,Do you by any chance have the ORBX Libraries installed in FSX (check your scenery library layer). I too had been experiencing G3D.dll issues here and there, actually it was pretty rare and I did some digging, one of the users over at ORBX's forum suggested that the ORBX libraries should be placed at the top (above all ORBX/FTW sceneries). I did this and I have not had any G3D.dll crashes since then (so FAR)... BUT - as Ryan says, check your hardware, especially your video card. Chances are ORBX sceneries plus high end aircrafts might be pushing temps high. So check the temps on the card and if possible, increase the card's fan RPM.Cheers,

I haven't tried these solutions, I will try that and report back!Thank you very much!christopher volle

As others have said, this is likely to be a hardware issue. In my case, I had to use the nvidia control panel to force the fan to work at 100% even under relatively light load on my gtx285.Tim

As others have said, this is likely to be a hardware issue. In my case, I had to use the nvidia control panel to force the fan to work at 100% even under relatively light load on my gtx285.Tim

Same here... I had the G3D.dll crash with complex aircraft once in awhile - especially on long flights. I now use the NVidia CP to force the fan on my GTX480 to 100% before I start FSX, and have not had the problem since.Jim Barrett

Same here... I had the G3D.dll crash with complex aircraft once in awhile - especially on long flights. I now use the NVidia CP to force the fan on my GTX480 to 100% before I start FSX, and have not had the problem since.Jim Barrett

This is interesting. I have a GTX280 and I'm right now doing some testing, first with the default scenery around PNW. I have much more experience with temperatures and the CPU, did a whole bunch of tweaking when I OC my 2600k. Right now tempeartures on my GPU are around 80° C, while my GPU fan had a max of 59%. Shouldn't he be running on a much higher level to keep the GPU temp around 60? Running the CPU at temps above 80 wouldn't be to healthy in the long run, however I'm not sure about the GPU temp... What are you temps (max and average) on your GPU?Regards,christopher volle

Chris,My GPU temps are currently running at 39C on idle. When I have FSX running, the card doesn't get any hotter than 59C with the fan at 85% locked (via EVGA) precision. All this on an EVGA GTX 570. Comparing your card with a 570 isn't wise but you should have temps lower than 80. Why don't you crank up the fan speed and test of you don't get any G3D errors.

This is interesting. I have a GTX280 and I'm right now doing some testing, first with the default scenery around PNW. I have much more experience with temperatures and the CPU, did a whole bunch of tweaking when I OC my 2600k. Right now tempeartures on my GPU are around 80° C, while my GPU fan had a max of 59%. Shouldn't he be running on a much higher level to keep the GPU temp around 60? Running the CPU at temps above 80 wouldn't be to healthy in the long run, however I'm not sure about the GPU temp... What are you temps (max and average) on your GPU?Regards,christopher volle

I normally don't run the NVidia performance monitoring software while using FSX, as I like to keep background processes to a minimum, but I have done some tests, and also found that my GPU temps would get up to 80+ while FSX was running. With the fan at 100%, the temps stay below 50C. It is possible within the NV performance software to set up a temp vs. fan speed profile to automatically increase the fan as GPU temps rise, but I've never felt confident that this feature works properly. By setting the fan to 100%, I have the security of knowing that I'm getting the maximum possible cooling. Only drawback is that the fan is quite noisy running at full speed, but for me, it's a small price to pay for the stability that it provides.Jim Barrett

Setting it to around 85% (with nvidia inspector) decreases the temperature to around 60. I'll keep testing. maybe we have some light at the ned of the tunnel :( Thank you very much,Christopher Volle

For me the "g3d.dll" errors I was seeing were related to an unstable overclock of my CPU so checking your hardware and any OC of GPU/CPU might solve your issues. Good luck!

Christopher before you go chasing the white rabbit trying to solve this thing here are my results, I have suffered from the gd3.dll error since buying all the NA sceneries a few months ago, never had them before this. They don't just happen in PMDG aircraft but in the RealAir Duke, IFly and LevelD, these are the only AC I fly. Now my system is OC'ed but I ran Prime95 for 16 hrs, also used OCCT and Intel burn test and my system is rock solid. However as soon as I enter an FTX area its not long after and its crash time, I can do the same flight again with the the FTX switch turned off and everything is alright. The biggest problem is it seems for every person that reports these issues there is 3 or 4 people saying they don't have them, so what then can we ask the developer to do, it would be hard to pin point the problem, that is if there is a problem with their scenery in the first place.Good luck though.

I think many of you out there know how frustrating the (in)famous "g3d.dll" error can be. I'm still suffering from this error regularly especially with the MD11 over FTX-territory. Neither turning down the autogen, reducing Ai-traffic nor updating my nvidia drivers could solve fsx crashing after around 20 minutes in these areas (mostly PNW, but sometimes even near YSTW). It only happens with the (amazing) complex PMDG-aircraft, however not with "other" complex planes like the A2A B17 (accusim) or the FSlabs Concorde.

Christopheri wouldn't reply on your post, if i wasn't totally sure, that PMDG isn't causing the G3D events. Beside of that, some virtual pilots see the G3D Error in A2A Aircrafts, too.I've read a lot about G3D Events in several forums last months, but never had one by myself (>2500h on MD-11 and 744). Though, it took me 15 minutes to trigger the event in Brisbane by changing one line in the fsx.cfg in FSX@SP2 environment. This should be mentioned cause the G3D.dll of SP2 and Acceleration-Pack deviate of each other.Which line i did change?I raised the LOD radius fom standard (4.5) to 9.5 mio to stress the engine.Youy guys are searching for an ingame- setting, aircraft or scenery as trigger. The real trigger is to run the FSX- engine out of its own specification and some of you have forgotten the warnings which also were published when you have received performance tweaking hints for the fsx-engine.the lines:HIGHMEMFIX=1TEXTURE_MAX_LOAD=1024 - 4096 are reliable to do not trigger the G3D event worldwide (i would have tons of problems if that causes problems, too)also the stability tweak "UIAutomationCore.dll" doesn't result in G3D! For the contingency someone says: "Hey, i have G3D Events without tweaking fsx-config"=> make sure you are starting with a fresh fsc.cfg => make your OC CPU stable (=> that means lower clockspeed, just to give some of you a direction )=> chuck you acceleration-pack out and install FSX SP2 Beside of Microsoft no FS developer is delivering deviating software based on the same product, so no further aberrance should be expected.conclusion: performance tweaking fsx.cfg is still risky!

Interesting to see that there is another g3d.dll thread starting.But when you carefully read through all these thread around the web you will find the following:1. The problem exists since 2001(!)2. There is no "single point of failure" and so there is no solution!Some people thought they found a solution, and it might have worked for them but not for others.Some people had problems in certain areas, where others didn't.As Ryan said, the problem occurs when a certain combination of 999 variables (out of hardware, OS, drivers, addons, date, time and weather ... :( ) apply. So, don't waste your time to chase something you never can catch. I know, it's annoying to get a CTD at the end of a 3 hour flight, but sh.. happens.