TBM900 freezing, finally got good capture on log file

[Javiatrix]

Hi all,

Have had problems with the TBM900 freezing midflight, usually when interacting with the PFD or MFD, but the log file hasn't thrown anything up, until now!

I'm not sure what to make of it, but timestamp 2021-01-16 04:56:42 indicated a failure to load something/numerous items... Any ideas?

Thanks in advance

Log.txt

[Goran_M]

If you have AI enabled, can you try disabling it and testing again?

Also, try it with xPilot removed.

This is just a test.  Not a solution.  It helps us determine what may be the cause.

 

 

[Javiatrix]

Hi and thanks for the reply

I always run with AI turned off, and unfortunately this did occur a few days ago 'post XPilot shutdown', but I'll do the full plugin disable and see how it gets on.

Frequency has significantly increased since copying the entire XP11 folder to another location (but currently running from the ORIGINAL location), and using manual data from Navigraph as per the ILS workaround. Not sure if related?

Edited January 16, 2021 by Javiatrix

[Javiatrix]

And some more information if it helps you at all (may be nothing/unrelated) - the aircraft does suffer 'mini freezes' when clicking the side pocket to stow the tablet, usually half a second or so, where the sound goes quiet as well (something I've usually correlated with freezes rather than loading). The same thing occurs when using the hotkey to open XPilot (it won't open it but will freeze temporarily until I press the hotkey again). Have to alt tab to open XPilot when in the TBM.

[Javiatrix]

Ok, so it's not XPilot - I've disabled both that and flywithlua, and have found a way of triggering it every time. Clicking on the pilot's side pocket (to stow/bring out the tablet) repeatedly (in/out/in/out etc) will freeze the sim after a few seconds. I can't guarantee this is the same issue as above, but it 'feels' identical - the sim simply freezes and goes silent. It doesn't crash (thus doesn't generate a crash dump), but remains frozen. Clicking on the screen after 5 seconds (default time for Windows to wait for a program I think) brings up the loading icon and 'not responding' box as expected, but interestingly the frozen sim screen reverts to an image from ~ 5 minutes ago, i.e. if it froze shortly after TOC, after doing the above the screen will then remain frozen as it was at some point in the climb.

Very strange. I would also add that MSI Afterburner reveals all values are within the 'normal' range throughout, 9GB of RAM out of 16 being used etc.

Occurs in both windowed and fullscreen.

 

EDITED - So it's not the act of repeatedly clicking the tablet in and out that's causing the freeze, it's the tablet itself. Specifically, as it hones on to the present position from whereever its default location is. The landscape whizzes past on the tablet, and just as it's about the reach the correct location, it freezes everything up. Will get a video to demonstrate.

Edited January 16, 2021 by Javiatrix

[Javiatrix]

Attached is a quick video to show replication. Again, not sure if related to the original issue but produces the same result.

[Goran_M]

That is, indeed, very unusual.  I just tried it on my end, and I don't get what you are getting (the freeze and load icon).  

Can you do this again, force quit X-Plane, and then send a new log.txt.

[Javiatrix]

Hi Goran

Certainly, I let it fester for a good two minutes in case it dumped anything else in the log, and this is the result...

Log1.txt

[Goran_M]

The first thing that screamed at me.

X-System folder:'C:\Users/jackm/OneDrive/Desktop/X-Plane 11/', case sensitive=0

 

Your X-Plane folder is in your OneDrive folder???

I would bet money that this is causing your problem.  I may be wrong, but since OneDrive is a cloud service, it could be syncing while running X-Plane and it's various plugins, leading to load time problems with some plugins.

Definitely try removing the entire folder out of OneDrive and onto your desktop or another partition.

Post back results.

[Javiatrix]

It IS on my desktop haha, I've read all the bad stories, I literally installed it to the desktop but the desktop just happens to be in the OneDrive folder, the online services of which I have turned OFF to prevent exactly that issue. Should I move my desktop into C (or maybe E) drive? I heard they have their own problems regarding permissions?

