Goran_M

Do you have any other add ons with pop out windows? Also, what happens if you try OpenGL?

I'm not really sure what you mean by "can you suggest the settings..."

The VACUUM LOW CAS gets triggered when sim/cockpit/misc/vacuum is less than 6.

I was going to reply with the question, "Are you using an AMD GPU, and then saw the last part of the post. Laminar have been trying to get AMD to fix a few graphics issues. Let me ask, are you also running in Metal/Vulkan?

This has been fixed in the last update.

Could you post your TBM900log.txt file. That'll tell me more about the panel state of the aircraft. Maybe something in there will tell me about something staying on.

I meant did you have any external hardware hooked up to the sim, with a rogue switch assigned to some kind of power dataref that is keeping it on? We've seen this happen before.

You have a lot going on by way of plugins and scenery, and my first guess would be you are getting crashes with corrupted scenery and the TBM trying to read corrupted terrain data. Do these crashes happen in any other areas? If not, can you try doing the same flights with the custom scenery removed, to test what would happen? To really eliminate the possibility of the TBM being the cause, could you try installing a clean copy of X-Plane, with no scenery and no plugins, and just the TBM, and then checking for crashes? If no crashes happen, try installing the scenery and plugins 1 or 2 at a time, and re-test.

Do you have any hardware that may be drawing power from the battery, that you are unaware of?

I wouldn't consider it a "bad move", per se. We just wanted to create something different and more advanced, that we had access to.

To not make it?

https://discord.gg/Wfb8dYEB

This is a common problem we're seeing with AMD GPU's and running X-Plane in full screen. This is not something we can fix with code, nor is it something Laminar can fix with X-Plane. This is something AMD needs to address. The workaround is to run X-Plane in Windowed mode (the better solution for now), or if you insist on running X-Plane in full screen mode, have a window open in the background. It can be an explorer window or your browser, but a window needs to be open while X-Plane is running in full screen mode. This works most of the time, but it has unpredictable results. Try either or both of these options, and post back results. Hopefully, this is something AMD addresses some time soon.

I'm guessing you are running X-Plane in full screen (not windowed) mode. Am I correct?

This is the command for the cockpit manipulator. It should work. tbm900/actuators/cb/light

I couldn't tell you the issue with your hardware. We have quite a few people using the TBM with the Logitech Extreme stick, and they have no problems. One of our testers has that exact hardware. The only thing I can suggest is that you make sure everything is calibrated correctly and all axis assigned.

I'll need the complete log.txt file immediately after X-Plane crashes.

Looking through the forums, I've already replied to you. less than 2 hours after your initial request for help. Unless something else comes up, I'll consider your issue solved.

I've sent Saso your log file. He's still investigating. For more direct contact, consider joining our discord.

Mojave is too old of an OS to run the TBM on. Please consider updating to, at least, Catalina.

After looking at the screenshot more closely, the time to TOD is 1 minute 18 seconds. Not 1 hour and 18 minutes. Apart from that, there really is nothing more we can do with the default G1000 code. We did what the SDK allowed.

You're running MacOS 14. This is very likely your problem. macOS: Version 10.14.6 (Build 18G7016) Please consider upgrading to, at least, Catalina.

This looks like a problem between Littlenavmap and X-Plane. In any case, post a log.txt file and I'll take a look. Make sure you post a log file from a crashed session.

Can you post the entire log.txt file

I was corresponding with him through DM, here on the forums, and he confirmed on a clean install, with no plugins, there were no crashes. Following this, I instructed him to add the plugins and scenery back, 1 at a time, until it crashes, then to post results to determine if it's something we can fix or the author of the offending add on needs to fix.