Goran_M

This is the concerning part. This is what happened just prior to your crash. XLF file not exist: C:\Users\Ralph\Desktop\X-Plane 11\Resources\plugins\FM\Airports/KFCI.xlf DAT file not exist: C:\Users\Ralph\Desktop\X-Plane 11\Resources\plugins\FM\Airports/KFCI.dat OPEN scenery_packs.ini FILE OK DAT file not exist: FlyWithLua Info: Searching for Lua quarantined script files FlyWithLua Info: The folder /Resources/plugins/FlyWithLua/Scripts (Quarantine)/ does not exist or it is empty. G64: 196.632: Boot Count: 4 G64: 196.826: Run: OnKickStart.. Looks like some kind of plug in at 2 of your airport sceneries is missing some files, which led to your CTD.

You'll have to assign left and right rudder to 2 individual keys on your keyboard.

Can you post your log file?

Check your maintenance manager to see if there is any engine damage. My guess is exactly the same as yours. Calibrating the throttle with the engine off. And this WILL destroy parts of the engine, resulting in an overheat and engine fire.

Just saw the last few posts. Good to see you've sorted it out. Here's the discord link. https://discord.gg/295eqn

In future, could you please post in our support forum. We don't normally check in here too often. As for your problems with the TBM, try creating a new airframe. This should fix it.

Could you try with AI turned off? (We're still working with Laminar to try to figure out why the crashes are happening with AI)

Is it the same circumstances as this post?

Happy to see you solved the issue. Enjoy.

Ok, then you have now confirmed the problem is isolated to that 1 installation. It all comes down to a process of elimination now. There is something in your assignments on the non-beta that is interfering with the landing gear. You could try removing/deleting the files in your preferences folder, but you will have to re-assign everything.

Shut the sim down, disconnect all hardware, restart the sim and post back if it happens again. I'm suspecting it has something to do with your hardware.

The problem is a bug we have in this release. In short, it's happening when you switch from GPS to NAV1 if an ILS is tuned in and we don't have a CDI deflection yet (too far from the ILS centerline). You can work around it until the next update is out by delaying switching from GPS to ILS until you are flying the intercept leg to the ILS.

lol, let's not jump to any conclusions. There may be a chance, we just don't have anything planned. But anything is possible.

This is not implemented at this time.

https://discord.gg/rK9k6F

The old installer won't work. Regarding the brakes, nothing was done to them in this update, so this is something isolated to your PC. Before checking anything further, make sure you are applying brakes, and THEN apply park brake. Otherwise, they won't work. Failing that, please check all key strokes/button presses. Check the maintenance manager to see if the brakes have failed. If. none of that fixes the problem, you may need to create a new airframe. And what @Pivot said

oh THAT. I thought you were talking about the bezels. What you're referring to is likely the glass layer I have over the top of the screen. I mean, I suppose you COULD adjust that if you wanted to. But it's probably a normal map issue. The normal map is reflecting the light, giving off a washed out look in the sun. If it's not the reflectiveness of the glass, then it's down to the color of the actual background of the screen. I'll take a closer look and make some comparisons and if they're significant enough, I'll make a few changes for the next update. And no offense taken.

Depends what kind of lighting the MFD was under. They used to be too dark, and I went through a bunch of photos and color sampled the MFD and applied that color to the texture. The normal map may have an effect on the color due to how much light reflects off it, but the colors have been OK'ed by the testers...which includes a TBM pilot.

These stutters could be anything from scenery loading to processes the TBM is doing. There's really no way around that. The stutters do disappear with Vulkan and Metal as Vulkan and Metal take advantage of all the CPU cores.

The last resort would be to shut the sim down, empty the contents of your "state" folder, then restart the sim.

It's not a normal event to have happen, because I've never seen this happen on my end, and neither has anyone else, as far as I have seen. Even Steveokinevo just posted a new video on youtube with the TBM, and this issue was not present on his setup. So I would definitely assume this is some kind of isolated issue. The only things I can suggest now would be to check the maintenance manager and fix anything that may need to be fixed, delete the contents of your state folder or create a new airframe and then see if the problem persists.

If you left the yaw damper on while landing, and after landing, it will remain on when you next start up the sim. This is all part of the panel save state we have implemented. In future, the yaw damper must be turned off when on approach.

The only thing that changed is Vulkan and Metal compatibility, along with some bug fixes. However, AMD are still falling behind nvidia as far as driver stability and optimization is concerned, and that's causing issues with some PC's. But as I said in another thread, these issues are few and far between. I'm seeing very few issues on my Mac, and no CTD's. So it's like trying to hit a real target that's among a group of fake ones, as far as bug fixing is concerned.

Your question is not easy to answer. Is there a version of X-Plane with Vulkan that the TBM will work in? Yes. 11.50 beta. Is it "officially" supported under a beta of X-Plane? No. Vulkan is new to 11.50, and it won't work for everyone due to the enormous amount of system configurations out there (including software) that could conflict with a beta copy of X-Plane, on top of issues with X-Plane beta itself. We're now into our 6th version of the beta due to the bugs that were present in the last 5 versions. AMD drivers are notoriously unreliable. We're seeing more problems with AMD/Radeon GPU's than Nvidia GPU's. However, these are more annoyances than problems, with a very small minority not being able to run the TBM at all. This minority represents, literally, less than 1% of our customer base. Example: I have a Mac and I'm running a 5700XT, and seeing no problems on my end when using 11.50. (Other than the custom rain effects and AoA indicator not working.). But I also have very few plugins installed. Other people, like yourself, are having far more serious problems. So, to answer your question on Vulkan support. Yes, the TBM will run under Vulkan. It has ever since the first beta came out. If it wasn't compatible, 100% of the people who have the TBM won't be able to run it, and that simply isn't the case. The few people that are having issues with it are submitting logs, just as you have, and we're looking into getting the problem fixed as soon as possible.

In some cases, the workaround is still running X-Plane in windowed mode, or if you insist on running it in full screen mode, having a browser window open behind the sim. The problem is still being worked on to find a more permanent solution.