Page MenuHomeFeedback Tracker

Heli joystick issues
New, WishlistPublic

Description

Since 1.48 (I hoped it was fixed in 1.50 but problems are still there)..

  1. Fixed in 132000 dev build! Heli doesn't stay at ground after landing - even if you have 0 collective - and switching to the map. This results in the heli lifts a bit above the ground and flies/slides into whatever is around if you don't jump back regulary and press the descend key.

I don't know if this somehow is related to curve settings on collective but I changed my personal curve between 1.46 and 1.48/1.50.

  1. The numbers you could show in the joystick customization screen by pressing show is gone...

Another old problem...

For some reason the keyboard keys makes the heli descend faster than when using the collective on the joystick so I often have to use the keys to try to get decrease altitude as fast as possible even if collective is at min.

It is possible to increase the descent rate by using a more aggressive curve but by doing so it becomes very hard to make smooth landings.

IMO the descent rate at min collective should be the same regardless of curve settings since 0 collective is 0 collective.

And of course the very old problem...

The heli drops like a stone if you try to chat while flying with joystick.

Details

Legacy ID
1760297589
Severity
None
Resolution
Open
Reproducibility
Always
Category
Controls
Steps To Reproduce

Fly with joystick (as stated above I use slightly tweaked curves on X/Y/Z axis) and for the last one just hover and open the chat window in MP.

Additional Information

This is with standard flight model and I use Thrustmaster Cougar HOTAS and SIMPED rudders.

Event Timeline

KeyCat edited Steps To Reproduce. (Show Details)Aug 27 2015, 12:41 PM
KeyCat edited Additional Information. (Show Details)
KeyCat set Category to Controls.
KeyCat set Reproducibility to Always.
KeyCat set Severity to None.
KeyCat set Resolution to Open.
KeyCat set Legacy ID to 1760297589.May 8 2016, 12:35 PM
KeyCat added a subscriber: KeyCat.

Looks like #1 was fixed in today's dev-build :)