Goran_M

To toggle taxi speed, you'll need to assign a button or keypress to "Toggle thrust reverse." This will get you into the area you want to get into. Disregard the wording. It will get you into taxi mode AND thrust reverse (if you go down far enough with the mouse or your throttle hardware). Assuming you're not familiar with this, it can all be done in the section in sim that I have posted below for the "toggle reverse thrust". Absolutely no need to hand edit anything. All you need to is add a key assignment on the right, and it's done.

Yoke commands: tbm900/anim/yoke_show[0] (Left side) tbm900/anim/yoke_show[1] (Right side) Regarding the throttle gate, are you trying to go into reverse? If not, what are you trying to accomplish with it?

These are custom datarefs and commands. Default keypresses won't work. You have to manually set them

See how your visors are also hidden? Your visual effects are low enough to hide any glass objects. You need to turn up your Visual Effects to, I think, maximum.

As I mentioned, I need the Log.txt file from the X-Plane root folder. Not your installer log

Graphics. Just make sure your glass (visors) are visible. If not, you'll need to turn up your reflection settings to be at, at least "Low".

Thanks @Knedl. At least this explains why we couldn't really nail it down. But we always knew it was either some kind of controller assignment or LUA script that went unnoticed.

This is definitely not caused by the TBM, but in any case, I need the Log.txt from the X-Plane root folder immediately after the crash. I'm suspecting some kind of scenery issue or a memory leak from another plugin.

Try reinstalling. It looks like the aircraft might not be activated.

Can you post a screenshot of your settings?

Turn on AP Trims. Overhead panel. Centre right.

Did you guys check calibration. Did you remove all plugins and try again? We haven’t had many of these, so it’s very isolated.

It's very hard to gauge, but Saso made it a point to make sure it runs well on his machine. And he's running an i5, GTX970 Linux machine, and getting acceptable fps on mid settings. I'd say the bare minimum of memory you would need is 16GB with little to no plugins. If you have more than the average amount of plugins running, you would need 32.

It depends on your settings. With that hardware, and the add ons you listed, I'd imagine your settings would be turned right down. Can you post a screenshot of your settings so I can get a better idea of whether or not you can run the TBM?

Right away I can see you only have 16GB of RAM. Do you have any ortho scenery installed? Many times, a pause every 5-10 minutes is scenery tiles loading. Also, can you try removing XJet? It looks like that might be chewing up a ton of your RAM.

Nvidia drivers are outdated. Update to current version.

Can you add some kind of exclusion rule to it? I would suggest asking in the FlyWithLUA forums why the file has been quarantined, and maybe they can whitelist it somehow.

Good to see you got it all working. Re the DME, it's very likely a Laminar bug in this case. Our G1000 has had a lot of customisations done to it, but the guts of it, with regards to navigation, is still the stock G1000. I'll look into it, though.

Give it a try. Make sure it's a complete CLEAN reinstall of the drivers. There is acheckbox in the Nvidia GeForce control panel for this.

Your graphics drivers are still crashing. Do you have some kind extensive multi monitor setup running?

We don't handle activations in the forums. You'll have to submit a support ticket here

Turn off your yaw damper

Right before the crash happened, you're getting a number of scenery errors/warnings for BGBW. Have you flown into or out of here before? Could you re-check the install and make sure nothing is missing or corrupted?

Thank you for the comments. There are no plans for more advanced variants at this time. Possibly in the future.

I see you are getting help from "totoritko" in the HS discord. Please keep your questions in there. No need to double post.