When coming out of horizontal (fast) flight, switching to vectoring mode and reducing thrust to zero, the rotors/nozzles of the VTOL don't automatically go into hover position when using analogue thrust control from some joysticks (Logitech Attack 3 in this case). Instead it's possible to set the rotation of the rotors/nozzles to 5 different degrees by using the flaps up/down action.
One tap of the "Decrease thrust" key 'y' will solve all of this however, this causes the engines to move into hover position and the joystick's thrust control can be used again to finish the landing attempt while hovering. The problem really lies in the engine not recognizing the right moment to move the engines into hovering position when using analogue thrust control.
Description
Details
- Severity
- Minor
- Resolution
- Open
- Reproducibility
- Sometimes
- Operating System
- Windows 10 x64
- Operating System Version
- 10.0.10586 Build 10586
- Category
- Controls
Using either the Blackfish or the Xi'an, go into fast horizontal flight with vectoring disabled. Then enable vectoring and reduce thrust to zero using the joystick's analogue thrust control. The rotors/nozzles will not go into hovering position, as they would when using the keyboard key to decrease thrust ('y' in most control schemes).
This is the way it behaves on my system with the Logitech Attack 3 joystick, but I've heard of people who have no problems whatsoever with joysticks, that's why reproducibility is only set to "Sometimes", even though it behaves consistently for me.
My suspicion is that "Decrease thrust (Analogue)" on my joystick never truly reduces thrust to zero, as using the "Decrease thrust" keyboard key would. That would explain why one tap of the keyboard key solves the problem and causes the VTOL to go into the proper state.
Event Timeline
I've got same issue.
What actually "fix" this, is one keystroke of keyboard "throttle" (LShift). After pressing - engine changes instantly.
It's still unusable to fly with HOTAS, but there is tip for programmers.
Could you please check whether this got better in the Steam Development branch? Thank you
Just checked and it's still the exact same behavior. See the attached pictures for a detailed explanation.
A possible fix would be to make the engines always turn into full vertical hover position when autohover is activated.