Goran_M

With those specs, you won't have a problem. We made the TBM before the 20xx series of GPU's were even out.

We've seen people make comparisons in performance between the TBM and the Zibo, and stating "If you can run the Zibo, you can run the TBM".

It's been a while since I fired up the TBM, and I very rarely, if ever, fly for "fun", but I could take another look. But even if it shows what it shows in these images, it remains a problem on Laminar's end, as we use the default G1000 moving map. Edit: Just took another look. I stand corrected, but the reason I could see the aircraft in the first place was because I wasn't zoomed in as much. I can see the wings protruding from the sides of the taxiway.

Anything to do with the moving map is Laminar's area. You'll need to report this to them. I haven't seen this happen on my install. Do you have some kind of plugin like reshade that could change the saturation?

We use the X-Plane AIRAC. To taxi, you need to go into BETA, which is to the left side, between flight idle and reverse.

The 580 isn't that old. mid 2017 if memory serves. Have you tried removing all 3rd party plugins and trying again?

Make sure "Start with engines running" is unchecked when you load the TBM Also, the TBM uses the X-Plane 11.50 AIRAC. But There is a bug with that navdata, so to avoid issues, use the X-Plane 11 AIRAC.

And this would happen if you tried to calibrate your hardware with the TBM loaded and the engine off. The maintenance manager will reveal what, if anything, is wrong.

Check failures and the maintenance manager. Make sure all X-Plane default failures are set to "always working"

You can assign trim up and down to any part of the hardware you like in the TBM commands list.

Try removing all 3PD plugins and test again.

This is almost definitely a GPU problem. Are you perhaps running an AMD GPU?

Do you have any plugins that could be interfering with the state folder? Any kind of hardware that could be controlling switch positions? This is not a bug we're aware of, so it's safe to say this is isolated to your system.

Try removing the contents of the Resources/Output/TBM900/state folder, then reload the sim.

Is that the log file from an actual crash?

This is definitely something in your configuration. There is nothing that we've done that will prevent you from setting preset views. Make sure you don't have anything assigned to any hardwire, or any plugins that could be controlling your views.

The TBM reads X-Planes default navdata format. If it's not registering the newest version, then you'll need to bring that up with Laminar.

https://discord.gg/azk9Zh

There is one included in the package, under "LDJ". (Leen De Jager)

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.