Products Support > Honolulu FSX/P3D
Not Pointing Fingers, Just Need Help g3d.dll crash
lot734:
I'm sorry for bringing this old thread up but maybe I can help some of you.
I had the same problem and I found that g3d.dll CTD is caused by two afcads.
I own Megascenery Hawaii, FSDT PHNL and Aerosoft Dillingham. At the beginning I didn't realize that I have two afcads for PHNL and PHDH.
Megascenery Hawaii has an afcad file for the default Honolulu and Dillingham.
After I deleted these two Megascenery afcads g3d.dll CTD problem is fixed. From now on I will always check for double afcads.
Best regards,
Kris
aarnjer:
There is various errors what can cause the g3d.dll error message
heres a few
1.missing texture mostly if not update to current UT2.
2.too much textureload not the size like autogen, bufferpools, etc (brobaly not tweaked fsx.cfg) -> bojote will do that
3.dublicate afcads.
4.too much fregmented hard-drive. and fsx and all the files not marked as high perf also add folderpath user/appdata/roaming/microsoft/fsx (disktrix will do it)
I'm not sure about this but i think also they have something to do whit g3d.dll
5.uiautomationcore.dll and simconnet.dll
btw.this topic sholuld be pinned
pcubine:
Umberto
Guess what. A g3d.dll error at PHNL. I installed PHNL maybe four or five months ago and did many flights between PHNL-PHNL, PANC-PHNL and PHNL-YSSB with no problems. Then about two months ago the g3l.dll errors started with the PMDG MD-11. I can start the flight at PHNL or end it at PHNL. It makes no difference. I still get g3d.dll errors. Two tonight. The first when the MD-11 was initializing, it stopped at 0 seconds left and I got a CTD. The second occured after starting to taxi to 8R from the cargo area. The faulting module was g3d.dll. The closest scenery is PANC,KLAX and VHHH. I have no UT2. Any ideas on what to try?
Thank you
Michael Cubine
virtuali:
--- Quote from: pcubine on October 11, 2012, 08:07:28 am ---Guess what. A g3d.dll error at PHNL. I installed PHNL maybe four or five months ago and did many flights between PHNL-PHNL, PANC-PHNL and PHNL-YSSB with no problems. Then about two months ago the g3l.dll errors started with the PMDG MD-11.
--- End quote ---
That should be plenty enough proof it can't be a PHNL problem, since the scenery surely hasn't changed itself so, it's not PHNL, but something else you have only in that area, either a problem with terrain, or an AI that goes only there (so you are mislead thinking the problem might be the airport)
In any case, the g3d.dll problem it's the most common FSX crash, and it's possible you might fix it by installing the latest FSUIPC, which has a feature that prevents g3d.dll crashes.
pcubine:
Umberto
I have the lastest complete install of FSUIPC as of September 7, 2012. So FSUIPC is not going to solve anything. I believe the first update which attempted to solve most of the g3d.dll errors was dated in January 2012. I installed that update then which did eliminate the g3d.dll errors I was having prior to that update.
I went back and tried to determine a timeline of what was going on at the end of July and the beginning of August 2012.
7-24-12 Installed PHNL.
7-26-12 Last succesfull flight from YSSY to PHNL.
8-5-12 g3d.dll error appears for first time.
Between 7-26-12 and 8-5-12 the following was installed.
AS2012 SP1
SetUp_AddOnManager
FSUIPC4843.zip which contained FSUIPC4.dll
Could the AI that you mentioned that goes only there be a FSX default plane. If so, I will reduce all the planes to 0%.
Thank you
Michael Cubine
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version