skiselkov

This is currently not possible. The aircraft cannot be taxied in the flight idle position, as it provides excessive amounts of thrust. We will look into supporting multi-lever throttle layouts in a future update.

We are looking at toning the glass reflections. They are the thing washing the displays out. Please try to increase "Control response" on the yaw axis to try and give yourself more fine-grained control near the center position. See what feels best. Please watch the "Operating the Throttle" tutorial, this is explained in the tutorial. The tutorials can be accessed via Plugins > TBM900 > Tutorials. Can you please describe a bit more about the circumstances when this happens? Mode AP modes were active, what controls have been actuated, etc. The aircraft should normally never descend on its own when it is in ALT-hold mode. The notable exception being Emergency Descent Mode when a cabin pressurization leak is detected. I assume you are not simulating cabin pressure loss. A screenshot in the moment would be perfect. This can be simply made via SHIFT+SPACE and the screenshots are saved under "Output" in the simulator. This should help shed light on the problems.

Our quick start guide is intentionally not attempting to reproduce the real avionics manuals, as those are available online. We link to the from the quick start guide. https://static.garmincdn.com/pumac/190-00709-04_0A_Web.pdf See section 6.3 "AIRBORNE COLOR WEATHER RADAR".

Can you please attach the full Log.txt from the crash. The metar.xml message is harmless and pertains to the aircraft not being able to read network weather (which isn't fatal, it simply won't show a METAR or TAF).

We have a fix for this in the pipeline. Will be rolling it out in the next update.

Yes, the avionics is heavily multi-threaded.

What sort of CPU are you running?

@trigger_xp After the trick with the Cessna, does the problem still occur when you load into the TBM directly?

Thank you, this helps.

Thank you for the log. We're tracing this down. Have a fair idea on how to resolve this. Don't worry, we'll get you up and running soon.

Are you sure this is the right log file? It's not even attempting to load the aircraft. It seems to stop after reading scenery and before a flight is actually started. The log file should contain a line such as: I/FCG: Starting new flight in Aircraft/X-Aviation/TBM-900/TBM900.acf

Does version 1.0.1 work for you? If so, can you please share your log?

Well this is a new one. Putting this in our bugtracker and I'll be taking a look at it in detail shortly. Thanks for the log!

Thank you for the log, this has helped a great deal. Working through it to trace the issue down.

@ramster211 Can you please attach a log? I'd like to confirm the GPU driver version.

@BelGeode Please confirm for me that you have an AMD GPU. We're looking at this being a compatibility issue with the AMD driver. This information will help steer me during debug.

It should print a backtrace in the Log file. Can you please attach that?

We are looking into that ntdll/kernel32dll crash. Seems to be systemic, so we should be able to get this one addressed reasonably quickly.

What texture settings are you running. If your GeForce 1060 is a 3GB VRAM model, that is our minimum and that requires turning down the texture quality to medium. The aircraft comes packed with very high resolution textures.

Great to hear, thanks for letting us know!

Yes, it's the same reason. The Mac build got accidentally broken so it's not loading any of the custom code. I expect we should have the fix ready in a few hours tops. I'll keep you folks posted and let you know as soon as it's available.

Can you please try to delete "Output/TBM900" from the sim and then trying again? This removes the persistence state and gives you a fresh config of the airplane. Please let us know if it helped.

Can you share your Log file please. Also, temporarily try to disable any extra addons (besides Gizmo) to see if that clears the issue. If yes, add them back in one by one, so we can identify where the conflict lies (if any).

This is an artifact that is due to another bug on Mac. We will be rolling out a fix for this shortly.

Can you please check if you have a Saitek switch panel if - always put the AVIONICS switch to ON. Otherwise it kill the background G1000 systems. Or unplug the panel.