Goran_M

If you're already in the air, you can't. Just like the real thing, you have to land and then close them.

Go into your Airframe Manager and uncheck what you don't want shown (lower right).

The gear is very sturdy and shouldn't be giving you a gear unsafe warning if your landings are acceptable. Check to make sure you don't have any failures armed or enabled in the default X-Plane failures. If you did have a hard landing the first time, make sure you go through the maintenance manager and make any repairs necessary.

That actually makes sense, because I haven't seen this problem in every system. Only a select few.

This one totally slipped past me. One thing I've seen is people with AMD GPU's having weird issues with the TBM. However, it's not in all cases. I have the exact same card you do, and I don't get crashes...at all. But that may have something to do with running it windowed mode. Are you running the TBM in windowed mode or full screen?

I guess I would put it down to plugins, then. I doubt it's the TBM causing your fps issues. It's been heavily optimized to make use of all your CPU cores. I'm assuming it's just the VR headset putting a load on the CPU. Take note of the CPU time figure. The lower the figure, the better the performance. If the figure creeps up, it means there's extra load on the CPU. It could be plugins, other Operating System processes running in the background, or any other possibilities. I don't own a VR headset, so I can't run any tests on that, but from what has been told to me, VR headsets can have a significant impact on performance. One thing I can say for certain is that performance has been further optimized in this update over the last version. A sure way to tell for certain is to remove all 3rd party plugins and test again. Plugins can put a massive strain on the CPU.

Can you post your PC specs and a screenshot of your X-Plane graphics settings?

Every system you turn on will be another draw on the CPU. 25 fps seems a bit excessive (a 15fps drop isn't unreasonable), but in saying that, at 75fps, it's safe to say you have nothing to worry about.

Does it run on 11.41?

The fact it worked even 1 time, proves it’s something in your hardware or software configuration.

https://discord.gg/UKDPqn

I know exactly who you are talking about when it comes to paying for add ons again with regards to XP11 updates. And I can safely say they are the ONLY developers to pull such a stunt. I can understand your frustrations, but perhaps send a support ticket to X-Aviation on the contact page and ask them for some clarity, maybe you will be more informed on any reasoning.

With all due respect, just stating "Still a lot of people flying X-Plane 10..." doesn't really mean much without any hard figures. It wasn't my decision to pull the X-Plane 10 version. We just make the aircraft. The store/publisher makes the decisions when it comes to the actual store and what platforms are supported. If AFL want to keep supporting X-Plane 10, that's entirely their decision, or the decision of their publisher. I can understand, for whatever reasons, you may want to keep X-Plane 10, but hopefully, if you want to purchase the Saab, you could consider upgrading to X-Plane 11.

Strange hardware behaviour, but as long as it's working now.

All good. We don't want to see people having problems. We'll figure it out.

The section I highlighted has now confirmed this is something to do with your hardware or system set up. It's changed after an uninstall and reinstall, and it is impossible for the TBM to be doing it in some kind of spontaneous way after a reinstall. I'm going to notify Saso about this and see if he can make any sense out of it after getting all this new information.

Not THAT imminent. I’ll clarify by saying there’s still testing to do.

If you're running in windowed mode, try full screen...or vice versa.

Half bank is fixed and will be in the update. Update is imminent.

Log.txt is found in your root X-Plane folder.

When you post back results, can you also post a screenshot of your hardware assignment screen. Nothing specific, just the screen you see when you go into your hardware setup section.

Whenever you experience issues, the first thing we ask you to post is a fresh log.txt file. If you restarted the sim since the crash, it would have been overwritten, so if/when your problems happen again, make another post and attach the log.txt file.

The only things I can suggest is either a completely clean install of X-Plane or thoroughly go through your assignments for mixture and throttle. There is nothing that should be causing this, least of all an add on loaded prior, somehow, corrupting the code that controls the throttle, and judging by your log, with all plugins taken out, I'm almost 100% certain it is some kind of key assignment that is overriding your mixture or throttles. I've just tested a fresh install of the TBM on my PC, and all is working as it should be. I've asked other people who have a steam copy of X-Plane and they also said everything is working fine. I don't want to ask you to do a fresh install of X-Plane, but if we can't narrow this down, I'm afraid it may be the only course of action.

If you want to restore the state of the aircraft after some kind of mid flight sim shut down, you need to load the aircraft with engines running in the aircraft set up screen. As for the H Stab problem, it doesn't get affected by the scenery. however, if you've had a tail strike, or you've hit the empennage on the ground (popped a wheelie), it's highly likely you have a broken pressure vessel. This needs a new airframe, unfortunately. This is normally caused by corrupted terrain data (a dip in the ground where there shouldn't be one.). Unfortunately, X-Planes scenery isn't perfect, and there are several of this dips around the virtual world. To get around this, you'll need to load the TBM at another location at the airport.

https://discord.gg/RTWCSG