The Home of FlyInside Flight Simulator FFS FSX P3D and X-PLANE Message Board

Fatal error: error-20160815T192518

Hi,

This error has happened 8 times in the last 5 days. Took a test flight to a regional airport about 20 mins away. Landed, set up the GTN750 to take me to another airport about 120miles away. about 50 miles into the flight the error froze P3D and returned me back to the FI loading screen which was frozen too and no tracking.

The forum up-loader won't allow me to upload the error txt file because it's 1.4MB.

Help!

If you compress it using zip or such, maybe it will go?

Thanks for the report Ted. Could you let me know two things?

1. Does this still happen in FlyInside 1.6?
2. Does changing the "Asynchronous Timewarp Mode" from "Low-Speed/High-Stability" to "High-Speed/Possible-Artifacts" (under FlyInside Settings) fix the issue, or lead to a different crash?

Thanks,
Dan

Hi Dan,

This error has not happened since that report.

As I have been working on getting to the bottom of my instability issues, I have thought it was hardware - my overclock. That OC has worked fine for the last 12 months and I never had to hit the reset button while I was using XP10. I have removed those settings and returned to the MSI Genie overclock for the time being to see if it improves. It might have been that.

BUT over the last few days the GTN 750 has been freezing during the flight inexplicably. I logged a support ticket with Flight1 and I happened to mention that I was using Process Lasso to manage affinity for all running processes. I was told that others had solved the freezing problem by uninstalling Process Lasso. So I uninstalled it last night.

I put in an Affinity setting within P3D config to use only four of the six cores now that Process Lasso wasn't doing it. Last night, and it is early days, everything worked perfectly - even starting up SteamVR first shot which used to start sometimes in Extended Mode or not at all. Trying to get SteamVR working at the beginning of each session sometimes took several reboots and Deleting Local Content etc which was very disheartening. It could take up to 20 minutes to get into the cockpit.

Last night - BAM - worked immediately (which I think is the first time since I have had the Vive. I am growing in confidence that the root cause of my stability issues has been either the overclock and/or Process Lasso. Now that things seem to be working, I will not change anything and see how it goes but I am sure it is not the OC.

I also found the problem with losing the compositor which I will relate in the other thread I created.

Thanks Dan - you have created a brilliant piece of software engineering which has completely changed my flight sim experience.