Goran_M

Will do

I need your log.txt from the root X-Plane folder. But only immediately after the crash

Do you have any complex external hardware? Any doubled up control assignments? Will do a test flight tonight. I might stream it. If I do stream, I'll let you know.

If something isn’t working, always check maintenance manager.

Is your AP trims switch on?

Ok

I see another issue. Some new bug fixes require you to update to at least X-Plane 11.3. Please update to the latest stable version of X-Plane. By all means, if you're nervous about updating, make a back up copy of X-Plane, and then update the current copy you are using. It's safe to say this new update of the TBM is not compatible with 11.26 or earlier versions of X-Plane.

Try 2 things, in the order given. 1. Remove all plugins except Gizmo, and try again. If no crash, then it's one of your plugins conflicting with the TBM. 2. Uninstall, delete any remaining files or folders that may be present, including the actual TBM folder. Reinstall and try again.

Did you download the new installer? Also, when installing, make sure X-Plane is not running.

You have quite a few plugins installed. I realise this is a new problem for you, but can you try the usual removing of all plugins except Gizmo, and try running it again? Just to see if that works. If it does, then the problem lies with one of your plugins.

It looks like your GPU driver is crashing. Can you try reinstalling those and see if that fixes it?

Rest assured, Cameron will make a post as soon as the installer is sorted out. Is your AP Trims switch turned on?

We'll get everyone sorted out. It's now early morning at X-Aviation, so please just wait a little longer. Saso is still looking into it. Laminar may need to do something on their end. It'll get done as soon as Saso can figure out what's going on.

Check maintenance manager. If everything is in good working order, make sure you dont have any weird assignments in any hardware you may have hooked up to the avionics.

One of the fixes... "Steering had a confusing delay on it, which made for difficult directional control."

It was a small error in version numbers. Try reinstalling.

Due to the complexity of the TBM, all support is done through these forums or the Hot Start discord. Feel free to send your log to Saso (totoritko) in the discord and he may be able to shed some light. This one is a little deeper than what I know. https://discord.gg/kyccK5

Many people agree with you. It's definitely a lifesaver. I can't take credit for it, though. Saso, the gentleman who brought me on board the TBM project, made it happen. I just made the artwork and mesh. This will be looked into. It's likely the FAA changed the URL.

Did you turn AP trims on? (Overhead panel)?

This is an issue across the board with ALL add ons. Not just the TBM. However, Saso, who coded the TBM, has recently created a plugin to stop it from happening. Please read all documentation that comes with it.

That's the one. Thanks @boredtechie

@skiselkov any ideas?

I think I saw a solution to this. I'll look for it and post back.

I can see one of the errors contributing to the crash is from the GPU drivers. Can you try updating your drivers, or reinstalling them, and seeing if that fixes the problem?

They actually do work, but they're very faint. This has been brought up before, and I asked Jim about this and if he coded something in there that's causing this. What we found, and what he coded, was that in the actual Saab documentation, the engine annunciators are very difficult, if not impossible to see during daylight hours with the sun shining directly on them. To the point that sometimes the pilots need to cover them with their hands to give them some shade to see if they are working. I'll see if I can find the page in the documents this is mentioned and post back. For the next update, we might bump up the brightness a little, but we'll have to get feedback from a couple of pilots who have generously given us their time and some very valuable feedback, on the brightness.