Goran_M

This is definitely not normal, as there are many people who are able to run the TBM, as well as other Gizmo equipped aircraft without issue. The only other thing I can think of is you have an older version of Gizmo installed. When you get your new drive, try re-installing the TBM, which will install the current version of Gizmo, and see if it works.

Shut X-Plane down. Try deleting all files out of X-Plane 11/Output/TBM900/state and then reload X-Plane.

Saso has added some extra terrain radar features (side profile being one of them). When I see 2 terrain radars working in 1 product, conflicts can definitely occur. 1st concern for me is your graphics drivers. They're very outdated. Can you update those first, and then, if it crashes again, we can take it from there.

The only thing I can think of is a hardware calibration issue. The feedback we've received on the steering for this latest update has been extremely positive with regards to the steering, so the fact you get this "ice skate" type of steering is a bit of a mystery.

Try resetting them to default and see if that fixes it.

Can you post a screenshot of your control curves?

Can you confirm you definitely have 1.1.9. Everyone is reporting vastly improved ground handling. Not sure why you’re getting this.

Will look into it.

Many thanks! Glad you're enjoying it

Understood. But it will help with diagnosing the problem.

Is this log from immediately after the crash? Because X-Plane is not recognizing this as a crash. But anyway, I see some potential issues. "Loaded: C:\Games/X-Plane 11/Resources/plugins/TerrainRadar/64/win.xpl (drgluck.plugins.terrain_radar)." This may potentially conflict with the terrain radar that has been added to the G1000 And this... "Loaded: C:\Games/X-Plane 11/Resources/plugins/xswiftbus/64/win.xpl (org.swift-project.xswiftbus)." I've heard this can cause problems. Try removing these 2 plugins first, and see if the crashes persist.

Nothing secretive going on. It's just that there isn't much to show yet.

Still a few things to do before we continue with the Citation. Saab update is being worked on for now.

There are no plans to add a ferry tank to this version. The real thing never had it. It IS possible, though. With careful planning and favourable winds, it can be done from France to the US. In an 850, no less.

What key bind are you using the engage beta and what is the command you are using? Can you post a screenshot of the key bind (keys and buttons section in the sim) that engages beta?

First guess is something in FlywithLUA is preventing your autopilot from engaging. Can you remove flywithlua for now, and then try again? Remember, in case you haven't done it, turn on AP Trims. Please post back if this works.

log.txt. Not TBM900_log.txt

Ok, we need to get a little more drastic now. Could you please go through your plugins folder and remove all plugins except Gizmo, and then try again. If no crash happens, replace each plugin, reloading the sim each time, to see which plugins causes the crash. Then we can decide where we can go from there. The TBM will run without issue on a bare installation of X-Plane, but some plugins can cause conflicts. I f we find out what is causing it, we can decide whether or not it's the TBM's fault, or another plugin.

Now it looks like Livetraffic is causing the crash. Quite a big one, too.

Please attach a log.txt file so I can take a look what's going on. Found in your root x-plane folder.

Is this a heading on a flight plan or a manually selected heading?

In the TBM menu, under plugins, there is an option to turn off warnings. Enjoy the challenge.

Not sure about the first one, but I'm guessing Saso coded some kind of EWS (early warning system) for the end user. In the realm of flight simming, there are very few of us who are actually type rated on a TBM 900, so we've added a few things to help prevent destroying the aircraft or the engine. No doubt, people who are type rated will have no problems knowing how the real aircraft works, and what could cause it to "break". For a $4 million aircraft, they'd better. Hot brakes can eventually boil brake fluid, and that causes the brakes to go spongy. Again, there are probably guidelines on how to tell if the brakes have overheated. Something like "Do not apply brake pressure for more than 5 seconds" or something to that effect, followed by "Do not operate aircraft for at least 15 minutes after overheating brakes." (I just modelled the thing, so I'm hazarding a few guesses. Systems are Saso's domain) I remember going for my PPL in a Beech C23, and even that was more study than I ever expected. I can only imagine what getting to know a TBM entails.

I think this is definitely one for the Laminar guys to look into. The Garmin is meant to be reading the frequencies from the apt.dat file, which we have no control over. Can you try contacting Laminar and asking them what could be a possible solution? Show them the same image you posted here, as well as the log file.

Can you try re-installing your GPU drivers. The backtrace is showing the drivers are causing X-Plane to go crazy, and then crashing. That's usually a sign of more than 2 monitors running, but in this case, it's unusual.