Goran_M

Can you try removing all your plugins, except Gizmo, from the Resources/plugins folder, and see if the problem persists. Don't delete them. Just move them to another folder. Please report back if the problem goes away.

Can you confirm if the TBM performed better prior to installing Skymaxx?

Go to your graphics settings and make sure HDR is enabled.

If you don't have the TBM tool tray on the left in windowed mode, then the plugins are not loading. I'll take a look at your log.

It's possible X-Plane is loading the sky and cloud textures. Maybe try to turn down graphics options in Skymaxx.

I don't think Skymaxx is causing this. What happens when you turn AI off?

Wow. Haven't seen that one before. @skiselkov , all yours, buddy

@sundog

Can you show me what you're seeing with the splash screen?

@skiselkov

The SD card is for anyone with an autorouter account. https://www.autorouter.aero/ It's free to join, and once you join, you can directly download and bring up charts on the MFD by entering your autorouter email and password on the "SD Card". This will only give you European charts. The TBM also has the ability to download charts directly from the FAA, but with the release of the new navdata, there was a bug in that, so it won't work. A fix will be in the next update. The next update will also have dedicated navigraph navdata.

You're welcome!

You'll find your settings in the upper right corner of the sim among the other icons.

Check to make sure HDR is on in your settings.

Check the maintenance manager. Something might be broken.

I'm guessing you have ortho installed for KORD. You need to have the underlying terrain. Synthetic vision can't read ortho.

AP Trims

Turn on AP Trims on the overhead.

No need to troubleshoot. Toto found the problem and a fix will be in the coming update.

This is definitely a new one and one we haven't seen. Just out of curiosity, can you post your log.txt and TBM900_log.txt files

There are 2 different scenarios. Normal engine start and abnormal engine start (where you get the warnings) In a normal start up, you should never trip the abort switch. If you want to stop the engine in a normal engine start, let the engine start, and then to stop the engine, pull the Power Lever back to fuel cut off. The engine start abort switch is only used for emergency/abnormal situations during engine start. Example, when the covers and prop ties are accidentally left on the props.

The backtrace leads to something in X-Plane crashing that might be triggered by something in the TBM (hence the TBM entries). If you look at the end of the log, there are several X-Plane entries, and prior to those, it looks like something in the nvidia drivers is triggering it. We're working with Laminar to try to pinpoint what is going on, and hopefully a fix will be in the next update.

Your question was not simple. You said the instructions were for the XP10 version of the TBM. We never made it for XP10.

Yeah, something to do with how the synthetic vision reads terrain. It can only read default scenery. I'll link this to @skiselkov and see if he has anything to say about implementing it...if it's even possible to do so.

After speaking with toto about this, he found it was a bug in his code. A fix will be in the coming update.