Hi allIs anyone having CTA with g3d.all error, when flying 738NGX, using FSX? or is just me?RonI get this error all the time coming into ORD (FSDT) after passing BENKY on the BENKY1 arrival

Hi Ron!I don´t have the solution, but here´s a lot of info about this:here/ Leffe

Do you have the UiAutomationCore.dll file in your main FSX root folder? I do have this and I'm not having any CTD's whatsoever.

Do you have the UiAutomationCore.dll file in your main FSX root folder? I do have this and I'm not having any CTD's whatsoever.

That will only cure using the FSX Menu to much. I also had no probs and I also havethe UIAutomationCore.dll copied to my Root FSX folder.So it hasn´t anything to do with his G3d.dll crash when arriving an airport.Here´s what Ryan said about it some months ago:/ Leffe"Here is the deal on the dll:It's a Windows OS library for creating user interface (UI) elements. It resides in the WindowsSystem32 folder. FSX calls it to create the menus and dialogs in the sim and it's also involved in view switching.There is an incompatibility between FSX and the Windows 7 x64 version of this file that can cause a crash after a certain amount of uses of the menus or view changes. A lot of crashes people assume are out of memory errors or whatever are actually this uiautomationcore.dll problem building up over the course of a flight - it can take several hours for enough actions to happen to trigger the freeze or crash with it.You can see it yourself by doing the following - load up any aircraft - default ultralight is fine. Without any replacement dll in your FSX folder, start bringing up the right-click menu over and over. After 20-30 times, the sim will crash - it's totally repeatable for me here.The replacement file is from Vista x64 I believe and doesn't have any issue with FSX.To answer an earlier question, the reason this works is because applications have a series of fallback "paths" where they automatically look for required dlls. The first place it checks is the same folder the exe is in... After that it'll look in the various Windows system folders, the side by side cache etc"Ryan Maziarz

That will only cure using the FSX Menu to much. I also had no probs and I also havethe UIAutomationCore.dll copied to my Root FSX folder.So it hasn´t anything to do with his G3d.dll crash when arriving an airport.Here´s what Ryan said about it some months ago:/ Leffe"Here is the deal on the dll:It's a Windows OS library for creating user interface (UI) elements. It resides in the WindowsSystem32 folder. FSX calls it to create the menus and dialogs in the sim and it's also involved in view switching.There is an incompatibility between FSX and the Windows 7 x64 version of this file that can cause a crash after a certain amount of uses of the menus or view changes. A lot of crashes people assume are out of memory errors or whatever are actually this uiautomationcore.dll problem building up over the course of a flight - it can take several hours for enough actions to happen to trigger the freeze or crash with it.You can see it yourself by doing the following - load up any aircraft - default ultralight is fine. Without any replacement dll in your FSX folder, start bringing up the right-click menu over and over. After 20-30 times, the sim will crash - it's totally repeatable for me here.The replacement file is from Vista x64 I believe and doesn't have any issue with FSX.To answer an earlier question, the reason this works is because applications have a series of fallback "paths" where they automatically look for required dlls. The first place it checks is the same folder the exe is in... After that it'll look in the various Windows system folders, the side by side cache etc"Ryan Maziarz

When I used to use FSX on W7 (x64) the UIAutomationCore.dll placed in FSX's root folder NEVER cured black screen of death crashes. I went back to XP (x64) and black / cream screen of deaths still occur so it has nothing to do with an incompatibility issue with Vista and W7.Regarding your G3D.dll CTD that issue has been around for years. I actually got it last night around LOWI though I wasnt flying the NGX, I had so many issues with that dll crashing at the beginning of the year and nearly binned FSX as it was so upsetting and frustrating having spent 1000s on the sim. At the time I mostly flew around ORBX PNW and research found me finding dozens of other users of this product having G3D crashes. I hadnt had one since removing this scenery and was horrified to get one last night. Many users will claim its caused by an overload of your system...check my specs my system is high end and it gets itIt;s so unpredicable and stops you enjoying the sim as it's not invoked by user access to menus etc

Maybe this is all being caused by a too large lod radius? I've set it to 4.5 and having no problems at all.

Maybe this is all being caused by a too large lod radius? I've set it to 4.5 and having no problems at all.

Not ONLY by that... but mainly.Check here for MUCH more info:http://forum.avsim.net/topic/353179-gd3dllhelp/

Maybe this is all being caused by a too large lod radius? I've set it to 4.5 and having no problems at all.

