Goran_M

No. Those errors can be ignored. The backtrace points to X-Plane crashing due to some kind of indirect conflict between 1 or more plugins, X-Plane itself, Windows and the TBM. The normal process of elimination is to remove all plug ins, and then retest. It's a matter of simply moving the folders out of the plugins directory to another location, then reloading. Not all plugins are bug free, and it can take a small thing to cause them to crash. You have quite a few plugins loaded, but let's start with if you have any AI running? People have reported that by turning AI off, the error stops. If so, this is a temporary workaround we're asking people to do while we look into fixing it.

I'll add this one to the list for V2

You have quite a few plugins. Going to ask you to do the usual "Remove all plugins except Gizmo and retry." If, after doing this, the crashes stop, replace the plugins and retry each time until it crashes, and then post back when you found the offending plugin. This will help us in determining what is going on.

This kind of issue is usually associated with a part of the avionics not working properly or turning itself off. If nothing is assigned to any kind of hardware or script, check the maintenance manager for any failures

For future reference, it'd be better if you posted screenshots so we can see exactly what everything looks like. Landing gear not coming down could be hydraulics or power issues.

Have you tried removing all plugins (except Gizmo)?

Do you have any part of the avionics assigned to any hardware?

I'll look into adding this for you in a future update.

Please post your PC specs and a log.txt file

Do you have AI Traffic enabled?

Saso is still working on this. It’s proving a little tricky.

Can you turn off AI and try again. Please post back if it returns everything to normal.

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.