Goran_M

Ok, so if you can use the throttle through other inputs, that all but verifies the problem lies with something other than the TBM, ie. either with your hardware calibration, some kind of plug in that overrides your controls, or the hardware itself. The only thing I can suggest is to go through everything again, and make sure there isn't something else overriding your throttle inputs.

I'd love to know where you got your information. Version 2 of the Saab will be ready either late this year or some time next year. If you already have the current version, the upgrade will be heavily discounted.

Wait until X-Plane comes out of beta, then we can take another look. For now, it could be anything.

Try deleting the contents of your state folder. Output/TBM900/state That will reset the airframe.

Can't be removed. Because of the unique design of the throttle, it's there to provide reference.

Can you try disconnecting all hardware and using the manipulator to move the throttle? Want to make sure that at least THAT is working correctly for you. The next step is to make a second install of vanilla X-Plane and the TBM (no scenery) and testing on that. If it works in your second install, and not your primary one, then it's definitely something gone awry in your primary install.

Need to take more drastic steps. Can you temporarily remove skunkcrafts updater (this is known to cause problems with the TBM), FlywithLUA and JarDesign Ground Handling. Also, I would like to ask that you double check any throttle assignments in your hardware, and make sure nothing is doubled up. My hunch is that FlywithLUA may be doing something, but I'm not 100% sure.

I'm seeing a few of these in your TBM log. Are you 100% certain there are no maintenance issues, because the log is suggesting otherwise.

Can you post your log.txt file. Also, your TBM900_log.txt file.

Check your calibration and any other assignments you might have. The TBM won’t spontaneously mess up your calibration. Something must have changed. Also, just as a precaution, check your maintenance manager for any possible repairs that may need to be done.

It needs to be on.

I think the issue has more to do with the scenery developer. I can understand your annoyance at this situation, but what you're asking isn't available at this time. And to be honest, I don't think it ever will. But I can bring it up with Saso.

If you load the TBM and you don't get a notification of an update, you have the latest version.

Definitely.

Turn off any AI you have running. We're trying to figure out why this is happening with co-operation from Laminar.

https://discord.gg/AB4XGd

If many people are able to buy with this card, but you are not able to, I would say the problem is with your card or the card issuer.

I'll need to take a look at your log.txt, and am I right in assuming you have a VR Headset?

Not sure if you found a solution to this, but press the red button on the Audio panel. That will change it back to standard mode.

They're doing their best to help you. Try to work WITH them. If it's happening to you, and not to them, then it's obviously something on your system causing the issue. That IS a possibility.

Nothing has changed with the brakes in the last update. Check your key or hardware assignments. I've just tested this myself, and have no problems. The V key is used to apply the brakes.

https://discord.gg/xrDaEf

I wouldn't get your hopes up for that model. That has a lot of generic handles, levers and displays with the default FMC. You're pretty much getting what you pay for.

Why are you doing things your own way? We're here to help. There was no reason to buy another copy of X-Plane. There is something going on in your add ons that is causing a conflict somewhere. Our job is to figure out what that is. Contact Steam and ask them to refund your 2nd purchase of X-Plane. If you also purchased a second copy of the TBM, you'll need to contact X-Aviation to get a refund. If you want to get this fixed, you'll need to work with us on this. Please do not try to diagnose this problem on your own. There is a procedure to all this. If you're interested in continuing to find a solution, let me know. I'll forward your log files to Saso, and get him to take a look also.

The only reason I'm suspecting it's your scenery is because the scenery is the final entry in your log file and the TBM uses a terrain radar. If it reads a bad scenery tile or region, it has the potential to crash. An easy method to verify this is to do the same flight 1 or 2 more times over the same scenery. If it crashes both times, it's all but verified that the scenery is the problem.