Jump to content

P3d crashed when playing recorded video with A320


MSR_CEO

Recommended Posts

Hi

As shown in the title.... I'm recording a video inside p3d and the recording is going fine till the end, when I try to play it, p3d got crashed with a fatal error.

Please note that this only happens with Airbus only, not with any default aircraft or even the BBS A330.... Any one having the same problem? Any help?

I'm using p3d v 2.4 and the app log showing error with unknown reason.

Thanks in advance.

Link to comment
Share on other sites

Just a fatal error.... I tried with all other aircrafts when playing the recorded video and was fine.... Just only the Airbus... I will test with the update tomorrow

Link to comment
Share on other sites

Hi

It is still with the new SP 1.1

Event log is attached

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Prepar3D.exe
P2: 2.4.11570.0
P3: 542314d3
P4: ABX_VRi_SDK.dll
P5: 1.0.0.1
P6: 542a6eaa
P7: c0000005
P8: 00001556
P9:
P10:
Attached files:
C:\Users\mavi\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.cfg.txt
C:\Users\mavi\AppData\Roaming\Lockheed Martin\Prepar3D v2\dxdiag.txt
C:\Users\mavi\AppData\Roaming\Lockheed Martin\Prepar3D v2\scenery.cfg
C:\Users\mavi\AppData\Roaming\Lockheed Martin\Prepar3D v2\fdr.dat
C:\Users\mavi\AppData\Roaming\Lockheed Martin\Prepar3D v2\dll.xml
C:\Users\mavi\AppData\Local\Temp\WER60E8.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\mavi\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_84b4acc8b8fcdb432eae69f019f143fa5d41fce_1acb68a5
Analysis symbol:
Rechecking for solution: 0
Report Id: 5fc4c39b-75a4-11e4-afae-74d02b7f57fa
Report Status: 1

post-73682-0-91183600-1417031441_thumb.p

Link to comment
Share on other sites

  • Deputy Sheriffs

P4: ABX_VRi_SDK.dll

And this line tells us clearly that the problem is not caused by the Airbus but by a software module from VRInsight.

Link to comment
Share on other sites

Mmmm so it is the first time to have something like that.... I'm using that SD. dll with the old axe with path fsx and p3d.... Why this came up now with the new bus? Could it be related to VRI itself?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use