Goran_M

Are you talking about X-Plane or the TBM?

You'll need to contact X-Aviation support for this one. http://www.x-aviation.com/catalog/index.php and then click on the contact link. We (the developers) are unable to help with activation issues.

Interesting. Ok, thanks.

ah, ok, now I see. Perhaps in the meantime, you could assign the steering to a couple of key strokes.

You don't need rudder pedals. I have an X52 without rudder pedals and the twist on the stick works just fine. Make sure you double check everything, or even better, re-assign all commands to your hardware from scratch.

The only thing I can think of is some kind of calibration issue. As you mentioned, the TBM turned fine with your previous hardware, so the fault is not with the TBM. Also check you do not have anything else assigned to steering, as one assignment can override the other.

Can I ask you to try a flight (when you have some time) without XSquawkbox weather running and see if the crash happens again. This will help us further diagnose the crash.

Press the red button on the Audio Panel. You're in PFD backup mode. This mode exists in case you lose 1 or both PFD's. The PFD is considered more important than the MFD as it contains all the important information for flying.

You have your glass and reflections set to zero in your X-Plane graphic settings.

Please? https://discord.gg/ZT3wmc

Perhaps I could ask you to contact the developers of XPilot and see what they can make of the crashes from their end.

There's a duplicate OpenGL init from X-Plane. We don't generate those WGL_ARB_buffer_region WGL_ARB_create_context WGL_ARB_create_context_no_error... messages. And the crash occurs right after that message line... Looks like some X-Plane background thread doing something. The only thing that can prove this is trying a clean install of X-Plane with no plugins and seeing if the crash still keeps happening. Is it possible to first remove all 3rd party plugins and seeing if the crash still occurs?

Esta aeronave, e a real, não possui limpadores de pára-brisa.

I can see you're running X-Ivap. This is fine, but you will need to turn off AI while running it. For a more complete explanation, please see this link. http://forums.x-pilot.com/forums/topic/16772-tbm900-and-live-traffic-plugin-ctd/

Very happy you're enjoying it. Hope you continue to enjoy.

Anything to do with the airways or the navigation of the aircraft via the G1000 ultimately falls on Laminar, as it is their G1000 we're using as a foundation. Everything else that is TBM specific is custom coded. So your best bet would be to contact Laminar and let them know the issue with the airway.

1. Yes. Map a button to "Toggle thrust reverse". This will bring the power lever back to the beta mode and you can taxi. Bringing it back further will bring it into reverse. 2. If navdata is new, it can sometimes take a few weeks or a few months to make it into the next navdata file. However, in saying that, make sure your navdata is up to date. 3. You can literally download the actual TBM operations manual and use that. There are links in the documentation we have included. Here's one of them with the performance data included. https://www.tbm.aero/wp-content/uploads/2016/03/PIM__900_AN__E0R2.pdf

Make sure you enable the COM frequencies via the Audio panel (The panel to the left of the PFD). Not enabling it there, and trying to enable it in XPilot may very well be the cause of the crash. Also, check your display drivers. Possibly consider reinstalling them, because the log does show some kind of display driver issue.

This is the part that is sticking out at me. It's not the TBM crashing. It looks like something inside XPilot and something to do with your display drivers. Do you have some kind of extended monitor setup? The TBM can act unexpectedly when using a multi monitor setup that is not configured correctly.

Yes sir. I modelled and textured the TBM.

Oops. Sorry. I totally missed this one.

We're investigating further. I'll post back here with possible solutions.

Can you try the following: Remove all 3rd party plugins except Gizmo and remove your state folder (found in X-Plane 11/Output/TBM900) and try again. The state folder will rebuild itself.

Have you tried at different locations. Can you try at a default airport? Sometimes we see crashes like this when the scenery has corrupt terrain data. The reason you're not seeing it with other add ons is because the TBM uses a ground radar. If the crashes stop at a default airport or a different airport, the problem is almost definitely bad terrain data.

Due to the underlying Laminar G1000, this isn't possible without rewriting large chunks of the PROC entry page.