FSDreamTeam forum
Products Support => Honolulu FSX/P3D => Topic started by: johndrago on March 28, 2011, 10:11:03 pm
-
Hi Guys,
I have a new high-end machine, to which I reinstalled FSX, and all add-ons too. I've been a user of FSDT PHNL, and Hawaii Volume 1 for a long time. Since my new install, I've been receiving CTDs at PHNL, with the faulting module being g3d.dll. This has only happened at FSDT PHNL so far. It has happened when loading the airport and flight from PHNL, and on final approach to 8L flying KLAX-PHNL. I've been flying the LDS767.
The only new add-on I have with my new installation is UT2. It has been working fine so far, but I'm wondering if there is a conflict between FSDT and UT2. I'm not pointing fingers at either one, but given the many users here, I thought someone might be able to help me diagnose and fix this, so that I can get a successful flight into my favorite airport!
Are there settings on either app that may help tune them to work better together?
Any help would be greatly appreciated!
Thanks,
John
Below are my specs:
Windows 7 Ultimate 64 bit
Core i7 960
6GB Muskin RAM
EVGA Nvidia Geforce 460 GTX OC 1GB
FSX Gold with Acceleration
-
The first question that comes to mind is, have you tried PHNL with default traffic ? At least we would know if it's the combination of the two which creates a problem. Then, after we assessed this, we might try to understand any reason.
BTW, I use UT2 myself and, even if I'm not have it turned on at all times, when we test a scenery with lots of traffic, we tend to use UT2 as a reference, specifically because it also uses Simconnect, quite heavily so, it could *potentially* create issues with our airports. But it never happen to have such crash.
AI-related crashes are tricky to check, because they are related to a specific schedule, they might not appear every day, or every time.
-
The first question that comes to mind is, have you tried PHNL with default traffic ? At least we would know if it's the combination of the two which creates a problem. Then, after we assessed this, we might try to understand any reason.
BTW, I use UT2 myself and, even if I'm not have it turned on at all times, when we test a scenery with lots of traffic, we tend to use UT2 as a reference, specifically because it also uses Simconnect, quite heavily so, it could *potentially* create issues with our airports. But it never happen to have such crash.
AI-related crashes are tricky to check, because they are related to a specific schedule, they might not appear every day, or every time.
I will test this weekend without AI (UT2), and let you know.
Thanks,
John
-
The first question that comes to mind is, have you tried PHNL with default traffic ? At least we would know if it's the combination of the two which creates a problem. Then, after we assessed this, we might try to understand any reason.
BTW, I use UT2 myself and, even if I'm not have it turned on at all times, when we test a scenery with lots of traffic, we tend to use UT2 as a reference, specifically because it also uses Simconnect, quite heavily so, it could *potentially* create issues with our airports. But it never happen to have such crash.
AI-related crashes are tricky to check, because they are related to a specific schedule, they might not appear every day, or every time.
Ok, I tested over the weekend. I disabled UT2, and flew the same flight (KLAX-PHNL). This time, I was able to land without incident. Again, not sure what the interaction issue is, but something is going on.
Any ideas?
Thanks
-
I disabled UT2, and flew the same flight (KLAX-PHNL). This time, I was able to land without incident.
Most likely cause, it's a problem with one of the UT2 models, maybe related to an invalid/missing/corrupted texture. Or, maybe not really a problem, but just too many objects loaded, leading to video memory corruption/exhaustion, that might be fixed by lowering the AI density.
-
I disabled UT2, and flew the same flight (KLAX-PHNL). This time, I was able to land without incident.
Most likely cause, it's a problem with one of the UT2 models, maybe related to an invalid/missing/corrupted texture. Or, maybe not really a problem, but just too many objects loaded, leading to video memory corruption/exhaustion, that might be fixed by lowering the AI density.
Ok, good suggestion. Anyone else that had this problem, or similar have a suggestion to what UT2 settings work at PHNL?
Thanks,
John
-
I wish I could help John but I don't have ut2 yet I should be getting it hopefully soon, like Umberto mentioned there could be a missing ai texture causing the crash or there is just to much going on for the system. I had a similar problem with aerosoft/simwings Madrid scenery were it would constantly crash and it was because of a missing texture in one of the ai folders.
-
Ok, good suggestion. Anyone else that had this problem, or similar have a suggestion to what UT2 settings work at PHNL?
Thanks,
John
I've been having the same problem since day one of installing PHNL. Loading at the airport, or approaching from one of the other islands presents no problems, but on overwater flights from the mainland or asia the sim crashes somewhere between 100-50mi out of HNL.
There seems to be no resolution to the issue. I'm using UT2, Activesky, etc. All worked well in concert prior to the installation of HNL. I've since performed full reinstallation of FSX and all add-ons, done all the standard tests, etc. Same result- sim crashes apparently at some point where it begins loading the airport, scenery, etc. Through tedious steps I've found that it was, unfortunately, HNL's installation that brought this behavior to my situation.
Some discussions have circled simconnect, and as expected each party insists there is no piece of their product causing the overload. It's very possible that having some of these add-ons working simultaneously is simply passing an inherent limit within FSX and that there really is no fault or culprit buried in either.
You might try changing the load distance settings for UT2 while adjusting the load/pop settings for HNL to separate the two as much as possible. I've had limited success with this. More often I've found that pausing and refreshing the sim/scenery, etc at around the 70mi mark can be beneficial, but it's a toss-up.
Personally I think these two products are just taxing FSX/simconnect excessively as one approaches HNL from a long distance. Why it seems related to long duration flights in-sim is beyond me....
-
but on overwater flights from the mainland or asia the sim crashes somewhere between 100-50mi out of HNL.
If this is the case, you can safely discount the problem being PHNL airport, since we don't load it until 10 nm from the airport center. Even with the Anti-popup at the maximum level, nothing with be loaded anyway outside the global range of the airport, which at PHNL is set at 10 nm.
The only thing loaded at that distance would be the AFCAD and AI and of course, a different AFCAD from default might call different AI models comparing to default because of the different airline assignments so, one might be easily mistaken the problem "started" when installing the airport, when if fact its AFCAD simply disclosed a problem with AI that was already there, but couldn't be noticed using a different AFCAD.
Some discussions have circled simconnect, and as expected each party insists there is no piece of their product causing the overload.
We had issues with KDFW + UT2, which *used* to rely on Simconnect more heavily compared to other sceneries, and some logging tests we made a while ago revealed several Simconnect errors caused by UT2 (and less errors caused by the LD767), but no errors at all caused by our module, see the original discussion here:
http://www.fsdreamteam.com/forum/index.php?topic=3350.msg29573#msg29573
This lead us to change the method KDFW handles ground objects using shaders, and stop using Simconnect, and the problem went away. However, those problem led our module not having enough time left to issue its commands, which caused visual problems at the airport, but we never seen crashes.
PHNL, on the other hand, never used that method to begin with, and it's way less taxiing on Simconnect than KDFW, also because of way less objects to draw. In any case, there are no Simconnect "actions" on our side at PHNL, until entering inside the 10 nm range.
-
I disabled UT2, and flew the same flight (KLAX-PHNL). This time, I was able to land without incident.
Most likely cause, it's a problem with one of the UT2 models, maybe related to an invalid/missing/corrupted texture. Or, maybe not really a problem, but just too many objects loaded, leading to video memory corruption/exhaustion, that might be fixed by lowering the AI density.
Ok, good suggestion. Anyone else that had this problem, or similar have a suggestion to what UT2 settings work at PHNL?
John
I had the very same issue for a considerable time and just like you the problem occured when i bought and installed PHNL, I run UT2 as well. I have no idea what caused the issue but this is what i did to resolve it, in UT2 i turned off GA traffic and moving Jetways and since then i've not had the problem,.....give it a try and see if it helps, i still keep commercial AI at 100%.
-
I had the very same issue for a considerable time and just like you the problem occured when i bought and installed PHNL, I run UT2 as well. I have no idea what caused the issue but this is what i did to resolve it, in UT2 i turned off GA traffic and moving Jetways and since then i've not had the problem,.....give it a try and see if it helps, i still keep commercial AI at 100%.
Interesting. Is it the combo of unchecking the moving jetways and GA traffic, or does just unchecking the moving jetways work too?
Thanks,
John
-
I had the very same issue for a considerable time and just like you the problem occured when i bought and installed PHNL, I run UT2 as well. I have no idea what caused the issue but this is what i did to resolve it, in UT2 i turned off GA traffic and moving Jetways and since then i've not had the problem,.....give it a try and see if it helps, i still keep commercial AI at 100%.
Interesting. Is it the combo of unchecking the moving jetways and GA traffic, or does just unchecking the moving jetways work too?
Thanks,
John
I did them both John, so i believe its the combination, when i tested with just the GA turned off i had the occasional issue but with them both deactivated, it was fine.
-
I have read in other forums that sometimes the cause for this is a texture issue with one of your planes or one in UT2. The g3d.dll is a hard one to figure out as many things can cause it to happen.
-
yea this ctd is a hard one since can can come up anywhere just go over to orbox forum they got two thread on this type of ctds
-
I had the very same issue for a considerable time and just like you the problem occured when i bought and installed PHNL, I run UT2 as well. I have no idea what caused the issue but this is what i did to resolve it, in UT2 i turned off GA traffic and moving Jetways and since then i've not had the problem,.....give it a try and see if it helps, i still keep commercial AI at 100%.
Interesting. Is it the combo of unchecking the moving jetways and GA traffic, or does just unchecking the moving jetways work too?
Thanks,
John
I did them both John, so i believe its the combination, when i tested with just the GA turned off i had the occasional issue but with them both deactivated, it was fine.
I ended up turning off GA traffic, and moving jetways, and it solved the problem for me so far.
John
-
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
-
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
-
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
-
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.
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.
-
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
-
Not a single file in the whole PHNL folder has been updated since May 2012 so, if you installed it in July and were able to complete a flight successfully back then, but not now, it's fairly safe to assume PHNL is not the problem.
About FSUIPC, the most current version is 4.853, not 4.843
http://www.schiratti.com/dowson.html
and it seems to be coming in a .ZIP file named FSUIPC4, not FSUIPC4843.zip
http://fsuipc.simflight.com/beta/FSUIPC4.zip
-
Umberto
What about the AI plane you mentioned? I have no AI planes except for FSX default AI. If you believe that might help, I will set commercial and GA to % in the FSX Settings.
Thanks
Michael Cubine
-
What about the AI plane you mentioned? I have no AI planes except for FSX default AI. If you believe that might help, I will set commercial and GA to % in the FSX Settings.
It's unusual for default AI to have a problem, but testing it without AI doesn't cost anything. And of course, you should test disabling any other addon to, you mentioned AS2012, turn off that one too as a test.
Another possible cause, which might be difficult to find, it's a corrupted default texture, but since there are thousands of them, it might be easier just reinstalling FSX than trying to find it.
-
Umberto
I will try the AI and AS2012 and let you know what happens. Reinstall FSX. I would quit simming before I would do that.
Thanks
Michael Cubine
-
Reinstall FSX. I would quit simming before I would do that.
You could simply REPAIR your FSX or the SP2 (or Acceleration) installation, that doesn't require reinstalling anything else.
-
Umberto
Here is what I did and it seemed to work this time. Set commercial, GA, and airport vehicles to 0% density. Installed FSUIPC update 4858. This is just the the .dll file. Unzipp it, copy and paste to Modules in FSX. This update can only be used if the Full Installer FSUIPC 4.853 was run which I had done at the beginning of September 2012. Ran AS2012 for weather. Will be several days before return trip. If anything untoward happens I will let you know.
I had never considered the repair option. However, PHNL is the only airport or scenery where g3d.dll occurs and I only use it about once a month so I think I will just makes the changes to the density in aircraft to 0%.
The update page for FSUIPC is http://forum.simflight.com/topic/66139-updated-modules/.
Thamk you
Michael Cubine
-
Here is what I did and it seemed to work this time. Set commercial, GA, and airport vehicles to 0% density.
Ok, thats finally confirms it was never a scenery problem but, one of your AI or default ground vehicles has a problem, like a corrupted texture. If you read all the previous posts in this thread, other users fixed it by turning off GA traffic only.