Goran_M

AFAIK, this is correct, but we can check with our pilot consultants. For now, you can use the mouse to drag the gear up and down. An update will be released very soon with a command so you can bind a key or button to it. What @manofmacsaid. The numbers appear in the top left of the screen when you adjust the CRS and HDG. When you stop adjusting, they go away.

Are you using reshade?

We're looking into why this is working for the left engine but not the right engine. For now, we ask that you push the condition lever into the detent by using the mouse manipulator (just left click and push it in). This will start the engine.

Glad to see you got it sorted out.

Wait. Is X-Plane running while you’re downloading? If it is, Gizmo cannot install. You need to shut down X-Plane.

We're looking into this. It's ok. We're still going through some teething problems, and an update will be issued very quickly. They are very small updates, and we won't make people wait any longer than they need to. Make sure Windows Defender also is not running. Cameron comes here regularly, and hopefully he will have a solution for you.

I don't know how you wouldn't notice these issues before. It was a major part of the update and the engines were severely affected by the new XP11 engine model before this update. The landing gear is new, and the next update will address the command for assigning a key press or button press to toggle it up or down. But for now, we ask that you use the mouse to click on the gear handle and drag it up or down. Perhaps your AoA is too low on landing. We've checked the new flight model against the charts, and the Saab pilots who helped us have checked this. We're comfortable with the way the flight model handles now.

So you're saying the previous version was BETTER than 1.6? With the wildly swinging engine temperatures and torque? I'm going to keep it courteous and respectful. I would rather you ask for help, instead of making snarky remarks. But you do whatever you want to do, while I address your issues with this free update. HDG Slave is NOT HDG Sync This now works correctly. We're looking into this. In the meantime, you can grab the gear handle with the mouse and drag it up. Did you re-assign your key/button presses? This does nothing for me to be able to help you. Tested and working. The friction of the plane now matches the charts much more closely.

Please read the last line of this post.

Have you tried physically pushing the CL into the START detent with the mouse? If it starts when you do this, we can take a closer look into why the other engine starts, but this one doesn't.

As far as the code is concerned, if the hardware lines up with the detent, which is indicated in the 2D pop up by the text "START", you should have no problem doing an engine start. The actual detent, which can be used with the mouse, is a separate dataref, and cannot be bound to hardware. However, I refer to my original statement. As long as the hardware lines up with the START position, the engines should start. See images below... CL levers, indicated by the yellow lines are at START, which is indicated in blue (at the top of the CL range)... This will give you an engine start. This image shows the CL's at FEATHER. If the engines are not running, and you want to start, they will not start if the CL's are in this position...

The pop up is the default Laminar pop up. Any lighting done to that is controlled by them. In your image, it is obviously taken at night, so it will reflect night time textures on the pop up, regardless of cockpit lighting.

This. I was watching someone demonstrate this to me last night, and you MUST make sure the condition levers are pressed into the detents, otherwise the engine won't start.

A component error is due to running an older installer. Are you sure you are running the new installer? The zip file should be named TBM_900_v1.1.13.zip

Cannot reproduce. Can you post a Gizmolog.txt and log.txt file?

Yes, it will work in Vulkan.

yes

We'll look into this over the next few hours. Can confirm. Noted and this will be looked at. EDIT: Just did another test. With the Saab running, the tiller doesn't move, but the nose wheel does steer with hardware, once the aircraft park brakes are off. We'll look at the tiller issue.

We have individual AND a common manipulator for the CL's. So yes, you can map your hardware individually or using 1 axis. What happens if you use the mouse on the tiller? Do you have hydraulics pressurized?

You can map both condition levers to 1 axis using a common manipulator that is now implemented. Make sure the steering tiller is unlocked and mapped correctly. The naming of all the commands has been changed for this update. We understand this may be an inconvenience to those with hardware assignments, and we apologize for this.

Cameron has mystical powers.

This right here is likely the cause of your FPS issues. The TBM uses some hi resolution textures, and is very likely overloading your GPU. My suggestion is, while flying online, to reduce the texture quality. I know it's not ideal, but you're trying to squeeze something out of your GPU that simply isn't there. Another possible cause is what Ben posted below.

Unable to reproduce on my end. If you remove the ground handling plugin, does the sound go away?

Next step is to isolate the plug in causing you problems. Add plugins back, one at a time, and loading the TBM each time, to see which one is causing the crash. Then we can determine is if it's something for us to address, or something for the developer of the plugin to address.

Set a button or keystroke to "Toggle thrust reverse". That will bring it back to Taxi/Ground Idle