Goran_M

We're not interested in anyone else's opinion about which sim is the "best" one. This isn't reddit. You deserve to have your opinion respected about which sim is right for YOU. And you deserve to enjoy whatever you want to enjoy, without argument. Exactly the same way that every single one of us, flight simmers and developers, deserves to be respected for which sim right for US. No matter if it's X-Plane, FS2020, Aerofly, DCS or Flight Gear. Screaming "X-Plane will die..." is so counter-productive, it's a joke. It only discourages more of us from even considering trying FS2020. It also discourages X-Plane developers from making add ons for FS2020. Enjoy your sim! No one is stopping you. Let the X-Plane community enjoy X-Plane.

I'm assuming you're running X-Plane in full screen mode. If so, there is a known issue with running X-Plane in full screen mode with AMD GPU's. If you have been running it in full screen mode, can you try Windowed mode, or, if you must run it in full screen mode, have another window open in the background. Please post back results.

You have a lot of failures being registered in the TBM. Do you have any failures enabled in the X-Plane failures menu?

There are a few areas of the TBM that may be iffy under Vulkan. It's unlikely, but a log will tell us more. We have been seeing some issues under AMD GPU's, also.

Does it crash while using OpenGL?

you can try de-activating. But removing it makes sure it doesn't get loaded. But by all means, de-activate first and test.

Did you check the list of incompatible add ons. If you have any of these, please remove them and test again.

Could you post a log.txt file so we can see what's going on?

It's always great to read that people are enjoying it.

This is a really bizarre problem. Official word from the programmer. Something is blocking your systems.xpl file from loading or installing. This could either be insufficient memory or your anti virus. I know you said you disabled, but if it's a multi function anti virus, you may need to turn everything off. Is there another X-Plane install that you could install the TBM on?

Not fully. It's still not working correctly in VR.

Then you definitely have an incomplete installation. If you have some kind of internet security, please turn it off. Lack of a state folder could easily explain the lack of functionality you are experiencing.

We need more information from you if you are having the same problem. If this is an activation problem, then you need to contact X-Aviation support. Other than that, I'll need to see your log.txt file

/Output/TBM900/state Just remove the contents.

You can try removing the "state" folder, or reinstalling

No plans at this time.

Only going by the official word from Laminar. No further details were given.

We've received a list confirming what is not compatible with 11.50 b17, and could potentially cause CTD's when run together with the TBM. Bandicam Ground Traffic Pilot Edge (yet to fully confirm) SimVim XJet X-Life XPRealistic xSquawkbox xSwift If you have any of these installed, and you crash when running the TBM, please remove the offending plugin and re-test.

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.