Errors occur with any software on occasion.  I have never had a crash with P3D except an OOM once which are easy to fix.  I personally think individuals having issues with P3D have installed incompatible software that was compatible for FSX or FS9, but P3D is a complete different animal.  Or, they have installed tweaks.  Or, it was not installed properly (outside the default folder, UAC and anti-virus/malware programs disabled, run with Administrative Privileges).  If you can install a virgin P3D3.1 w/o any addons or tweaks and still get the errors you are experiencing, then I would agree.  Lockheed is at fault.  What drives any techie up the wall who develops products like P3D is when some report the Microsoft Visual 2012 error and it's not happening to them or others.  Just a few.  Strange for sure.  These people definitely do not have a virgin install of P3D and have added Addons.  That invalidates the fault of Lockheed immediately when that happens. 

 

I saw everyone installing incompatible software as soon as P3Dv3.1 was released.  They were not going to wait for the developer to make it compatible!  We (me, Vic, and Rob) warned everyone of the consequences yet people went ahead anyway.  P3Dv3.1 is a new Flight Simulator.  It is like going from FS 2000, 2002, 2004 and then to FSX.  In two years, Lockheed will probably release another major simulator version.  So, remember those days when FSX first came out and you jumped to get addons made for FS2000, 2002, and 2004 installed and started to have problems until the developers updated the products or released new versions.  We are going through that process all over again.

 

Best regards,

 

 

I personally think individuals having issues with P3D have installed incompatible software that was compatible for FSX or FS9, but P3D is a complete different animal.  Or, they have installed tweaks.  Or, it was not installed properly (outside the default folder, UAC and anti-virus/malware programs disabled, run with Administrative Privileges). 

 

Hello. Yes - all those things are possible and may be a potential cause. However, given how widespread these crashes seem to be, and the fact that a number of people who have tried vanilla re-installs are still suffering crashes, it seems there may be an issue with v3.1. This has been acknowledged by Lockheed Martin who say they are aware of the issue and it's under investigation:

http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=117444

 

Well known YouTuber Matt Davies (Belynz) suffered the same problems with the PMDG 777 on using v3.1. He reinstalled Windows and P3D but still suffered CTDs. He has now rolled back to v3 and successfully completed extended 777 flights. Hopefully Locheed Martin is able to identify the issue and resolve it.

The error or issue was acknowledged by Lockheed but it does not mean they are working on a solution.  Only a very small minority of P3D users are having this issue.  Personally I would reformat my HDD/SDD, reinstall Windows, and then P3D.  Why continue to suffer? 

 

Best regards,