Goran_M

Interesting. Thanks for letting us know.

Did it crash in the last log file you sent? I see a plugin stopping, but nothing crashing. If it is crashing, it's a very unusual crash. Can you confirm?

Your log file shows nothing on the TBM. Only that you loaded the FJS 737. Did you load the TBM, sim crashed, then loaded the 737, THEN send the log? If so, you'll need to reload the TBM, and if it crashes, THEN post the log. The log file gets overwritten each time you load the sim or a new aircraft.

When things calm down a little bit, I'll get around to finishing the XP11 version.

Thanks for that info @DwightP980 Didnt even know.

Denada

We have an unpublished tentative list at the moment. But nothing definite.

The G1000 is the default X-Plane G1000 with some extras added by Saso. So as far as showing systems, map orientation and map modes, this is all limited by the default G1000.

That navaid error is nothing. You can ignore it. I think you need to get drastic now. Remove all plugins, except Gizmo, and then try again and see if it crashes. If not, add the plugins 1 at a time, and see if it crashes. You have quite a few plugins that can be the cause, but we need to be sure. And if a plugin has a bug, or bugs in it, it can cause the TBM to crash.

Ah, now I understand. Sorry, no, this is not possible. The code does not work this way. To get to reverse, in the real thing, you must go through beta. This is how it was programmed.

Espero que Google traduzca esto correctamente Si asigna un botón para cambiar de reversa, puede controlar la versión beta y la reversa con el hardware del joystick. La palanca hace clic en la palanca de potencia en beta

Yes, definitely add power gradually, instead of slamming it full forward. The real aircraft has a power lever that is restricted by some friction.

Sure, go to "X-Plane 11/Output/TBM900/state" and delete the files from in there. Reloading the aircraft will rebuild the files.

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?