Goran_M

Did you check the maintenance manager, and any damage on the trim linkage? A broken trim linkage will stop the autopilot from working.

Did you try re-engaging?

The hypoxia effect is X-Plane's default. I think it can be turned off in the settings. (I haven't checked in quite a while).

Incredibly bizarre. It's literally like either the TBM or your X-Plane install took on a life of it's own and did it's own thing. Glad you got it working. We'll continue to try to replicate and investigate, just in case it happens again.

Do you have any external hardware (besides mouse and joystick) hooked up to X-Plane? If so, disconnect it and see if that changes anything. If not, A reinstall may be in order. Your airframe is saved in the Output/TBM900/state folder. So feel free to back up that entire folder and put it back in to the reinstall. However, I'm almost certain this will reintroduce the problem. But feel free to try it. In the meantime, we'll continue to look into this and see if we can reproduce. The oxygen system that is displayed in the G1000 is for emergency oxygen only. It's delivered by the oxygen masks above each cockpit passenger. The cabin is automatically pressurized, and hypoxia will only occur with a ruptured cabin pressure vessel. When this happens, hypoxia will, indeed, start to come in.

Don't reinstall. Just install a 2nd copy of X-Plane and the TBM.

Can you post your log.txt file

We're still unable to reproduce this. Are you able to install a clean copy of X-Plane to another location and then install the TBM and test again? Do not install any other plugins or scenery.

This is not something we can control on our end. We have seen ShadeX do weird things to other displays, as well. This could be either a Vulkan issue or a ShadeX issue. The G1000 in the TBM uses basic, X-Plane drawing for the custom screens and default/generic displays for the moving map. I will say that LR have stated, repeatedly, that they strongly discourage developers from altering the graphics of X-Plane, by way of shaders, because in all likelihood, they will break something.

Focus is on the CL650 for now. Which WILL use Navigraph AIRAC's. After the 650 is out, then the TBM will probably get the same AIRAC implemented.

I've reported this to Saso (who coded the TBM), and he's going to check into this. In the meantime, if you feel like doing this, try a reinstall of the TBM.

Can you confirm you are still seeing a red X?

Can you post the log.txt and tbm900log.txt files. This is definitely something that shouldn't be happening, and something neither of us have come across.

The problem persists?? Can you check and make sure all X-Plane default systems, under "failures" are set to "Always working"?

ok, that's very strange. I've never come across an issue like this before. Try something. Go to your X-Plane/Output/TBM/state folder, and remove all files in that folder. (Put them somewhere safe. Don't delete them yet.) Reload X-Plane, and check the oxygen. Post back results.

It depends. Damage can occur when even loading the TBM on a scenery that forces the aircraft to "drop" due to incorrect or more accurate terrain data. Also, not saying this is the cause, but make sure "accelerated wear" is turned off.

Not refillable anymore. It's worn out. Needs to be replaced.

Traffic might be another issue. If it happens again, try it without traffic. I think there's a setting in your traffic plugin where you can disable visual traffic, but still get TCAS traffic.

Can you post a screenshot of the Oxygen section of the maintenance manager.

You have quite a lot of plugins running, and some are very likely not compatible (Marginals ground traffic being one of them). I'll need you to try from the bottom to figure out which one is causing the problem. But before you do that, if you are running in full screen mode, change to windowed mode and see if the crashes stop. This is something on AMD's end, and not something we can fix. If this doesn't work, proceed with the next steps. Can you install a second copy of X-Plane, with no scenery, and just the TBM. This will very likely work without issue. Then start adding plugins one at a time until a crash happens. Report back when the crash happens and we can take it from there.

It may be a memory issue, but in all likelihood, it is not caused by the TBM. The reason I know this, is because I also run X-Plane on a MacBook Pro, and I don't have this kind of crash. Could you post a log.txt that is generated after the crash.

https://discord.gg/xtmesQYz

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.