Products Support > Honolulu FSX/P3D
Crashes to desktop **solved**
9Y-POS:
I think that UT2 has released an update to address the issue of FSX crashing which is what i think i've been experiencing, before installing this hot fix i turned of "general avaition traffic" and the CTD's stopped but now i've applied the patch that reads "Adds Runtime to help stop FSX crashes related to AI aircraft system operations" i've enabled it again and so far so good at PHNL.
I'll keep testing to see if this was infact my issue and hope maybe it helps others w/ their CTD's if they are in fact using UT2.
jordanal:
My CTD wasn't UT2 related, but it was probably traffic related. I normally only use WoAI and AIG flightplans (converted to FSX format) which are fully tested and ready for use. While waiting for FSDT to 'finally' (sorry, couldn't resist) release PHNL, I had installed a custom Aloha Cargo traffic bgl which was modified prior to using the MRAI installer. I almost never hand-jam my own traffic text files but rely on those previously tested. I then recalled this single file which may have been corrupted by the MRAI flightplan installer becuase of my manual modification to the text files.
What kept nagging me is the fact that this CTD would also happen with the simple default Baron sitting on the tarmac, let alone my PMDG aircraft, and it would only happen near the Hawain islands. Then I removed this Aloha cargo traffic file yesterday and let it the sim sit there for about 5 hours without a CTD, using the PMDG 748i. I am now ready to try my PMDG 748i from LAX to HNL again - although I will probably have a few stiff drinks enroute, just in case ;)
virtuali:
--- Quote from: jordanal on March 17, 2010, 12:31:08 pm ---Then I removed this Aloha cargo traffic file yesterday and let it the sim sit there for about 5 hours without a CTD, using the PMDG 748i.
--- End quote ---
Very good, I think this was the best possible test you could do. We can safely conclude the scenery is rock solid...
anappy:
This is for anyone still having problems w/ the airport crashing your comp on approach set the level of detail radius to small. It works
jordanal:
Well, I hate to report that I've spent another few days continuing to troubleshoot the dang CTD using a saved scenario with the default Baron. I thought this was traffic related but after two more CTD's last weekend using the PMDG MD-11, I started looking at the issue, again. I went through all my WoAI and AIG traffic and absolutely can not find a specific file (or two) which reliably contribuites to the scenario. I can usually start at PHNL with the baron and it'll sit there all day. But (read on):
Basically, with the Baron, if start the sim, and then "Go To Airport" from the FSX menu and enter PHNL, it will CTD towards the end of the scenery loading bar graph. This occurs if I "jump" to PHNL from ImagineSim's KATL, Flytampa's KBOS, or FSDT's KLAS, and so on. "Go to" PHNL and boom, CTD.
This is driving me nuts! I don't have ANY CTD occurences ever with any other high-end scenery including all the FSDT FSX airports. None, noda, silch! It is only when PHNL is involved.
I have scanned my entire FSXsp2 dedicated raid-0 Velociraptor drive array and no other PHNL named files are found outside the FSDT directory so I am absolutely sure there is no AFCAD conflict. I have re-installed the standalone FSDT manager and the bglmanx.dll is version 2.7.0.21. I am using most of the popluar FSX packages which may or may not contribute to the CTD, including FSDT PHNL (from the lastest Full Installer), F1 UTX & GEX (all the latest updates), FSGenesis, (latest versions). FSUIPC 4.6 (reg'd), WoAI traffic, and AIG traffic.
I am running a tweaked WinXP_x64 rig with 6GB of DDR3-1600 RAM and a GTX285 with 1GB of VRAM. All are finely tuned to the NickN tuning threads on F1's webite. This absolutely should never happen with the default Baron. Something is wrong somewhere!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version