Products Support > Honolulu FSX/P3D
CTD coming into Honolulu
johndrago:
--- Quote from: wb2002 on December 14, 2011, 07:49:32 am ---
--- Quote from: johndrago on December 08, 2011, 07:19:47 pm ---
Hi Dave,
Do you have (UT2) Ultimate Traffic II installed?
- John
--- End quote ---
Hello John. Is this significant about UT2?
--- End quote ---
I can't speak for Dave's exact issue yet, but there is a thread in this forum, where myself, and a couple others had issues approaching PHNL, and getting crashes. After we made a couple changes to UT2 (turned off moving jetways, and turned off GA traffic), all was well. We believe there was some overload with the amount of traffic generated, as well as the graphic strain to start moving the jetways when the airport was starting to pop into range.
Either way, it fixed both of our issues. The other most common issue with this type of crash is duel AFCADs. I didn't have any, but other have. Here is the thread:
http://www.fsdreamteam.com/forum/index.php?topic=4201.0
- John
virtuali:
--- Quote from: johndrago on December 14, 2011, 07:09:23 pm ---as well as the graphic strain to start moving the jetways when the airport was starting to pop into range.
--- End quote ---
Not in that case, because he reported a crash at 20 nm, but the loading range for all objects at PHNL is exactly 10 nm, nothing related to the airport is loaded at 20 nm so, it's surely something else, most likely AI-related.
airforce806:
Everytime I load Honolulu intl I get a crash to desktop. All other fsdt scenerys are working. Only when I load honolulu does my sim crash
virtuali:
--- Quote from: airforce806 on January 20, 2012, 09:42:48 pm ---Everytime I load Honolulu intl I get a crash to desktop. All other fsdt scenerys are working. Only when I load honolulu does my sim crash
--- End quote ---
I don't see why you are attaching your issue, that doesn't have anything to do with this, with the fact that you (according to your description of the problem) can't load *FSX* after having installed PHNL.
This thread discussed an entirely different problem, since it's discussing a crash *approaching* PHNL, but it has been already established that, since it happens at 20 NM out, it's entirely unrelated to PHNL, and most likely related to AI.
So please, don't confuse other people reading this with your problem, which is entirely different, and please continue on its own thread, posting about the same problem on two separate threads, which one entirely unrelated (and that discussed a problem which wasn't even caused by PHNL in the first place) will not give you more chances to get replied to. Your issue has been already being dealt with, without the need to cross-post in other unrelated threads.
airforce806:
I figured a crash is a crash in regards to the PHNL scenery and thought both issues perhaps could be linked.
Navigation
[0] Message Index
[*] Previous page
Go to full version