Goran_M

Remove XPRealistic and try again. We've confirmed XPRealistic is not compatible with 11.50 b17, and this may very well be conflicting with the TBM AND X-Plane giving you this crash.

I'm done answering this question. I've been answering it for the past 1 year, 11 months and 12 days...at minimum. And the answer has always been the same. For anyone who needs to know the answer, a quick search will yield a large number of results.

If you're turning on the yaw damper after take off, and then using the rudder during flight, the yaw damper will fight your inputs. If you're landing with the yaw damper on, it will also cause control issues. Always make sure you do not use the rudder pedals with the yaw damper turned on.

I don't have ASXP, so I cant be sure. Ok, to the problem. When the issue points to an X-Plane.exe problem, as it does in this case: Backtrace is: 0 00000239B0996280 D:\XFlightSimulator\X-Plane 11\X-Plane.exe+00000239B0996280 () 1 0000000017C62CC0 D:\XFlightSimulator\X-Plane 11\X-Plane.exe+0000000017C62CC0 () it could mean any number of things. And in cases like this, whereas I understand you want us to analyze and fix this, it's easier said than done. The TBM will work fine in vanilla X-Plane. When you start adding plugins, the potential for problems increases. In your case, remove ASXP first, then test with Skymaxx installed. If crashes stop, the problem lies somewhere between the TBM and ASXP. If crashes still occur, remove Skymaxx (while keeping ASXP removed). Retest. If crashes stop, replace ASXP. Retest. Post back with results so we can continue.

Why do you have ASXP and Skymaxx installed? I could be mistaken, but having 2 weather engines will almost definitely cause problems.

Ok! Good day to you, too!

You want me to not publicly try to claim that you did not provide the information that we asked, yet you publicly state the above comment? You were asked to provide a Log.txt after you reported your problem. We did not ask for any other files. After looking at that 1 file, I saw no indication that the sim crashed. As I said, it even states the TBM had a clean exit, followed by the sim shutting down with no issue. I don't know what else you would like me to do after seeing that. You're claiming one thing. The log is telling me something totally opposite. The log file records exactly what is going on. So, as I said earlier, there is something happening that is unique to your system, causing a clean shut down, but resulting in a crash. Something I haven't seen in the 11 years I've been doing this. Of course there are more avenues we could explore, but you decided to quit after my last suggestion to you. Plugins are not without flaws. Could the TBM be causing you problems? Going by your logs, unlikely, but a slight possibility. Could it be another plugin? Highly likely. Could it be scenery? Highly likely. Could it be your internal hardware? Definitely likely. Others came in and offered to help, suspecting your scenery was the cause of the problem. You're accusing the TBM of randomly crashing in some cases, but not in others, while at the same time, dismissing the scenery or any other plugins as being the possible cause. The TBM is not coded with some uber code that spontaneously crashes your sim. Going by what you have provided, the chances of finding out what is going on is near impossible. We can only do so much from our end, short of actually sitting at your terminal and finding out what is going on. In saying all this, despite your decision to, for some reason, publicly announce your intention to switch to FS2020 in a thread that has nothing to do with that, and then trying to discredit a product I was involved in, I am still willing to help you find out what the problem is. But all I can do is make suggestions to try to eliminate all possible issues until your sim stops crashing. Short of that, the choice is yours.

SCIP is the preferred airport for testing among developers. Very little scenery, faster loading time and it's so small that the chance of any corrupted scenery is low to non existent.

So, after checking your post history, of which all of them are in this thread, I have not seen a single log file from you that shows a crash. The only log you posted shows a clean exit from the TBM and a clean shut down of the sim. So either the crashes you are experiencing are absolutely unique to your system, where the log shows no crash, but the sim crashes anyway, or something else is going on. But I'm not one to speculate without evidence. Either way, we can't help you if you can't provide what we need for us to help you. I'll consider your issue closed until you provide what we ask for.

De-activating plugins will not solve the problem. You need to remove them completely. If you keep them in the plugins folder, they still get loaded. Enjoy FS2020.

The very first concern I have is your GPU drivers are very out of date. This could, very well, be causing the crashes. I see in your log file in here that you've updated them, so try loading it again and see if the crashes persist. Failing that, try loading the TBM at SCIP, and doing a few circuits. If it doesn't crash, I would put it down to the 3rd party scenery causing the crash. If it still crashes, post back with another log file.

The wear and tear we've implemented involves the day to day running of a TBM. The X-Plane failures module is there should you wish to set things like, for example, the engine to fail at a particular time, so you can practise engine out procedures.

You'll need to reproduce the problem you were having that caused the crash. It seems you reloaded X-Plane since then and in doing so, you've overwritten the previous log file. The Log.txt is what gives us the details of the crash.

You can certainly set your own failures in X-Plane if you want to practise procedures.

Where is the log file? There is nothing attached in your post.

So far, the answers to your questions can be found in the Quickstart guide.

Just a quick FYI, there is a documentation folder with manuals that will answer all your questions. It'll save you from posting in here and waiting for a response.

We have it working in the beta for the next update, but there are some issues in VR with it. Still being worked on.

Try this. Made by the same person who coded the TBM. https://github.com/skiselkov/StopZoomingDammit

An update is in the works, and there are many fixes that have gone into it, including the pathway in the sky. The biggest issue is getting librain to work in Vulkan/Metal. A beta build of the update has been in the hands of testers, and librain integration, while making progress, is still being worked on, due to some VR issues.

Check Aircraft/X-Aviation/TBM-900/Documentation

I'll need to see your entire log file.. I may know what is causing it, but what I'm looking for is earlier in the log.

Very vague, but usually when there's some kind of warning, it's accompanied by a flashing light on the Master Caution or Master Warning. Also, a CAS message should state the problem.

In your case, you have a lot going on in your plugins folder, and my thinking is there is something in there, combined with the TBM, causing the crash. This is a case of removing all 3rd party plugins, with the exception of Gizmo, and then reloading. If it runs normally without a crash, replace the plugins 1 at a time (shutting the sim down each time) and reloading the sim until the crash occurs. The TBM runs without crashing in vanilla X-Plane.

Have a look at cockpit_builder.cfg in the TBM folder. It explains how to get bezel-less pop-ups going.