Goran_M

http://forums.x-pilot.com/forums/topic/15801-the-tbm-ctds-and-xp-1132/

If all goes smoothly, a matter of days.

The owner of that actual aircraft (Jason Miller - Co Owner of Foreflight) helped us throughout the development of our TBM.

It looks like you have the same issue I'm referencing in the top post. Many thanks for this, Robert. Very much appreciated.

This looks like you’re running out of memory half way through loading. You also have a graphics card that is almost definitely struggling to keep up. Try turning down your graphics settings in x plane and closing some background programs. A good method for the graphics adjustment is to go lowest settings possible, then turn them up bit by bit until you crash.

Folks, I need to address this before it get's too much for us. I've been bombarded with PM's on Facebook, posts on Facebook, PM's on discord, a sprinkling of posts on reddit and forum posts here. Mostly from people just trying to help us with logs and feedback, but unfortunately there have been a few negative ones. So here it is. We are aware of the new CTD's with the TBM and 11.32. We were told 11.32 was going to fix the CTD's that were occurring with 11.31. This is obviously not the case. I did mention in my original post to hold off on updating if you are still on 11.30. We are doing our best in handling the support and staying visible in the community, and we would appreciate it if you are experiencing these CTD's, to not make any further posts about it. We know you only want to help, but when we get new notifications about a CTD and the Flight Plan key on the FMS, it takes time away from other support questions. On to the good news. A working update is ready to ship. It has been tested and all is good. It just needs to be packaged, and that'll be done in the next couple of days. We ask that you just please be a little more patient, and you'll be flying this sweet aircraft again very soon. Apologies if this post comes across as somewhat confronting, (It's not meant to) but it is now 3:20am, and I've spent most of the day helping toto with support...so I'm a little frazzled. We very much appreciate your understanding. For any other support related questions (not pertaining to the FMC and 11.32), please feel free to post! Cheers!

The crash, we've determined, is on Laminars end. Saso has reached out to Ben Supnik and made him aware of it. Regardless, the update he was working on will go ahead. With regards to the crash bar, there are 3 other possible solutions I can recommend. 1. Delete or move the contents of the preferences folder, and relaunch X-Plane. 2. Delete the contents of the TBM "State" folder and let it rebuild on next launch 3. Reinstall the TBM.

Cannot reproduce. I've seen cases of people having a rogue controller assignment that can affect the crash bar. Can you check your key/button assignments and make sure they're not assigned to anything to do with electrical power.

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.