Back in Feb I did EVERY single variation to cure the issue, removed all overclocks on cpu and gpu, reinatlled OS, reinstalled FSX and minimal addons, stop using external frame limiters, stopped using enb hd mod, lowered settings right down to sparse, even tried a different cpu then different gpu then different memory....there simply is NO cure for this crash. Last time I looked ORBS had about 22 very long pages on the subject and nothing worked EDITMeant to say after all the speculation about LOD I ran it all at default, clean installation, clean fsx.cfg getting 40+ fps no strain on the system whatoever and BAM fatal error. monitored all my hardware and memory usage and it was not being pushed so those that say its caused by stress of the users settings are well clutching at straws. Some systems get it, some dont. Its the one crash that makes my blood boil unfortunately so I apologise if this is apparent in my comments on the subject. I literally spent about 2 full months pulling my hair out. If I reinstall ORBX PNW I can 100% of the time initiate a CTD

Back in Feb I did EVERY single variation to cure the issue, removed all overclocks on cpu and gpu, reinatlled OS, reinstalled FSX and minimal addons, stop using external frame limiters, stopped using enb hd mod, lowered settings right down to sparse, even tried a different cpu then different gpu then different memory....there simply is NO cure for this crash. Last time I looked ORBS had about 22 very long pages on the subject and nothing worked EDITMeant to say after all the speculation about LOD I ran it all at default, clean installation, clean fsx.cfg getting 40+ fps no strain on the system whatoever and BAM fatal error. monitored all my hardware and memory usage and it was not being pushed so those that say its caused by stress of the users settings are well clutching at straws. Some systems get it, some dont. Its the one crash that makes my blood boil unfortunately so I apologise if this is apparent in my comments on the subject. I literally spent about 2 full months pulling my hair out. If I reinstall ORBX PNW I can 100% of the time initiate a CTD

Same here mate, same here. It's one of those things that tells me to go play some other game.

Same here mate, same here. It's one of those things that tells me to go play some other game.

LOL I agree I actually installed Tomb Raider to take my mind off FSX for a while but the flying bug creeps back in

Hi allIs anyone having CTA with g3d.all error, when flying 738NGX, using FSX? or is just me?RonI get this error all the time coming into ORD (FSDT) after passing BENKY on the BENKY1 arrival

I was having a bunch of these g3d.dll CTD's recently, especially in places that stress the scenery - and tried everything under the sun to resolve it from a FSX standpoint. Finally, I uninstalled the Nvidia 285.62 GPU driver and ran DriverSweeper in Windows safe-mode. Then reinstalled the 275.33 driver. I have not had one single g3d.dll CTD in the several weeks since. I don't know if it was a flakey installation of the 285.62 driver - I performed the 'clean install' option when I originally installed it, but maybe that's not as good as the 'ol fashioned, tried-and-true meathod of using DriverSweeper.Try a uninstall and deep-cleaning of your video driver and see if it helps.Oh, and I personally use Ryan's Nvidia Inspector settings found at the top of the PMDG General Forum - 8xS option.

I was having a bunch of these g3d.dll CTD's recently, especially in places that stress the scenery - and tried everything under the sun to resolve it from a FSX standpoint. Finally, I uninstalled the Nvidia 285.62 GPU driver and ran DriverSweeper in Windows safe-mode. Then reinstalled the 275.33 driver. I have not had one single g3d.dll CTD in the several weeks since. I don't know if it was a flakey installation of the 285.62 driver - I performed the 'clean install' option when I originally installed it, but maybe that's not as good as the 'ol fashed, tried-and-true meathod of using DriverSweeper.Try a uninstall and deep-cleaning of your video driver and see if it helps.Oh, and I personally use Ryan's Nvidia Inspector settings found at the top of the PMDG General Forum - 8xS option.

I have 275.33 Driver installed since I upgraded to GTX570 and never updated the driver as I read some negative comments on the new Nvidia Drivers.......unfortunately I am having g3d.dll crashes as well (follow the link on Post #7 above by Word Not Allowed...)Regards

I went through couple of driver versions, testing for the error. It's not the driver. Yes, I did use the sweeper and safe mode for each and every driver version I tested. I tested 275.33 too.

I too went through every viable option, Ive posted another extremely long comment on another threadhttp://forum.avsim.net/topic/353179-gd3dllhelp/page__view__findpost__p__2162543My way of thinking is if you have to debug errors you omit ALL custom made changes, you remove any tweaks to cfg files, you remove ALL graphic driver tweaks both to nvidea control panel, nhancer or Nvidea Inspector and run at default. I too tried loads of drivers and went right back to 182.50 which some report as being a 'cure', using both Driver Sweeper, another driver cleaner and nvideas clean installs but unfortunately absolutely nothing worked.

Well i have a topic about this regarding the OEV16/8500 LOWI G3D.DLL and it seems to me that getting around this is setting the Autogen to Normal and then back up to MAX passing the spot.I have the same in Munich EDDM and occasionally in LFPG but 100% at OEV16/8500 LOWI with the NGX/Michael