Page 1 of 3

Fatal Error flying Maddog X

PostPosted: Mon Oct 08, 2018 6:58 pm
by rsowder
Today after about 45 minutes in the air, I encountered the attached fatal error. I think I've had this same error flying the PMDG 737 as well. I'm using the latest version of FlyInside (1.96)

I have Orbex scenery installed and I'm also using Active Sky.

Re: Fatal Error flying Maddog X

PostPosted: Tue Oct 09, 2018 8:40 am
by Tony
Do any settings changes make this stop happening? Potentially turning off dynamic lighting, or turning down reflections a bit?

That will give us more info towards fixing it.

Re: Fatal Error flying Maddog X

PostPosted: Sun Oct 14, 2018 11:32 am
by Badwolfx
I keep getting exactly the same only mine shows line 191 where you have 117. REALLY annoying, happens at random points in flight. I have tried various configurations but nothing works other than complete re-installation of flyinside, it will then work for about 6 sessions and then the error starts to re-appear like something gets corrupted!! Did you find an answer?

Re: Fatal Error flying Maddog X

PostPosted: Mon Oct 15, 2018 2:17 am
by Tony
We are looking into this, are you in the latest gpu drivers ?

Re: Fatal Error flying Maddog X

PostPosted: Mon Oct 15, 2018 6:46 am
by Badwolfx
So i have used 390.77 / 388.59 / 416.34 (the latest) and 390.77 'seemed' to go the longest without issue, but that is just a gut feeling of time length.
The latest update of windows 10 is installed. P3Dv4.3 using 1.96 flyinside. I have suffered the issue sinces P3Dv4.1 I believe and through all of the flyinside
updates.
PC spec - i7 6700 no over clocking, 16G DDR4 and GTX 1080Ti GPU

Re: Fatal Error flying Maddog X

PostPosted: Mon Oct 15, 2018 9:40 am
by Messifan30
All new drivers do this, go back and try driver 388.33.

Re: Fatal Error flying Maddog X

PostPosted: Thu Oct 18, 2018 12:54 pm
by rsowder
I made several flights with shadows turned off and didn't have any crashes. I turned them back on and made about 3 flights without a problem. Today I increased the shadows and on approach (where it usually happens) I had the FI crash (Line 117). Here is how I had the shadows set on todays flight:

---------------------Cast------Received
Internal Vehicle----------ON---------ON
External Vehicle----------ON---------ON
Buildings----------------ON--------OFF
Terrain------------------ON--------N/A

All others were not checked.

I'm using the latest video drivers. I searched for driver 388.33, but they don't show that one. They have 388.31 and 388.43 with nothing in between.

Re: Fatal Error flying Maddog X

PostPosted: Thu Oct 18, 2018 4:49 pm
by Tony
We are looking into these certain specific errors guys.

Re: Fatal Error flying Maddog X

PostPosted: Thu Oct 25, 2018 7:45 am
by Goromo
Is there any news on this yet.....? the Line 117 crash, it happens on most PMDG aircraft also.
It is getting to the point where this software is useless to me.

Please can you find a solution to these problems, and not just tell us "we are looking into the problem" this has being going on for months now. (there are many other posts about this problem dating back to May of this year)

Last time this happened was in the PMDG 737, with Orbx England and a few UK2000 sceneries installed....(.I do not have any shader mods.)

The Nvidia driver version makes no difference, old or new, same thing happens.

I have reverted back to Flyinside ver 1.95 in the hope that this version is more stable......its not!

I cant upload the log txt or error files the site says they are "413 Request Entity Too Large"


Cheers.

Re: Fatal Error flying Maddog X

PostPosted: Sun Oct 28, 2018 10:03 am
by Messifan30
Goromo you are not the only one, flyinside is one big error program, they should give it away.I would never ever recommand this program to anyone. :(