Goran_M

It's something we confirmed by running some tests on our end, and then posting results and info on to Laminar. What we found was X-Plane was stuck in some kind of loop when loading the Saab at these airports.

https://discord.gg/X22GfCWF

Running full screen on an AMD GPU MIGHT give you problems. If you are, can you try running Windowed mode, and see if the problem persists. If you are already running Windowed mode, and it still crashes, post back and we can go from there.

Basically, the moving map and anything to do with navigation, including autopilot, is stock X-Plane. All the synoptics, specific to the TBM is custom.

You could always just use the mouse.

Are you running more than 1 monitor? Does this crash happen randomly, anywhere...or at a specific location? Are you running in windowed mode or full screen mode?

The navigation section of the G1000 is all controlled by Laminars code. My suggestion would be to contact them, and provide as many details as possible about the problem, and hopefully they can organize a fix for this.

It looks like it's the scenery causing the crash. Does this crash happen just at this location?

https://discord.gg/8mV455zC

https://discord.gg/8mV455zC

The aircraft needs to be flown to you from the factory.

I've forwarded this to Saso for further investigation.

This is a definite sign that the trim linkage is broken. Most likely from a tail strike or the aircraft "dropped" onto the apron when you loaded it. Check the maintenance manager for airframe integrity.

You have quite a few plugins loading, and any one of them could be conflicting with the TBM or with X-Plane. First thing to confirm is if the crash is happening at a specific location. If it is, it is very likely the scenery could be the cause. If not, what I would suggest is you download a demo copy of X-Plane, install the TBM into that, and test. If it doesn't crash (which it likely won't), start adding the plugins you have in your original X-Plane install until it crashes. I also have a Mac, and am having no issues.

Already fixed and ready for the next update

Which variant?

We know there are issues. But "too many bugs for a successful release."?? I've seen much, much worse. Your opinion is a little harsh, in my own, honest opinion. Rest assured, we're working on fixing the known issues. All we ask is that people report them as they come across them. We don't really need to know how bad some people think it is. Those opinions are purely subjective, and if I was to be completely blunt and honest, and with all due respect, they do nothing to help us fix the issues that are present.

We're still human beings, who sometimes miss things. Yes, it's a simple thing, but even simple things get missed. I sometimes forget what day it is. Not much is simpler than remembering the day.

The same can be said about any issue that crops up. The more complex the add on, the more bugs slip through the testing cracks. The TBM had an update made every day for a week because of bugs that were found by the first batch of customers.

Log files are always helpful.

There are many posts about a crash while loading, but for future reference, please provide as many details as possible, while also attaching a log file. This is likely what you are experiencing. https://forums.x-pilot.com/forums/topic/20494-tbm-900-v1113-update-released/?do=findComment&comment=162635

Can you please post a log.txt file after flying the TBM.

Ok, enough of the bickering. There will never be a "perfect" sim that everyone is happy with. What one person finds excellent, another finds annoying. I think there is a way to speed up the altimeter, that is dependant on the speed of the scroll, so I'll look into that. Let's just all get along and move forward.

I don't have VR, which is why it never occurred to me that the VR resolution was the cause. Very glad to see you got it figured out. I might put this up on the whiteboard, in case there are others with the same problem.