Goran_M

If you have AI turned on, can you turn it off and see if that fixes the problem? If it does, we'll take a look at finding some kind of workaround in a future update.

Do you by any chance have AI turned on?

The engine will get realistic wear and tear. Things will eventually fail. Autorouter is just a connection to the autorouter website. Check you have an active account, and also check your firewall isn't blocking it.

Please remove all plugins, except Gizmo, and try the maintenance manager again. Please post back if this fixes it. If it does, replace the plugins one at a time and test until it crashes again.

Please remove all plugins except Gizmo and see if the CTD's persists. If the CTD's go away, replace the plugins 1 at a time until it crashes. When it crashes, that is the offending plugin and then we can possibly chase that up. Many times it's the plugins conflicting with the add on. Until we know which one it is, it's hard to know how to troubleshoot.

The log file you posted shows no crash at the end. It looks like X-Plane just quit without a crash. I've had it happen to me on the rare occasion. Coupled with your brakes issue, I'd suggest the usual routine. Remove all plugins except Gizmo, try it again, then replace plugins 1 at a time until it crashes. I'm almost positive your brake issue is the result of a double assignment.

Half bank is actually fixed. We're getting all the engine issues fixed first before we push the update out. We haven't actually checked the glass yet. I seriously doubt it's anything you can do to fix. To me, it just looks like crossing mesh, but in any case, we'll find out what it is and, if it's something on our end, a fix will be in the next update.

Exception handler error. Saso is currently trying to pinpoint what's causing it. They were a lot more frequent in earlier versions, but still, in this current build, some users are experiencing them.

Understood, but it is likely the TBM conflicting with another plugin (most likely scenario) or the TBM exposing some problem within X-Plane itself. If it was a fault in the TBM itself, the backtrace would point to the TBM. That's why the first course of action is to remove all plugins and then replace them 1 at a time to find the one that is conflicting with the TBM. Then we can narrow it down and find out what the problem is. If it's either the plug in or the TBM.

We're using the default Garmin 530, so if it's compatible with that, there will be no issues.

Did you touch ANYTHING during the startup? Also, check your hardware calibration. If you have an axis that is not assigned, it can bounce around, and this might interfere with the autostart.

Just to add to this. The VS ring and HDG ring (The ring around the VS ring) are both spring loaded. That's why it's a click, drag slightly, and hold. Letting it go will snap it back to the centre.

The backtrace points to X-Plane crashing, but there are no references to the TBM. This one looks like one of those "Please remove all plugins except Gizmo and try again" crashes. So if you could try that, and see if it happens again. If it doesn't crash with plugins removed, it's one of the plugins causing the crash.

This looks like X-IVAP crashed on you. Couldn't load missing files.

LOVE the graphic!

Make sure trims are in the right position by reading the trim indicator. Also, check winds. There’s nothing that should be leaning the aircraft otherwise.

Apologies, I was half asleep when I read your post. Thought it was charts. Could you tell me where you were when this happened?

That's a weird one. It doesn't really show a crash. It shows X-Plane stopping in the middle of a chart download. Can you try downloading the same chart, and see if it happens again. If it does happen again, can you remove all plugins, except Gizmo, and repeat, and, as before, see if it crashes...then post back with any findings.

Can you attach the actual log.txt file. We need to see the whole thing. You can only do it after the crash without starting another flight, so if it happens again, please take note of this.

Not really sure why you're seeing that. I'll load it up and see, then post back some time tonight or tomorrow.

I wish! My wife is the only one who can get rough ETA's on stuff we do, and I can't even give her one yet.

This is one for @skiselkov

Next time, you can just attach the file to your post. No need to copy and paste the contents. The drops you're describing are fairly minor, and if you're maintaining 45-50fps, with an occasional slight drop, I would say that's a successful and smooth running installation.

If it happens again, can you please post a fresh log file.

When in sim, can you go to the top drop down menu, click on View->Show Click Regions. Are there green click regions on the keypad? If there are, and it still doesn't work, try a reinstall.