Goran_M

Refresh. It was down for a few hours. New store is up now.

We found the problem. To make it short, reinstall the TBM. Please post back if you have problems.

https://discord.gg/GEGFNf

Make sure you're using the new installer in your account.

For future reference, could you please put any Saab support posts in the Saab forums. This is so others with the same problem can hopefully find a solution. As for the problem, there is nothing in the Saab or TBM preventing you from setting your views using CTRL+ (Numpad keys). Check to see if you have some kind of "view preset" plugin installed that could be overriding this.

Assign a key or button press to “toggle thrust reverse”.

http://forums.x-pilot.com/forums/topic/17332-strange-sound-tbm-900/?tab=comments#comment-146619

I did find another topic with the same problem, and he solved it by deleting Gizmo and uninstalling the TBM, then reinstalling. Feel free to give that a try and see if it works.

Just a reminder, whenever you re-test, I'll need to see the log.txt file if the issue persists. There is literally nothing in the TBM that can spontaneously cause the throttle to start creeping forward, and each time someone else has had this issue, it was always a double assignment or rogue script entry. This is why the log file is crucial for me to see. It tells me the story of what is going on in your X-Plane install. The next best thing is to sit at your PC and diagnose the problem that way.

Not anymore. Demand for the X-Plane 10 version is almost non existent.

Please check your key assignments and find any controlling the throttle or mixture. Check for any double assignments. Failing that, please remove all 3rd party plugins, except Gizmo, and reload the sim and test. I'm suspecting FlywithLUA is the culprit, so you can try removing that first if you wish.

Please turn off AI traffic

Please post a log.txt file. (Found in the root X-Plane folder.)

If you received a response, you should get an email from support shortly. It depends on how busy it is. Keeping mind, with self quarantine going on, a lot more people are home and flying X-Plane.

Thanks for reminding me how old I am. A lot has happened in the last decade. It's no secret that Jim, who was coding the Citation, was hired by Laminar soon after the Saab was done. It's a guaranteed income working on X-Plane. I don't know any developer who would say no to that. I decided to work on a new version of the C23, DC3, (including the mobile version), Saab 340 and get up to speed on PBR workflows, which included learning how to UV map and texture 3D mesh. Prior to the Saab, I had no clue how to do this. And then the TBM 900 project fell on my "virtual desk" at the beginning of 2018. Back then, when we were working on the Citation, we didn't think demand for the Saab would be what it is. There is an overwhelming response to get it upgraded to XP11+ standards. So, to cut it short, will it be finished? We want it to be finished, and we plan to get it finished. But it all depends on Jim's and my schedules. I still have 3D model and textures. ETA? We stopped giving out ETA's a few years ago. Simply because when we do, they always backfire on us. However, I'm hoping that in the meantime, the CL650 I'm working on will give the bizjet fans their bizjet fix.

Easy to confirm. Disconnect all your hardware and reload X-Plane. If the Power Lever behaves, it's confirmed the problem lies with your hardware.

https://discord.gg/QZDAsK

Many thanks for the comments and compliments. Regarding the crash, yes, this definitely sounds like that bug. To avoid it, make sure you're established before switching. A fix will be sent in the next update.

I've seen this happen before to some other people. This is happening because something got assigned to the mixture or power controls controls (although I think it was mixture). Please check your assignments or any scripts you may have and that they are not overriding anything in the TBM.

Are you running any scripts that may be interfering with the Autopilot?

The default keys for this are F1 (Throttle down a bit) and F2 (Throttle up a bit). Try those and see how you go.

Enjoy.

The fewer the bars, the lower the AoA. In normal cruise, 1 green bar is optimal AoA. While in the green, the aircraft will not stall, and you will not get a warning. While in the yellow bars, a stall is approaching/imminent. Red bars indicate the aircraft is stalling and action needs to be taken to recover.

Press the red button on the Audio Panel

We're trying to figure out what's going on. Just bear with us for the time being. It appears this has happened to a few people, but it is not something in the TBM. As soon as we figure out what is happening, we'll post back.