Jump to content

KDFW-KTUL CTD


ibgregr
 Share

Recommended Posts

Ok..I updated my GPU drivers to the latest and that seemed to help alot.  I had used simbrief to create the flightplan used above and the Xplane AIRAC cycle (1708) is not available to me so I deleted that flightplan and just entered my plan via the G1000 in the cockpit.  All was going very well.  I was about 100ft from touchdown and BAM....got a spinning hourglass (in my VR headset) and a frozen display.  I pulled off my headset and saw an error on the screen.  The same error was in the log.txt and I have attached that as well.  Here is what it said:

1:09:22.000 E/SYS: +-------------------------------------------------------------------------------
1:09:22.000 E/SYS: | Unexpected exception resulted from GPS update
1:09:22.000 E/SYS: | Course must be between 0 and 2*Pi
1:09:22.000 E/SYS: | 
1:09:22.000 E/SYS: | 
1:09:22.000 E/SYS: | (fm_navi.cpp:696)
1:09:22.000 E/SYS: +-------------------------------------------------------------------------------
2019-09-13 21:19:13 TBM900[except.c:232]: Caught unknown exception e06d7363
 

Log.txt

Link to comment
Share on other sites

On 9/13/2019 at 5:29 PM, ibgregr said:

Was flying along beautifully in VR from KDFW to KTUL.  Had passed KMLC and started descending.  All of a sudden...BAM...got an hourglass for a couple of seconds...couple of stutters...and then CTD.

From the best guess, this looks like a crash inside of X-Plane's core code:

EXCEPTION_ACCESS_VIOLATION    <--- This means X-Plane attempted to read invalid memory
Backtrace is:
0 00007FF641E9DA30 C:\Users\GregR\Desktop\X-Plane 11\X-Plane.exe+0000000000A6DA30 ()   <--- This is the offending code that caused the crash

If it were caused by our code, it would say "systems.xpl" somewhere in the stack trace. Since I only see X-Plane.exe there, I suspect it's been caused by X-Plane itself.

Link to comment
Share on other sites

14 hours ago, ibgregr said:

1:09:22.000 E/SYS: +-------------------------------------------------------------------------------
1:09:22.000 E/SYS: | Unexpected exception resulted from GPS update
1:09:22.000 E/SYS: | Course must be between 0 and 2*Pi
1:09:22.000 E/SYS: | 
1:09:22.000 E/SYS: | 
1:09:22.000 E/SYS: | (fm_navi.cpp:696)
1:09:22.000 E/SYS: +-------------------------------------------------------------------------------
2019-09-13 21:19:13 TBM900[except.c:232]: Caught unknown exception e06d7363

This is an assertion failure inside of X-Plane's FMS code. Please report to Laminar with the log attached. They seem to have a bug in there that is setting the GPS course variable to an invalid angle.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...