Goran_M

Just to add, there is a workaround. First switch to HDG, change CDI to NAV and then re-arm NAV. This should prevent further crashes until the update is out.

Thank you for your patience.

The only way we know of is to load a default aircraft with the check box left unchecked for "Start with engines running".

I'm guessing the X-Hobbs plugin may be an issue. When extra plugins are thrown into the mix, things start getting unpredictable. We'll take a look.

The fix already works...for the most part. VR is still an issue.

Even if my mother told me to give her an eta on the update, I wouldn't be able to give it. It could be days or it could be weeks. We have a bunch of testers who have their hands on a beta copy. By all means, join the discord and ask totoritko for a beta copy.

It should be quite stable with all curves set to linear.

The coming update will address the scroll wheel functions. AFAIK, all knobs will be able to use the scroll wheel.

The add ons made by Carenado and STMA are considered "lite" versions. Very light on systems and realism, but slightly more complex than default X-Plane. The TBM was created to replicate the real thing, in every way possible, and it was described as such on the product page. I'm afraid there is no option to set it to some kind of "get in and fly" mode, but in saying that, once you get the start procedure nailed, it will take less than a minute to go from cold and dark to engines running.

There's very little we can do about it, as it seems it's an X-Plane limitation. We can report it to Laminar and see if they do something about it, but it really is up to them.

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