Goran_M

It looks like we've narrowed this down to the TBM's rendering code. It was thought this was fixed in the previous update, but apparently not. This crash is not something we've seen in too many cases, but it appears in some configurations, it still happens. This will be addressed in the next update.

Adding hours and wear? I have to say, we haven't had this one requested. I have to say, this isn't something we've looked at. When you load the TBM, it does come with some hours added, but as far as adding hours, this isn't planned. The hours do accumulate, the longer you fly, though. And parts do wear out. Even when the sim is shut down, the wear and hours are maintained for as long as the aircraft is flyable.

When the maintenance manager tells you the aircraft is damaged beyond repair, it's time for a new airframe. It's fine if you want to practise failures, but some failures will end up destroying the airframe.

Quite a long log file. While I check through it, can I ask, did you check the maintenance manager for any failures?

Feel free to test in full screen first, just to see what happens. In the handful of cases we've seen, which includes yours, this update to X-Plane should fix the crashes.

There have been some fixes in the latest update to X-Plane. Please update to 11.55 and test again. But only do so if you are ok with having a beta installed.

Much appreciated, Claudio We'll support it for as long as it's available.

Unfortunately, this is not possible due to the underlying Laminar G1000 code.

This will work with our TBM. https://apps.apple.com/us/app/tbm-performance/id641403446

Not sure about your hardware, but I have the X52 Saitek hardware, and I just checked it and works fine with assigning the controls to "Yaw". There's nothing special about the yaw, and it should work.

When running the installer, you need to point the installer to the root X-Plane folder. It will create its own folder under Aircraft/X-Aviation.

Indeed they are. And Laminar have sent numerous emails to AMD to get this issue fixed.

Try running X-Plane in Windowed mode and see if the crashes still happen. If you want to try disabling AI, go into your Flight/Flight Configuration menu. Click the AI Aircraft button in the top right, and get rid of any aircraft listed there.

That log file doesn't show a crash, but I think I see the problem. Are you running X-Plane with AI traffic turned on and are you running it in full screen mode?

I need the log.txt file found in the root folder of X-Plane that gets created when the crash happens.

Very much appreciated. Thank you.

Unfortunately, no. Try full screen with a window open in the background. No guarantees this will work reliably, though.

Ah damn. Windowed mode. I should have asked you that earlier. AMD drivers have a problem with X-Plane, some add ons, Metal and full screen mode. Either change to windowed mode or if you insist on running full screen mode, have a window open in the background. Either Safari or Finder. The latter doesn't always work.

The SCEL scenery has a very long airport name in it that's hitting a bug in the TBM's navdata parser. You can temporarily work around this issue by going into the scenery, there should be a subfolder named "Earth nav data", inside which you'll find "apt.dat". Open it up in Notepad and near the top should be a line that looks like this: 1 1555 1 0 SCEL Arturo Merino Benítez International__de X-plane octubre-2016 Just trim down the name at the end by deleting the "__de X-Plane..." stuff and save it. Then it should load fine.

Do you have the add on SCEL scenery?

The only thing I can suggest, if you really want to find out what the cause is, is to remove all 3rd party plugins, and then test while putting 1 plugin back at a time, until the crash happens again. As far as debugging, to find out quicker, unfortunately, no. There are too many 3rd party variables. The best course of action would be to install a clean copy of X-Plane, and then test. But seeing as you're on Steam, this isn't possible without removing your entire X-Plane installation, and then reinstalling a clean copy.

There are a few issues I can see that are likely causing your CTD's in order of what I think is the cause. Marginals Ground Traffic Scenery location Mem Errors as reported by the log file Try either removing the Marginal Ground Traffic plug in. This is very old, and, AFAIK, hasn't been updated in quite a while. Alternatively, try a default airport. Many developers use SCIP for testing. Try those first, then post back and we can take it from there.

This will be added in V2.