Jump to content

Joystick Support Needs An Update


No replies to this topic

#1 VxSaAgE

    Member

  • PipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 133 posts

Posted 05 January 2016 - 03:45 PM

I did some limited testing and discovered that joysticks basically send 5 different inputs (besides throttle) for any Axis, such that the Joystick has barely any control at all. Here's a bad, but relatively accurate example for a joystick X axis using two arbitrary integer A and B:

Full Left = -A
Half Left = -B
Center = 0
Half Right = B
Full Right = A

So while mouse controls what I assume is how many A's and B's to input, joysticks apply a multiplier to whatever A and B are and just do that many per second.

To see what I mean, set your joystick sensitivity to 0.1 and see that it will NEVER move at full speed. That is not how joysticks work, and it's very sloppy implementation of something that is now supported in hundreds of first person shooter titles.

Please add real joystick support. Give me a curve, let 1=1 or 1=5, don't give me the worst option of binary (or trinary?) input on something that literally doesn't translate that way.

With further research, I am to set this up by using third party scripting tools. This is not ideal.

Edited by VxSaAgE, 05 January 2016 - 04:15 PM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users