Goran_M

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

Turn on experimental flight model.

Still waiting on confirmation, but according to my notes with information given to us by Jason Miller (Co Founder of Foreflight and TBM owner...so not just any Joe Blow GA pilot ), this is how they are supposed to behave, and were subsequently programmed in.

When a beta version of X-Plane comes out, the Laminar guys are very persistent in getting updates out until it's stable. These updates usually come out on a weekly basis, and they normally go to a stable release candidate within 1-2 months of the first beta build release. It's currently up to Beta 4 (5 was released but quickly pulled due to some serous issues). Hopefully, it'll only be another few weeks before X-Plane goes to RC1 (Release Candidate 1).

The way we have it modelled is if the NAV and STROBE lights are off, and the battery is on, the beacon will come on automatically. We are getting clarification that this is, indeed, how they are supposed to work.

I'm assuming you're new to the X-Plane world. No developer will officially support their add ons in an X-Plane beta build. The point of beta's is for people to try them out and submit bugs to Laminar. The TBM has been made compatible with Vulkan and Metal, but the base platform (X-Plane) is currently in an unstable beta state. If X-Plane is crashing because of something inside the X-Plane code itself, there's not much we can do about it. Especially if Vulkan/Metal is still unstable. This is the reason I asked you to try 11.50 in it's OpenGL format to see if the crash continues. Also, the reason I asked you to check if your GPU drivers were updated, was because of that very error you're asking about. By all means, you're welcome to ask other people for help, but I'm one of the people who helped make the TBM. And I look at log files every single day. We can only do so much without sitting in front of your PC. And it's usually a process of elimination.

All looks fine. You have your NAV lights switch turned on, and I see the green NAV light on the right wingtip. Could you elaborate further? There's also a Pulse switch and a strobe switch, but they're turned off. Incidentally, pressing Shift SPACE will store a screenshot of the sim in your Output folder.

Can you post a screenshot of the exterior with the lights on and a screenshot of the overhead panel?

Using an X-Plane beta means there are never any guarantees. I would recommend you roll back to 11.41. Otherwise, perhaps try running in OpenGL (uncheck "Use Vulkan driver"), or perhaps check to see if your GPU drivers are updated.

For the lights, make sure you have HDR enabled in your Graphic Settings. If you are using 11.50, the AoA will not work, as it is not compatible with Vulkan/Metal. It's being worked on.

This is the Laminar side of the G1000. Anything to do with the moving map or navigation needs to be addressed by them. The only ways for us to do it would be to code into the map directly (not possible) or to customise the map completely outside of what has been given to us. And that would involve 6-18 months worth of extra work making our own G1000.