Goran_M

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.

If switches aren't working, it means Gizmo is not installed or the Saab is not activated. If you move the mouse to the right edge of the screen, do you get a "toolbar" that slides out? If so, how many icons does it have? If not, then it's definite that you don't have Gizmo installed.

You have quite a lot of plugins, and the crash is happening before the TBM even starts to load. This tells me X-Plane is crashing due to some conflict between plugins. I see you have two different types of ground traffic, and some other plugins I haven't heard of. Your best option is to start from scratch, and remove all these 3rd party plugins, and then reload the TBM. Leave Gizmo in the plugins folder. If the TBM loads successfully (it should), replace the plugins one by one until the crash happens. That will be the plugin that is the cause of your problems.

It looks like your scenery is corrupted by looking at your log file. Take a look at the last section, particularly the second last line. I'm guessing the crash only happens while in this area. Not sure if it's the same issue, but we're in contact with Laminar about a possible scenery issue with some default airports.

This is his youtube channel. There are a few beta TBM videos in there. There is also a video where he shows flying our TBM with Foreflight.

1 aircraft cannot make the sim crash while using another aircraft. Again, please post your log.txt so we can help you and determine what is causing the crash.

Known issue. We're fixing up the more serious bugs first. This fix will come, probably, in the next update.

To turn off the AP alarm, bring up the yokes and press the red button

That's just it. We didn't make it a crazy size. My one is the standard size that takes up a small section of my monitor. I have no idea why it's so large on your screen.

All these issues have been posted and addressed

Fixed for the next update

Corrupted scenery is getting very annoying.

Are WE considering it? No. It's Windows only, and Jim and I both work on a Mac.

Remove JarDesign ground handling plugin and try again. Please post back results.

which was modelled incorrectly. When the directional gyro starts to go out of alignment over time, giving incorrect headings, pressing the HDG slave will align the DG to the AHARS.

Assign them to the PROP (for both CL's at the same time), or PROP 1 for Left and PROP 2 for right command in your settings.

Door logic has been recoded. But we'll look into it. Braking is now down to just using datarefs, which means V key for Park brakes and B key for foot brakes. We're looking into commands. The Power levers should work with a regular axis. Nothing was actually changed in that. Have you tried re-assigning an axis? Not aware of this one, and no else has reported this. I just double checked on my system, and sounds are working fine. Perhaps try a reinstall?

The only other option I can think of is to delete the contents of the state folder, but that will delete the airframe and all panel save state files, as well.

Can you grab it anywhere in the highlighted area on the left, and drag it around?

Not sure if you understood the post. The HDG slave is not HDG sync...like some people believe. The heading slave function slaves the magnetic heading related to present flux detector readout. Since X-Plane now accurately simulates gyroscopic drift and flux_detector errors, HDG slave now functions correctly.

I'll note it down. I don't really want to tilt it down, but we can widen the cone.

Point number 1.