Until XP11, I'd never had to consider where the desktop is placed, only that 'it's there'!

What do you think is best?

[Goran_M]

The best place to put X-Plane is on something like [Drive Letter]:\X-Plane or the desktop (in that order), but as long as the desktop is not in a OneDrive folder.  

If it HAS to be in the OneDrive folder, then definitely put X-Plane somewhere on it's own.

[Javiatrix]

Thanks for clarifying - I'm not overly computer savvy and had it in my head that installing it to drive:\ was a bad idea because I misunderstood a post that actually referred specifically to :\program files.

Almost finished transferring to my SSD E:\ drive where it will be all by itself.

Will report back 

[Javiatrix]

Alas, same result :/ As mentioned, it's now isolated in the E:\ drive. All CPU/GPU drivers are fresh (as of yesterday). I've also removed all Ortho4XP tiles within a thousand miles, just to be on the safe side, and still no cigar.

Interestingly, I can spawn at various locations and it doesn't replicate the issue. If you want to re-enact the situation precisely, spawn at 'FBO East Signature' @ KOPF. That's where the above video and logs occurred (and still do, unfortunately).

Also just uninstalled and reinstalled the TBM, issue remains.

Edited January 17, 2021 by Javiatrix

[Goran_M]

Just tried it, and no issues.  Although, on my end, KOPF is not marked as FBO East Signature.

So to clarify, it's only happening at 1 location?

Do you have custom/3rd party scenery installed?

Because if it only happens there, then that's a sure sign of corrupted scenery.  The tablet is reading the scenery, and displaying it on the screen.  If it's corrupted, it can cause problems..like the sim "hanging".

[Javiatrix]

So, the rabbit hole deepens (sorry)!

A few points -

1) I have never been able to BEGIN a flight in the TBM in fullscreen mode. When it gets to 'loadingTBM900.acf' XP11 will simply CTD. I put this down to having an AMD Vega 56 GPU which allegedly has known issues related to running certain applications fullscreen. As a workaround, I start the flight in windowed mode, then change to fullscreen once loaded, which works (for some reason).

2) I've just discovered that if the tablet is already deployed and centred on my location (which it does sometimes, only crashing when I try to stow it again), if I then try to change from windowed to fullscreen, the sim will hang as per above.

3) It appears I can only change from windowed to fullscreen with the tablet STOWED. I have videos of this if required, but suffice to say I can verify the above.

4) To clarify, the issue relating to this topic occurs in both fullscreen and windowed display.

5) I've only been able to replicate the issue at KOPF - I couldn't do so at FACT and EGNS, although the sim does hang at seemingly random moments in the cruise, usually after some interaction with the PFD/MFD.

The reason I'm focusing on the tablet issue is it 'feels' like an identical mechanism of action as the 'hanging in flight' but obviously would seem easier to diagnose/replicate. I think if the tablet issue is cleared up, the other issue will be solved as well.

I'm about to uninstall/reinstall the default USA scenery to address any potential corruption issues, and will report back

[Javiatrix]

Same issue, so scenery corruption can be ruled out.

[Javiatrix]

I never thought to check the log after it CTD'ing during loading, but it's thrown up some (possibly?) helpful errors...

2021-01-17 17:41:06 TBM900[glctx.c:273]: Utilizing shared window
2021-01-17 17:41:06 TBM900[helpers.c:1123]: Failed to create invisible OpenGL context: A directory service error has occurred.

