Goran_M

I think the best way to get to the bottom of this whole thing, is to install a fresh copy of X-Plane, minus any scenery and plugins and then install the TBM to see what happens. Then slowly introduce plugins and restarting the sim each time until it crashes. The TBM can often times crash due to another plugins bugs, even though that plugin appears to work perfectly. I understand it can be very frustrating, but I would suggest you try this idea to put to rest any doubts about the TBM.

It's crashing because of some missing files in FlywithLUA. Try either removing FlywithLUA or reinstalling it and adding exclusions for it in your antivirus. The missing files are due to your antivirus quarantining some files.

Yes, it will read mesh ortho.

Can you delete everything out of the "X-Plane 11/Output/TBM900/state" folder and then reload the TBM in a completely different location. If it does the same thing again, can you attach the log.txt file found in the X-Plane root folder.

Can you load up the TBM again and see if it crashes. If it does, send me the TBM straight after, without reloading the sim. Every time you load the sim, it writes a new log file that overwrites the previous one. This one shows no crash and that you just loaded the DA62.

When you load the TBM, change the location to another area of the airport. A different gate or ramp. The fire should stop.

Synthetic Vision will only read terrain and scenery data. Ortho is just images overlayed on top of terrain data. So it cannot be read. Example: if the ortho has an image of a river, or lake, but the terrain/scenery data doesn't have a lake or river, it will not display on the synthetic vision.

For correcting take off p factor, use rudder trim. When in the cruise, use aileron trim.

If it's pulling to the right as much as I saw in the video, it's likely you have too much right rudder trim. Try centring it a little more. The over correction...yes...I would strongly suspect is due to the over sensitive controls. It will roll a bit to the left on take off, due to P Factor. Just want to mention, I was watching a stream this morning with the TBM, and the streamer took off and landed very nicely. That's why what I see in your video is very unusual. If you like, I can link you to a VOD if he has one.

It's due to the huge amounts of hardware out there. Some hardware works with your current settings. Could be the firmware. Could be the actual hardware configuration settings (I have a Saitek X52, and it has a ton of customizable settings in it's own software). It's all about personal preference. It can be seen as somewhat of an inconvenience, but it's definitely there for a reason.

No, I think you have your sensitivity turned up. Try these curve adjustments.

That's definitely not normal, and not something I've seen. Can you show me a screenshot of your controller curves?

It depends the systems that are implemented. The TBM uses some custom screens, driven by some pretty intense code, for the G1000, and X-Plane has trouble replaying stuff like that. Default will ALWAYS replay, because it uses some xlua and generics. It's similar to the Saab that I made. Sounds won't work in replay mode (custom sound engine that X-Plane can't read in replay) as well as systems. I'm not sure if they also work, but I'm guessing the glass cockpit airliners would have trouble displaying everything in replay, as well...due to the nature of the displays being rendered.

When you say "other X-Plane aircraft", do you mean other complex payware? (Any of the Airbuses, Boeings, jets with custom plugins)

Could you post a screenshot of the panel just as you're taking off, and describing what is happening? When someone says it's "uncontrollable", I'm immediately leaning towards a hardware calibration issue.

Need the log.txt from the root X-Plane folder after the CTD

The problems were limited to the AMD 560. It's proving a bit of a chore to work the problem, but the 580 doesn't have any issues.

Unfortunately, there's nothing we can do to work around that. Call it an X-Plane shader limitation.

The 930's major difference is the Avionics suite. People have been asking for it, but there are no plans for an upgrade at the moment.

No crash is good news. Hope you enjoy, and thank you for the compliment.

This is the first I’ve heard of this. The TBM is separate from any other activation system from other vendors. It uses a completely different method. Could you have upgraded any hardware that could trigger an activation? CPU, graphics card, ram...?

Try adding your plugins one at a time, while testing each time until it crashes. That’ll help us determine what’s causing the crash and if it can be fixed on our end.

I think I see the problem. Windows 7. I know some people might not like upgrading, and we don't tell people to do so, but running the TBM on anything under Windows 10 could be unpredictable. Even though the system specs for X-Plane are Windows 7 or higher. I'll link Saso to this post, as he's the programmer who knows all about this stuff, and he'll give you a more comprehensive response with probably even a way to stop this from happening.

How much system RAM do you have? Also, can you post a log file?