Goran_M

It's an interesting and unique dynamic. The Laminar guys are always trying to make X-Plane better, in whatever way they can, and they do encourage 3rd party devs to get in touch with them. Sometimes they listen and implement fixes, but sometimes they either don't because they don't consider something a priority or they can't because it'll be taking a step or more backwards. I'm certainly not against them moving forward, even if it means we have to fix things in our add ons (The Saab's engines are another example. Temp spikes. Sensitive Power Levers, etc...), but the flip side to that is a more accurate PT6 engine simulation within the sim. But I do think we should be able to move back to a previous, non-beta version. The reason we can't, at least in my opinion...server space and bandwidth for an obsolete version. But that's just my opinion.

Welcome to X-Plane.

@HamSammich I knew there was another topic about this. Can you try this out?

As of yesterday, Saso and Ben Supnik have been in touch, via a developer chat in Slack, to see what is going on, and determining what will be done. If another X-Plane update comes out, and it breaks the TBM update because of Laminar fixing the original issue, then it's back to square one. There are also a few issues with an unrelated issue with the Mac version of the TBM, which Saso is working hard at getting sorted out. That has been the reason for the delay. When I know more about what Laminar are going to do, I'll post back here. Ben is currently waiting for a bug report from Saso that will be done within the next 12-24 hours.

Yep. Same problem.

Just saw this. Is this what you're looking for? And it is a command. tbm900/actuators/efis/pfd1_baro_push

Please do

Can you please post a screenshot of what you changed?

Can you try moving X-Plane out of the Program Files folder and try again?

Did you enter your email address and password again? If so, does the box appear again?

Please post log.txt

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?