Goran_M

AP Trims

Turn on AP Trims on the overhead.

No need to troubleshoot. Toto found the problem and a fix will be in the coming update.

This is definitely a new one and one we haven't seen. Just out of curiosity, can you post your log.txt and TBM900_log.txt files

There are 2 different scenarios. Normal engine start and abnormal engine start (where you get the warnings) In a normal start up, you should never trip the abort switch. If you want to stop the engine in a normal engine start, let the engine start, and then to stop the engine, pull the Power Lever back to fuel cut off. The engine start abort switch is only used for emergency/abnormal situations during engine start. Example, when the covers and prop ties are accidentally left on the props.

The backtrace leads to something in X-Plane crashing that might be triggered by something in the TBM (hence the TBM entries). If you look at the end of the log, there are several X-Plane entries, and prior to those, it looks like something in the nvidia drivers is triggering it. We're working with Laminar to try to pinpoint what is going on, and hopefully a fix will be in the next update.

Your question was not simple. You said the instructions were for the XP10 version of the TBM. We never made it for XP10.

Yeah, something to do with how the synthetic vision reads terrain. It can only read default scenery. I'll link this to @skiselkov and see if he has anything to say about implementing it...if it's even possible to do so.

After speaking with toto about this, he found it was a bug in his code. A fix will be in the coming update.

I think you're confusing our TBM 900 with the Carenado TBM 850. The TBM 900 was only made for X-Plane 11

I've changed the pilot so he also disappears when the door is open.

Disabling plugins still loads the plug ins. The only thing I can suggest is to completely remove all plug ins, except Gizmo, run a test, then replace plug ins, one at a time, until the crash happens. It's tedious, but it will determine what is causing the crash, and it will help toto to further diagnose the problem.

Yeah, ya bunch of spoilt flight simmers.

I haven't tried it yet, but it certainly seems as though the FAA have either changed the link or something is wrong with their server. If anyone has an aerorouters account, can you try pulling charts from Europe and see if the same thing is happening.

Assign a key or button to thrust reverse. This will bring you into beta mode.

Your system is better than mine and I get a constant average of 30-40 fps. Out of the city, I get 50's. My specs i7 6700K 980ti 32GB RAM 4K Monitor

Are you flying outside the US?

Do you have custom scenery for Bankstown?

14kt headwind is possibly enough to be able to do it to a TBM.

There's a lot of stuff going on in there, but I can't see anything associated with the TBM causing the crash. If you take a look at the log, the crash happened when your ATC software was going through some checks.

The charts are pulled directly from the FAA and autorouter websites. Flying outside of these will not give you any charts, and autorouter requires you to sign in. If charts from the US or autorouter are not showing up, then it's almost definitely something on their end. There's a chance the link the TBM is using has changed, in which case, it'll be looked into. Try again on your next flight and report back.

It's extremely unlikely that Laminar are going to change what they've done. Toto will make changes in the TBM, but not until 11.3 is out of beta.

Click the STRATUS USB port when the yoke is visible.

Jump in the discord and mention it to toto. https://discord.gg/k5A78z

Thanks for letting us know.