Goran_M

Going to need you to move these plug ins somewhere else, and try again.

I'll get back to you. I'm going to run some tests for this and the CTD's in 11.32 over the next 12-24 hours.

This one is out of left field, but I've seen crazier stuff. Have you installed the latest graphics drivers for your graphics card?

Stupid question. Did you check the maintenance manager to see if anything is broken?

I see the same error in other peoples log. Can you tell me step by step, what you did before the crash happens. I need to try to re-create this

log.txt in the root x plane folder

We're trying to deal with the 11.31 problem at the moment. That problem is a blanket issue for, literally, everyone who updated to 11.31. This one is an isolated case, limited to a few people. I'll get to it as soon as I can, but first thing I'll need is a log.txt file. Not the TBM900 log file, but the one found in your root x-plane folder. You could also try, if possible, installing a complete bare installation of x-plane somewhere on another hard drive. No scenery, and installing the TBM in that and see if the problem persists. To me it looks like you have missing G1000 files.

Thanks. I'm resigned to the fact there's always at least one.

Please go to the system support channel in discord and let totoritko know about this. The update is working for some, but not others. https://discord.gg/2RtDy3

Do you all have scenery spread across different partitions and/or hard drives?

Can you change to a different location and try again?

The backtrace on that log is pointing to x plane crashing from something the TBM is doing. It’s not the TBM itself crashing the sim. Try removing the plug ins and see if it fixes it. If not, you’ll need to send that log to Laminar and describe what’s happening.

Can you try removing plugins, except Gizmo, and see if the problem persists. The crash you’re getting is not the same as the crash caused by 11.31.

Need the log.txt from the root folder

Folks that have upgraded to XP11.31 and then had the TBM crashing during flight plan entry: XP11.32 is in public beta now. I've received a report that it fixes the issue. So if you are on 11.31 and were having crashing issues with the TBM, please update to the 11.32 beta! If you are still on 11.30, hold off on updating until it’s confirmed 11.32 has fixed the TBM issue.

Please post your log.txt. Also, remove any plug ins you have, except Gizmo, and test again. It’s usually caused by a conflict or something in flywithlua preventing you fro moving the crash bar.

I think you need to calm down. The TBM was thoroughly tested for more than 6 months with various streamers, and we haven't stopped working on updates since day 1. We finally had a stable release (with the exception of a few CTD's that were backtraced to XP11) until X Plane 11.31 came out, and from the moment we received the very first CTD report, Saso has been working on fixing it. He has a small group of testers making sure the next update is working with 11.31 before it goes final. Before you jump to harsh conclusions, it might serve you well to read the other posts in this forum. Calling us incompetent will not get you the update any faster.

Check your windows scaling and make sure it is set to 100%

Please post log.txt

Need you to do a little work on your end. First thing is to remove all plugins, except Gizmo, from your plugins folder, and then try again. I'm seeing quite a few plugins that could be causing the problem. Test again and post back.

Had a look and tested exactly what you did. I cannot duplicate the problem with the ECS stuff. Can you post your log.txt so I can see what's going on. Also, re the hot starts. We're aware of it and a fix is in the works. This is XP11's engine model conflicting with ours. Just an FYI, we originally made the Saab for XP10, so the hot starts were not an issue back then. No ETA yet, but we're working on it.

Could you post a screenshot or screenshots of what exactly is happening? I've tried to duplicate this, and it all works fine for me.

Definitely

It's currently getting tested. Won't be long.

Also, just for future reference, when posting about any problems, we ask that you add your log.txt file as an attachment. In this case, it isn't necessary because we know what the problem is.