skiselkov

Yes, there was a regression in 1.0.9 where we inadvertently broke persistent files created in earlier versions on Windows machines. Recreating those state files should address the issue.

@argonius Thank you for testing, will update the data.

Can you please post the Log.txt from the crashed run. Unfortunately Windows Event Viewer isn't really usable, as all it says is "Crash in the TBM code, somewhere, for some reason".

IRL there is ambient light scattering going on inside the cockpit, which helps brighten things up quite a bit. That doesn't happen in the sim due to lighting engine limitations. So if we were to just make the surfaces color-accurate as they are IRL, they'd look unusable in the shade. We've tried to strike a balance here, but we might need a somewhat more drastic approach. We'll be looking at some more workarounds for the lighting model in the next update.

The fix will be out tomorrow for everybody. You will be notified via an e-mail to your X-Aviation e-mail account, and we'll also put an announcement in our Discord group.

Thank you for testing, appreciate the help!

The screenshot got cut off there I'm afraid. Can you please expand it? Or just place the data pertaining to your setup into a comment. Text is OK, I can edit the spreadsheet on the first post and update it.

I apologize, I should clarify that! Thank you for bringing it to my attention!

Please don't disable pieces of the aircraft avionics. They are required to be loaded at the same time and changing their load state while in the aircraft can lead to unpredictable behavior and crashes.

Thank you. I'm going to mark this issue as "solved" for the time being. If you encounter a low-fps situation in the future that you believe is caused by the aircraft, please reopen this issue and we'll take another look.

We will be introducing a way to reset the aircraft to Cold & Dark on an aborted flight in a future update soon. For now, you can get a clean airframe by going into the Airframe Manager and clicking "Create new airframe" (you can then delete the old one). Also, whenever a crash-to-desktop occurs, please save the Log.txt file immediately, before restarting the simulator (otherwise the log gets overwritten). The Log is invaluable in being able to figure out what's going wrong.

This depends a lot on your graphical quality settings in X-Plane. Having a maxed out GPU means you probably have your anti-aliasing settings set very high, or scenery shadows or some other effects that put a lot of load on the GPU. Can you screenshot your Graphics Settings screen in X-Plane? We have people with far less performant machines getting higher framerates. It's really just a matter of finding the one setting that is dragging it down. Also, can you please screenshot the "Sensors" page on a program like GPU-Z. It should something like this: The reason is that the GPU memory usage statistics in GPU-Z are much more accurate than in X-Plane (X-Plane's statistics do not account for the VRAM overhead of the avionics, which is approximately 500 - 1000 MB, so it might be a matter of simply having the texture quality settings set a bit too high).

Sorry to hear it's giving you trouble. Looking at the log it seems like parts of the engine are failing due to over-heating. Can you please verify that you are keeping ITT below the red mark on takeoff? This is especially important for high altitude takeoffs with the inertial separator open. The maximum continuous ITT limitation is 840 C. Can you please make a short video of your takeoff? I'm sure that'll help shed some light on what the issue is.

Known issue with 11.30. The beta isn't yet fully supported and there's a range of known problems there.

Hello. It's always a good idea to include the Log.txt file from the X-Plane folder when reporting crashes. It should contain a good amount of information that can help us debug the problem. Also, forgive me for asking, but what's an "ITAS freq"? Did you mean ILS?

I see, it should definitely not be happening on 11.25 or 11.26. Can you please post a video of it? Seeing how it behaves might give us a clue as to the part of the code that's misbehaving.

You shouldn't need to. Of course, depends a lot on the used scenery (especially when high-resolution Ortho scenery is used).

I'm sorry, but this doesn't appear to be a bug in the TBM, but rather a bug in X-Plane itself (specifically a NULL-pointer dereference in X-Plane's terrain rendering code). Please submit this bug report to Laminar using their bug reporter: http://dev.x-plane.com/support/bugreport.html

Thank you @Floater for helping out. @cmbaviator In case you are not sure how to do it, please consult the UIGuide.pdf included in the aircraft's Documentation folder. It explains how to set up European chart access in section 7. Hope this helps.

Great to hear and thanks for letting us know! We'll get it fixed on the drivers anyway, because Mac users unfortunately can't update to newer drivers quite so easily.

We will be adding panel state resetting on creation of a new airframe in the next update. But as @ToxicResonance correct notes, if you want to keep the same airframe, you need to reset the panel state yourself.

That just means some other plugin has called the SetUnhandledExceptionFilter function and replaced the crash handler function of the TBM with their own. This crash handler function is used by the TBM avionics to generate debug traces so we can debug issues. Without a debug trace, there's nothing we can do. This is caused by one of your plugins. If you can recreate the issue, please try removing other plugins besides Gizmo from the plugins folder (e.g. by moving them to another location temporarily). If you then cause the sim to crash, it should produce a usable stack trace that we can use to debug the issue.

Are you by any chance using the 2D popup window and holding down the tilt control button and dragging your mouse away from the window? Because that can drag action causes X-Plane to never send us a mouse-button-up event, so the popup window then things you've never let go of your mouse. When holding down on the button, try not to move your mouse outside of the popup window.

We want to add the CWS annunciation over the stock G1000 (as we've done with many things), honestly just forgot to do it among the pile of work we already did to fix some of its quirks.

Thanks for letting us know, appreciate the feedback!