We have seen similar reports and are currently working a fix for this issue. If you can provide additional information that would help as well. What add-ons do you have installed? Do you only see this in certain aircraft or at certain locations?
Also if you have Visual Studio 2015 installed, an option would be to provide a crash dump to us.
When Prepar3D crashes, the option to debug through Visual Studio should appear. Attach to the Prepar3D process and then go to Debug --> Save Dump As to save the memory dump. Feel free to upload that dump to Dropbox or some other file server and PM me a link. Make sure you provide the full version number with each dump.
Rob McCarthy wrote: ↑Fri Aug 18, 2017 1:40 pm
We have seen similar reports and are currently working a fix for this issue. If you can provide additional information that would help as well. What add-ons do you have installed? Do you only see this in certain aircraft or at certain locations?
Also if you have Visual Studio 2015 installed, an option would be to provide a crash dump to us.
When Prepar3D crashes, the option to debug through Visual Studio should appear. Attach to the Prepar3D process and then go to Debug --> Save Dump As to save the memory dump. Feel free to upload that dump to Dropbox or some other file server and PM me a link. Make sure you provide the full version number with each dump.
I need help with this Rob, I am familiar with VS2015 at the amateur level creating c# applications. However, the link you provided provides instructions for debugging a executable and creating a dump file at a breakpoint or exception. However, we use P3D with the minimum of other applications running and it's hard to imagine that what the instructions are implying is that we should use VS2015 to load and run P3D. This is where I need help. Do we load P3D with VS2015? Do we have to create new projects? Are there Microsoft instructions for using VS2015 to debug executables created by other publishers? Thanks, I know I am revealing my total lack of knowledge but if I get pointed in the right direction I'll figure it out.
You won't need to start Prepar3D any differently than normal or create any new projects. If a crash occurs and you have Visual Studio installed a pop-up should show that gives you the option to debug the crash. If you click debug than a new instance of Visual Studio will launch with execution stopped at that location. From there you can save a dump file as described in the msdn instructions.
When you send the dump file to us we can use it to pinpoint the exact line in code where the issue occurred. Depending on the issue it could still take some time to fix, but this can help us diagnose crash issues much faster than attempting to reproduce specific conditions in most cases. As always more information helps. This combined with detailed reproduction steps as well as if any add-ons are installed will help us a great deal.
Thank you sir, I have VS2015 installed and have used it recently but no popups occur. So now I know to look in my VS2015 configuration for something that may enable that feature. Here we go.
Not really sure if this is going to be of any help, but I just had a P3D crash (v4 latest version) and saw this .DLL in the Event Viewer. I was flying the B-777 of PMDG, FL340 in an wing/engine view created by ChasePlane, took off from Greece (Samos) and was about 40 minutes into the flight when the crash happened. I was flying most to the North, maybe magnetic heading 340 in the direction of Sweden. It was not a direct CTD, P3D stayed frozen with the msgbox reporting an error, with the only button available to Close the application.
wanthuyr wrote: ↑Thu Sep 14, 2017 9:35 am
Not really sure if this is going to be of any help, but I just had a P3D crash (v4 latest version) and saw this .DLL in the Event Viewer. I was flying the B-777 of PMDG, FL340 in an wing/engine view created by ChasePlane, took off from Greece (Samos) and was about 40 minutes into the flight when the crash happened. I was flying most to the North, maybe magnetic heading 340 in the direction of Sweden. It was not a direct CTD, P3D stayed frozen with the msgbox reporting an error, with the only button available to Close the application.
