skiselkov

Can you please attach your Log.txt so I can take a look? Not being able to move controls indicates a problem in loading the aircraft's custom code and the Log file will no doubt contain the exact reason.

We are hard at work on a poly-reduced version of the model, so users with lower-specced GPUs can run the model without issues. We're also analyzing why seemingly very fast GPUs (GTX970 and up) are having trouble. We suspect either a driver tuning issue, or some sort of software incompatibility, as other users with similar setups report no framerate issues.

We have a fix for this in the pipeline. Will be coming out later today with a patch.

We have a fix for this in the pipeline, so it should no longer occur. Closing this issue as a duplicate for now, as it's being tracked in another topic. Expect a fix in the next patch.

You don' t need to uninstall it. And the Output/TBM900 directory is what contains the aircraft's persistent state. Leave that if you don't want to lose the maintenance history of the aircraft.

We have a fix for this coming in an update very soon. Please re-test when patch 1.0.2 is released.

Thank you, I will prepare a build with some improvements. That should help guide me further. I will notify you via PM with the ZIP when it's ready.

Unfortunately the crash backtrace generator is being confused somewhat. Could you please run X-Plane in a debugger and send us some debugging output commands? To get into the debugger use the following commands in a terminal: $ cd X-Plane/X-Plane_11 $ gdb ./X-Plane-x86_64 (gdb) r [start up the avionics and make the sim crash] (gdb) bt Please copy the output of the "bt" command and paste it into a forum post here. With this information I'll be able to pinpoint the code that is causing this. I appreciate the help!

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?