Goran_M

I did bring this up with Saso yesterday, and he thinks it's some kind of driver compatibility issue. Turning on HDR could definitely be the solution. We'll continue to investigate. Also, it appears this is isolated to some Mac's.

This is correct. This was very likely due to some kind of major failure. Probably in the electrics. Landing without gear extended will result in a damaged beyond repair TBM. What you SHOULD HAVE done was manually pump the gear down using the emergency gear extension lever located under the floor, just aft of the centre console. 25 pumps gets the gear fully extended. This would have given you a safe landing and then you would have been able to repair any electrics in the maintenance manager. 100% no. Creating a new airframe deletes the previous entries for the previous airframe. When you create a new airframe, the last one is lost forever. Possibly. But it could have been something in the default X-Plane failures module. We've seen some people report issues with the TBM failures and not being able to repair them due to some failure they have set in the default failures of X-Plane. But seeing as you have confirmed this is not the case, it's likely something else. Absolutely. We've consulted with a TBM pilot and owner (the co-founder of Foreflight) on all the little details and operating procedures of the TBM 900. A small malfunction could easily and quickly snowball into something major. As in real world ops, failures happen, and it could be any number of sequences that lead up to them. The key is to follow the appropriate checklists for the failure you are experiencing (in your case, loss of power and landing gear operation.) and do what you can to either re-establish power or land at the nearest airfield. Our TBM is extremely complex, and follows real world ops very closely. If you experience a failure of any kind, you need to follow the appropriate checklists, otherwise things will spiral out of control very quickly.

Correct. The official word... "That's not honeycomb's issue, it's deep in the innards of the TBM rendering code. This is going to require some deep dive into Cairo's font machinery." Cairo's font machinery is something inside a graphics coding language called "Cairo" which the TBM uses.

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?