Goran_M

Strange. Try a reinstall. Sometimes, issues like this can be due to a corrupt install.

Check the maintenance manager for any damage.

Default key for Park brake is V. Foot brakes is B. And these are definitely not working?

https://discord.gg/Wf4Qu9

Can you post your TBM900_log.txt file (X-Plane root folder)

If you can somehow get the airfoils from 11.4x into the install of X-Plane you have, it may work, but it's unlikely the TBM will work in an install that early. Hopefully we can get this rain bug sorted out in X-Plane Vulkan/Metal, and the update will be out soon after.

Make sure you have installed the navdata for X-Plane 11.00. NOT X-Plane 11.50. Double check the version numbers. The TBM uses all but 2 airfoils that are included with the original X-Plane install. The TBM comes with 2 custom airfoils, that are included in the installer download. Have you updated X-Plane to the latest version?

Did you check your LFE (Landing Field Elevation) before takeoff? Did you hit the tail on the ground at any point? (Check the maintenance Manager for a damaged Pressure Vessel.)

I don't know how many times we can repeat "We're working on it...", because that's what we're doing. The other reply is "It's finished and in the store." Since we can't say the latter, because it isn't true, all we can say is "We're working on it." I really don't know what else you want.

These are not implemented, due to limitations in the default G1000.

Known bug with the new navdata and it has been around since 11.50 B2. The workaround is to first switch to HDG, change CDI to NAV and then re-arm NAV. An update is coming.

Sorry for the late response. As far as the MFD configuration, can you confirm that it looks like this? (Note the aircraft southwest of my location.)

Looks like a missing scenery file.

The next update will have a fix. In the meantime, the workaround is what we suggest you use.

You'll need to map your hardware to the specific TBM commands. There is very little default functions going on under the hood, and you, very likely, mapped your hardware to some kind of command that cuts fuel.

Hell of an introduction for your very first post.

https://discord.gg/qfSU3v

That's definitely something for the developers of xswiftbus to look into. The backtrace points to xswiftbus, and this is indicating it is not compatible with X-Plane.

https://discord.gg/GKe4WX

https://forums.x-pilot.com/forums/topic/18326-tbm-900-ils-localizer-has-dissapeared/ https://forums.x-pilot.com/forums/topic/18158-issues-with-1150b10/?page=2&tab=comments#comment-152687

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?