Products Support > Honolulu FSX/P3D
Not Pointing Fingers, Just Need Help g3d.dll crash
johndrago:
--- Quote from: virtuali on April 04, 2011, 10:02:46 pm ---
--- Quote from: johndrago on April 04, 2011, 09:03:10 pm ---I disabled UT2, and flew the same flight (KLAX-PHNL). This time, I was able to land without incident.
--- End quote ---
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.
--- End quote ---
Ok, good suggestion. Anyone else that had this problem, or similar have a suggestion to what UT2 settings work at PHNL?
Thanks,
John
Silverbird:
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.
sddjd:
--- Quote from: johndrago on April 04, 2011, 10:20:37 pm ---Ok, good suggestion. Anyone else that had this problem, or similar have a suggestion to what UT2 settings work at PHNL?
Thanks,
John
--- End quote ---
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....
virtuali:
--- Quote --- but on overwater flights from the mainland or asia the sim crashes somewhere between 100-50mi out of HNL.
--- End quote ---
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.
--- Quote from: sddjd on April 05, 2011, 09:39:49 pm ---Some discussions have circled simconnect, and as expected each party insists there is no piece of their product causing the overload.
--- End quote ---
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.
9Y-POS:
--- Quote from: johndrago on April 04, 2011, 10:20:37 pm ---
--- Quote from: virtuali on April 04, 2011, 10:02:46 pm ---
--- Quote from: johndrago on April 04, 2011, 09:03:10 pm ---I disabled UT2, and flew the same flight (KLAX-PHNL). This time, I was able to land without incident.
--- End quote ---
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.
--- End quote ---
Ok, good suggestion. Anyone else that had this problem, or similar have a suggestion to what UT2 settings work at PHNL?
John
--- End quote ---
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%.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version