Goran_M

There are so many possibilities, that it's almost impossible to determine what is causing it. At the risk of sounding arrogant, not all add ons are created equally. The TBM has very complex systems and code implementation, and it could be forcing the CPU to work that little bit extra than other add ons.

The scaling problem is being looked into with the maintenance manager, and anything else associated with it.

It could very well be the time compression. Also, check your default X-Plane failures, and make sure they're all listed as "always working"

It's been determined that if the systems.xpl file fails to copy, it's either because of some kind antivirus or write permissions of the drive or folder.

It could definitely go at any time. Once it does, you'll need to use the oxygen mask, and once on the ground, you'll need to create a new airframe.

@Greaser, when you're ready to be reasonable, we'll help you. Making demands will get you nowhere. I've addressed the stuttering issue in other threads. I've also mentioned to everyone to stop mentioning "This only happens with the TBM." This statement is, literally, of no help to us. I've tried to see this stuttering issue on my end, and I'm getting nothing like what you're stating. ie. Unusable. We've seen streamers who are flying it with no issue. So I reiterate. This issue seems like it's isolated to a specific type of setup. Either with hardware or plugins. And when you're willing to accept that, we can move forward.

The cabin won't pressurize, as indicated on the MFD, and you'll get hypoxia at higher altitudes. The screen will slowly turn black.

We have a new beta in the hands of testers at the moment, and we're hoping to have it out asap.

We're getting an update ready that addresses this. We're hoping to have it out soon. May I ask, do you have AI traffic running?

You can get it through a navdata subscription.

I just noticed your visors are not showing up either. You don't have your settings set high enough to display glass. Turn them up, and the AoA will work (providing you are not using Metal)

For now, using the X-Plane 11 version of the navdata is the workaround (As opposed to the X-Plane 11.50 version). There is a lot more going into the update that we want to address. @3p13c3t0p You will get a notification of an update, should there be one, when running the TBM.

We'll need the entire log. There could be some kind of conflict that is listed higher up.

To change liveries, simply go into your Flight Configuration, and change the livery from the drop down menu.... The AoA HUD is not working in Vulkan/Metal, but we do have a copy of the TBM in the hands of some testers, and it does work in that version, although, not in VR yet. Once we get that straightened out, we'll publish another update.

Install the X-Plane 11 navdata. NOT the X-Plane 11.50 navdata

We've seen this happen sometimes, but not often. The best thing to do int hese cases is simply slew the aircraft to a different location. We think it's something to do with the scenery tile info.

I got a notification that I was quoted. Just an FYI, you're quoting my post, but the statement you quoted was typed by Marius_B.

No ETA yet. There are still a few issues left to address. No plans at this time. Focus in on the CL650.

I appreciate the comments, but, ummm...HotStart A340?

Not a waste of time. Support is part of the job. Some antiviruses are overly aggressive, and they can give you a warning on a safe file. I can guarantee you there is nothing dangerous in the TBM. So feel free to add it to the exclusion, and you should be fine.

Yeah, I wouldn't trust Avira to do anything good. https://au.pcmag.com/antivirus/58795/avira-antivirus-pro If you want a free antivirus, try AVG. If you want to stay with Avira, you'll need to create an exception in the interface, so it doesn't scan your X-Plane folder.

We recommend leaving EFM on for the TBM.

So to make sure I have this correct...You HAVE tried to install again, with antivurs turned off (including Windows Defender)? This error only occurs with some over aggressive antiviruses, so you'll have to make sure all security is disabled.

It looks like something on your install is preventing the systems.xpl file from getting written. Make sure any antivirus is disabled. A log.txt file will also help. (Found in your root folder)

A streamer has just flown the TBM a few days ago after the last major update to Windows 10. If your crashbar is not moving, there is something in your hardware of your X-Plane install that is not allowing it. Can you install a second copy of X-Plane, with just the TBM and test again. Make sure all AV software is either off, or you add the X-Plane folder as an exception to your AV.