Goran_M

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.

I'm sure you read the top post, Gav. Sometimes, when the criticisms go too far, into the "ridiculous" category, it turns into trolling. We can take criticisms, but not when they're lines of crap.

Someone said they had to re-calibrate their hardware each time the TBM was loaded. This is definitely not common, and I'm guessing it has to do with the individuals set up. But try that as well as controller sensitivity.

Whenever there is a backtrace like this one, it's something within the sim itself causing the crash with the TBM loaded. One of these is associated with the latest X-Plane navdata, as posted by another TBM user. When he removed the navdata, the TBM loaded without issue. Another crash is associate with X-Planes AI, so you could try disabling all AI and see what happens. As you can see in the log excerpt, there are multiple X-Plane references that lead up to the crash. I've spoken to someone at Laminar about this and he's looking into it. We're hoping the next update (X-Plane or the TBM) will get rid of this crash. It doesn't happen to everyone and sometimes it happens at certain airports. Shouldn't be too long.

I see this is your first post, so this is for future reference. If there is ever a problem, the 1 golden rule is to please post your log.txt file found in the root x-plane folder. That will give us a good head start into what is causing a crash. Before you do this, can you remove all plugins out of the resources/plugins folder (do not remove gizmo) and place them somewhere else. Preferably on your desktop. Restart the sim and see if you get a crash. Many times, a crash can be caused by another plugin conflicting with an aircraft add on.

Try rolling back to previous drivers. If it works after rolling back, it's definitely the driver...OR...something in your nvidia configuration.

Did you try removing all plugins, except Gizmo, and then try the TBM to see if it crashes?

The save state function has 1 or 2 little bugs in it, and is being worked on. This is one to add to that. Thanks.

What happens if you don't load a saved flight? Can you try to shut down the sim, without saving, then restart and click on "resume last flight"? After that, reload the sim and select "Start new flight" with the TBM. Please report back.

Does it always happen at that location? Does it always get fixed if you start up at a different airport? Can you check at a few different airports, and post back the results? What airports are you using and what airports give you the red XX's? (Want to see on my system)

Second try, meaning you had then enabled AI?

This answers a few questions. I was talking with Saso about this, and he was confident it was not the TBM, but something on Laminars end, causing the CTD's. Many thanks for this!

It's a strange one, because, from what I have seen, it doesn't happen to everyone. Me included.

Still trying to nail this one down.