2021-01-17 17:41:06 TBM900[glctx.c:464]: assertion "ctx->dc != ((void *)0)" failed: 
Backtrace is:
0 00000000805DE793 E:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+000000000017E793 (glctx_make_current+93)
1 00000000805DE8A8 E:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+000000000017E8A8 (glctx_destroy+38)
2 00000000805DECE3 E:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+000000000017ECE3 (glctx_create_invisible+373)
3 000000008059A1CC E:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+000000000013A1CC (libsvs_init+3ac)
4 00000000804ADA6D E:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+000000000004DA6D (efis_init+290d)
5 00000000805540A7 E:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+00000000000F40A7 (XPluginEnable+8f7)
6 00007FFA38ED14F5 E:\X-Plane 11\Resources\plugins\XPLM_64.dll+00000000000114F5 ()
7 00007FFA38ECF0F8 E:\X-Plane 11\Resources\plugins\XPLM_64.dll+000000000000F0F8 ()
8 00007FFA38ECBCE6 E:\X-Plane 11\Resources\plugins\XPLM_64.dll+000000000000BCE6 ()
9 00007FF647175FAC E:\X-Plane 11\X-Plane.exe+0000000000B05FAC ()
10 00007FF64738FB46 E:\X-Plane 11\X-Plane.exe+0000000000D1FB46 ()
11 00007FF646D8E0E9 E:\X-Plane 11\X-Plane.exe+000000000071E0E9 ()
12 00007FF647009BFE E:\X-Plane 11\X-Plane.exe+0000000000999BFE ()
13 00007FF64683956C E:\X-Plane 11\X-Plane.exe+00000000001C956C ()
14 00007FF646955B5C E:\X-Plane 11\X-Plane.exe+00000000002E5B5C ()
15 00007FF6468A4AAE E:\X-Plane 11\X-Plane.exe+0000000000234AAE ()
16 00007FF64695B333 E:\X-Plane 11\X-Plane.exe+00000000002EB333 ()
17 00007FF64694DC95 E:\X-Plane 11\X-Plane.exe+00000000002DDC95 ()
18 00007FF646A10083 E:\X-Plane 11\X-Plane.exe+00000000003A0083 ()
19 00007FF646A1F898 E:\X-Plane 11\X-Plane.exe+00000000003AF898 ()
20 00007FF646BA6D2C E:\X-Plane 11\X-Plane.exe+0000000000536D2C ()
21 00007FF646B370AA E:\X-Plane 11\X-Plane.exe+00000000004C70AA ()
22 00007FFA5F02E858 C:\WINDOWS\System32\USER32.dll+000000000000E858 ()
23 00007FFA5F02E299 C:\WINDOWS\System32\USER32.dll+000000000000E299 ()
24 00007FF6474C0F06 E:\X-Plane 11\X-Plane.exe+0000000000E50F06 ()
25 00007FF6474C10B8 E:\X-Plane 11\X-Plane.exe+0000000000E510B8 ()
26 00007FF6474B3D56 E:\X-Plane 11\X-Plane.exe+0000000000E43D56 ()
27 00007FF6476E26D7 E:\X-Plane 11\X-Plane.exe+00000000010726D7 ()
28 00007FFA5EBE7034 C:\WINDOWS\System32\KERNEL32.DLL+0000000000017034 ()
29 00007FFA6069D0D1 C:\WINDOWS\SYSTEM32\ntdll.dll+000000000004D0D1 ()

[Javiatrix]

Disregard that - clearly a Vulkan vs OpenGL issue (maybe worth addressing in case others aren't aware of the fullscreen vs windowed situation).

Issue remains regardless of Vulkan or OpenGL.

[Javiatrix]

SOLVED (partially) - Ensuring Synthetic Vision is turned OFF on the PFD prevents the issue from occurring. Even leaving it turned on prior to shut down, the next flight will reproduce the problem. Turning it off and keeping it off has resolved it entirely.

I don't make use of Synthetic Vision (I only had it turned on for aesthetics) but may be worth investigating this further.

[Goran_M]

Interesting.  I'll file this under "weird issues with the SVS and specific GPU's".

[Javiatrix]

Nice one, like I said it doesn't affect me as don't use it, but please be reassured that I wouldn't go to all this trouble if it wasn't such an AWESOME aircraft that's obviously been a labour of love (and frustration).

Absolutely brilliant product and very, very happy with it overall.