Goran_M

Thanks for the report.

Go into your maintenance manager and check the damage. Sometimes a repair is all that is needed. If the damage is too great, just create a new airframe in the same maintenance manager.

Apologies. I thought it was your navdata that was out of date. The obstacle database is different, but the same thing applies. It is not controlled by us. The G1000 simply reads what is there. You could try contacting Laminar, as they are responsible for implementing that.

When this happens, it's usually a sign of bad terrain data. Were you at a custom airport scenery? Another cause is loading the TBM and THEN calibrating your power lever/throttle. The power lever of the TBM must not be moved when the engine is off. You will do some serious damage to engine components this way (which will be displayed in your maintenance manager).

Your navdata is outdated. You can keep the current version you have or you can subscribe to navigraph and get regular updates.

Please post your log.txt and a screenshot of your X-Plane settings.

Delayed for the time being. The gentleman creating the sounds has been forced to put his regular job as first priority for now, due to COVID-19. I can't say any more than that. However, because of the delay, more work is being put into the systems to bring the fidelity up a few notches. We should hopefully have more to show when our sound guy comes back.

Are you running in windowed mode or full screen mode? Full screen mode might cause issues with AMD cards.

Please post a new log file. I have the exact same graphics card you do, and I'm having no issues, so I'll be very interested to see what the log contains. If you want to install it in 11.50, do so knowing that we don't officially support beta's, and you will most likely experience CTD's. Also the rain and icing effects will not work under Vulkan/Metal at this time. It is being looked into, and hopefully a patch can be made when 11.50 goes into release candidate status.

Always treat beta's as test versions. Not release candidates. Expect problems. But thanks for the report.

If you want to continue testing, by all means, add the plug in back, and see what happens. But treat it only as a test flight. If not, just enable/disable the plugin in your plugin admin menu.

The reason the drivers are important is because the TBM uses a plugin called "librain", which adds rain and icing effects to the TBM. librain uses complex OpenGL code, which is dependant on current GPU drivers. Other aircraft use this, but only if they are added by the developer. librain was developed by Saso Kiselkov, who coded the TBM. This is why the crashing only happens to the TBM, but it will also happen to other add ons that use librain.

Usually, when this happens, it's a sign you have outdated GPU drivers. Can you confirm you have the most recent drivers for your AMD card?

Then it might be a good idea to disable/remove all 3rd party plugins at once, except Gizmo, and then try it again. This is the best way to diagnose such things. Please post back with results.

Will need your log.txt file found in the X-Plane root folder, but only after it freezes. If you have since used X-Plane after the problem occurred, the log file will have been overwritten. Make sure you post a log file from immediately after the crash.

That's definitely a plugin.

You're the 4th person to report this kind of crash who has the AOS plugin installed. I'm seeing a common theme here so far. Could I ask you to disable or remove all 3rd party plugins, except Gizmo, and try again. You could try just removing AOS for now, and see if that has any effect, but failing that, try taking them all out.

Please contact X-Aviation support for this issue.

As I suspected. Your graphic card drivers are very outdated. Please update to the latest graphic card drivers. I am almost 100% sure that will fix the problem.

not that one. There is another one called "Log.txt" in the same folder. Please post that.

You have a LOT going on in 11.41. Log files that are 1MB or more, generally, are evidence of a bloated installation. After looking through it, the first thing I noticed is outdated drivers for your GPU. The first step I would suggest is updating those to the latest (445.xx). Following on from that, I can see a lot of custom scenery. The problem with custom scenery, especially if it's freeware, is the terrain data may not match what's visible. And that can lead to a crash when the TBM is loaded, due to the way the terrain radar is coded. I'm just going to suggest the most obvious and easiest solution, and that is to disable all 3rd party plugins except Gizmo, and try that first. If that works, re-enable each plugin until the crash stops. If not, pull out your custom scenery folder and put it on your desktop, and try reloading the sim. Feel free to pull the scenery first if you wish. Please post back results.

This could be a bug in the AMD drivers. We'll need to do more investigating. In the meantime, have you tried using X-Plane in full screen mode? If the problem persists in full screen mode, try Windowed mode. I know it may seem like a pain, but this may be the only workaround for it for now.

Can you please post your log.txt file.

https://discord.gg/wr6CsE

I'm going to have to get you to go hardcore. Time to remove all 3rd party plugins, except Gizmo, then test again. If it works as expected, replace plugins one at a time. I see a few plugins that may be of concern, but it's impossible to say which one might be causing the problem. The only reason I say this is because looking at your original log file, it tells me X-Plane is crashing due to something not directly related to the TBM. If it was the TBM causing the crash, it would be listed in the backtrace at the bottom of the log file. I'm afraid the only way to narrow it down is by removing or disabling your 3rd party plugins. Please post back results so we can take it further.