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!