Author Topic: P3D V2.0 Crashing at KDFW SOLVED (Read 7259 times)

thetford569 · « **on:** November 29, 2013, 07:12:01 pm »

I just installed the Prepar3D 2.0 compatible version of FS DreamTeams KDFW Airport and I am getting this error:

Faulting application name: Prepar3D.exe, version: 2.0.9448.0, time stamp: 0x528edbf4
Faulting module name: acontain.dll, version: 2.0.9448.0, time stamp: 0x528edbc4
Exception code: 0xc0000005
Fault offset: 0x00017cd3
Faulting process id: 0x1610
Faulting application start time: 0x01ceecc3aae79ca3
Faulting application path: D:\Prepar3D\Prepar3D.exe
Faulting module path: D:\Prepar3D\acontain.dll
Report Id: 39ea37de-58b7-11e3-807d-c86000a09a2c

Upon searching I found something that indicated it possibly had to do with AI Traffic however even after disabling AI traffic I am still getting this error at the airport. Any suggestions? I have gotten the error when slewing around and when flying around and it doesn't seem to be an Out of Memory problem. It was also suggested this possibly had to do with FSUIPC however I'm also using the latest version which is P3D 2.0 compatible. I also posted this at the Lockheed P3D forum but wondered if there were any suggestions here?

Brandon Thetford

virtuali · « **Reply #1 on:** November 30, 2013, 12:04:37 am »

I also saw that error once, when switching the airplane.

We use that .DLL in ONE specific case only: after a parking is selected from GSX, a function in that library is called to destroy any AI and/or default ground vehicles on that parking. It's not used in any other cases so, if you saw that error in another situation (not when selecting a parking with GSX), it's 100% sure it's nothing related to any of our software, and surely not the scenery.

thetford569 · « **Reply #2 on:** November 30, 2013, 02:07:48 am »

Thanks for the info. I do not have GSX even installed and the error happened after starting on the runway and slewing around the airport. Hopefully I will get some more time tomorrow to mess with fixing this issue and maybe the P3D team will find the problem.

Brandon

Baylorguy · « **Reply #3 on:** November 30, 2013, 03:17:17 pm »

I can confirm that KDFW crashes every time I am in the vicinity in P3D 2.0. What is interesting is that KORD is fine... but KDFW never fails to crash to the desktop whether I am sitting on the ground or flying.

thetford569 · « **Reply #4 on:** November 30, 2013, 04:38:15 pm »

I did some more testing this morning and found that it was crashing outside of slew mode as well. I can load KDFW on the active runway which was 17R and everything g loads fine and it works. If I change to Rwy 36R, 36L, 31L or 18L I get the fatal error crash. I also tried loading in GA Parking Spot 3 which is where I usually start from if flying from this airport. It crashes there too. I was able to change from 17R to 35L, 31R, and 17L without the issues. It seems that anything on the West side of the airport causes this issue. My VRAM was maxing out around 2045 and I have a GTX260 2GB memory card. I don't think it's an Out of Memory issue though and my physical RAM still has plenty free. I also installed FSDreamteams KLAX and CYVR and I have no issues with them whatsoever. My VRAM there was 2043....just 2 below KDFW. This is an issue that only happens at DFW.

Also this is using the default F-22 loading through the default flight. All I'm doing is changing the airport location.

Brandon

virtuali · « **Reply #5 on:** December 01, 2013, 01:21:32 am »

Found the problem. It's something that existed since KDFW was released, a single object name was mis-typed so the sim couldn't find it. However, while FSX just ignore it, it seems the same issue in Prepar3D will crash it.

To get the updated files, select "Check Live Update" from the "Couatl powered products" menu, and allow the Updater to run. Then, exit from the sim and restart it.

News: