Goran_M

No problem, and thank you.

It's not the errors or warnings I would want to see. I want to see the plugins and other things that are installed, and what they were doing that could have led up to the crash. For the record, this error appears to be very random. It happens with AI, ortho scenery (bad tiles), Squawkbox and other weird things. Personally, I haven't had it happen to me, but I have very few plugins running, and this is why it leads me to believe it's something to do with a 3rd party plugin. If it happens, please save your log file and post it here so we can take a look.

Please post your entire log file. Do you have any kind of AI traffic running?

Can you attach the whole log. We need to see the whole log.

Your log file is showing X-Plane crashing. Not the TBM. But it could be something the TBM is trying to deal with. This part has me concerned...

No, it needs to definitely be off, otherwise you will have a hard time landing...unless you want to try leaving it on for testing purposes. Usually, the rudder trim goes extreme left or right because it's fighting something you are doing. I saw it happen to a streamer once, who landed with Yaw Damper on. Please make sure all checklist items are followed on the MFD, and if it happens again, post back.

I'm not sure this is the reason, but you have a lot of missing scenery files, and I'm guessing this may be causing your issue. Could you try removing your ortho scenery folders out of X-Plane and trying again. Also, do you have AI traffic enabled?

Regarding the throttle, did you check your X-Plane failures? Is everything working in there? Nothing "failed"?

The throttle issue is not something we can duplicate, and seems to be isolated to very few people, so it's definitely something to do with calibration or some kind of script that is running. Could you include your log.txt file so I can take a look at why your FPS are low.

Did you turn off yaw damper prior to landing?

How is the CG and weight distribution? Can you post an image of it from the aircraft manager?

Best option is to just send in a support request through the contact section on x-aviation.com. I don't know what the outcome will be, as I don't do activation support. But like I said, just make sure you include as much detail as possible into what happened.

This looks like it's a very complicated situation. You'll need to contact X-Aviation support and detail absolutely everything that happened, and hopefully this can all get straightened out. Please only send 1 support request, as sending in more than one will reset the support ticket.

RAM is your problem. Big time. I think even the minimum requirement for memory for the sim is 16GB. Ortho will chew through RAM very quickly.

It appears you previously used the IXEG 737 which you did not own. The person (or you) who owned that product then de-authorized your machine over time and this has locked the computer out for good. This is a big reason why you should never use a friends account to have products you do not legally own. They have the power to ban your computer from the system forever, even if you use a new user login. This is the reason we see the support ticket under your "friends" name instead of your name.

Update your graphics driver. This will fix the crashes

Feel free to jump in the Facebook group. Lots of tips and help going on in there.

Please make sure your X-Aviation password contains numbers and letters ONLY. The crash bar won't stay up because the TBM is not activated. Try getting past your X-Aviation password and let us know how it goes after that.

I've made Saso aware of this and he's going to look into it.

Before we go any further, your GPU drivers are way too old. You're on 398.36 and the current drivers are 431.60. This is very likely what is giving you CTD's.

We need the log.txt file from the root folder. Also, check if you have any failures set in the X-Plane failures module. Do you have any external scripts running that can interfere with the avionics. As you noticed, it did work after a reinstall, so something else is preventing it from displaying properly.

Do you have any failures set in the X-Plane failures module?

Is your resolution the same on all monitors? (Keeping in mind, neither of us have experience with a monitor setup this extravagant.)

You could copy the "state" folder to your desktop as a backup, then after reinstalling, replace it. X-Plane 11/Output/TBM900/state

No plans in the immediate future