Goran_M

Just try to disable X-Life in the plugins menu. That SHOULD prevent the exception handler errors.

There's your problem. You need to assign Toggle thrust reversers WITHOUT the #. This is under Engines/Basics. The reason your brakes are getting hot is because you're taxiing in flight idle. Not Ground Idle. Ground Idle is the beta range. The aircraft will still want to move, but much slower.

No issues reported so far.

Yes

Not sure why it wouldn't be working, other than you missed something in the configuration in either the TBM or PE. Hopefully someone else can chime in with any advice on what you could have missed.

Right above the anti ice panel, there is a button labelled "MICRO" (Normal operation) and "MASK" (when you are wearing the oxygen mask). Make sure it is set to MICRO. Other than that, everything should be fine. Nothing was done to that area of the TBM in the update.

Glad you got the visuals sorted out. So if I understand your controller issue correctly, when pushing up on the hat switch, the TBM pitches up, and vice versa?

Like Cameron said, you're not being very clear. Which commands are not responding?

The textures have already been lightened quite a lot. To make sure my monitor was calibrated correctly, I actually purchased a Spyder X Pro to make sure everything is textured as accurately as possible. On top of that, I requested feedback from the testers on the latest textures, and they unanimously agreed the textures are spot on, and need no further adjustment. Might I suiggest you double check your monitors brightness calibration. Can you give us more background on your controls? Do you have any external scripts that might be interfering with them? What kind of hardware are you using?

Well, you may not agree with the response, but to say it is "unsatisfying", and forming your own opinion based on that response, is a bit too harsh. Rest assured, the update is very close to being completed.

Ok. Known issue that wasn't caught during testing. It's a straight forward fix and will be done soon. Apologies.

We need the log.txt file (not the TBM900_Log.txt) to identify what is causing the crash. If it happens again, can you please post it.

It'll be added in the next update.

We have narrowed down the Exception handler error to AI traffic, which is why I didn't open your log file earlier. I just opened your log file now and there is no exception handler error in there. Your log shows a clean shut down. Is this the log file immediately after the crash or did you restart the sim and then post the log file? Also, your GPU drivers are outdated.

Turn off AI for now.

What exactly are the problems you're experiencing? We may be able to find a solution if it isn't something you need the update for.

Hell of a response. I have to say, it was very double sided. "You're doing great work, but some of your policies really suck!". That's what I was getting from your post. We can all understand the frustration people like yourself are going through, but we're going through the same thing. And then some. I've had people tell me some very harsh things in private. Demanding refunds. Telling me I don't know how to run a business (even though Hot Start is not my company, I do, however, treat it as any partner would). Demanding access to their previous version. All this does not speed up the process. We're doing the absolute best we can. A few weeks for an update is, I think, more than reasonable. A very well known dev company for FSX took 18 months for an update for one of their add ons to come out. X-Plane itself can take months between updates. The X-Plane beta process can also take months. We (Hot Start) are very visible in the community, and I personally frequent all the social media sites to check to see whether people are having problems with not only my add ons, but also the TBM. I understand your main issue is people not having access to an earlier version of the TBM, but that is something that, as you say, needs to be taken up with X-Aviation. However, I do know there may be issues with the older version running on X-Plane 11.41, so there would be issues either way, anyway. We love that people love this add on as much as they do. It's very motivating and fills us with a massive sense of accomplishment. The best we can do is just work as hard and as fast as we can. We do this on weekends, holidays, and at ridiculous hours. 3am is not an uncommon time for either Saso or myself to quit for the day and go to sleep. Regardless if it's for working on a new add on or a free update. All I can promise you is that we're doing our best at making sure people get what they want as quickly as possible.

Gizmo is automatically installed into the Resources folder of X-Plane when you install an X-Aviation add on. If it is disabled or removed, or if the TBM is not activated, it won't run correctly. Make sure you meet all these criteria and it should work. Failing that, try a reinstall.

https://discord.gg/DjfyQa

Even though it's virtual currency, it still stings just a little when you need to pay it.

Please Join the discord and address this with Saso (totoritko). The fact you can't find a solution to this is really strange. https://discord.gg/DjfyQa

Perhaps check your X-Plane failures, too. Make sure they’re all set to always working.

I've noticed this in only a small handful of people. It seems to be isolated to the users hardware, as the vast majority of people are not having any issues at all. Can you check all your hardware and the drivers and make sure nothing is overriding your settings.

Response from Saso (Who coded the TBM) I tied that CAS message to the X-Plane vacuum pump system. But we never cause the system to fail, so something else must have caused it to fail. There's simply no code to write to the vacuum system fail dataref, so I know for sure it wasn't generated from our code. I did a quick search through the code: $ fgrep -Ir vacuum * engine.c: dr_t vacuum_ratio; engine.c: fdr_find(&drs.vacuum_ratio, "sim/cockpit/misc/vacuum"); engine.c: CAS_SELECT(dr_geti(&drs.vacuum_ratio) < VACUUM_MIN, CAS_VACUUM_LOW); fail_mgr.c: { "Engine", "Vacuum pump failure", XPFAIL("vacuum") } The stuff in engine.c is simply the trigger for the CAS message - it looks at sim/cockpit/misc/vacuum and if it's low, it triggers the CAS message. The thing in fail_mgr.c is our custom failure control window (Flight > Edit Failures). That thing doesn't spontaneously generate failures, only on command by the user.