Goran_M

Please post your log.txt after a crash. This will help us in seeing what exactly is happening, as well as any other conflicts the TBM might be having with other plugins.

Please post your log.txt file.

Nothing yet. Trying to get any remaining issues fixed (latest build just got sent out today), then when things quieten down, we'll take another look into this.

The "cheating" way would be to simply add fuel through your configuration menu when you're close to running out. Although, I think I've seen people make the trip, legitimately with careful flight planning and power settings.

The fewer bars there are, the better it is. As AoA increases, more bars will show. Staying in the green is best.

Wow! You definitely get an invite. https://discord.gg/b3ynWX

Confirming you are the same person who asked this question in discord?

No, we need to get you flying. I'll pass on your log to Saso and ask him to take a look.

Are you saying you CAN'T set your views in the TBM?

https://discord.gg/vEf3sv

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.