Throttle not maxing out

Issue #15 resolved
Det_Bullock created an issue

For some reason the throttle slider seems not to max out with a CH Pro Throttle, at first I thought it was a calibration issue but even after recalibrating with a bit of a margin often the y-wing with all equalized is stuck at 79 instead of 80 or sometimes at 75/76. I have tried putting a wider deadzone in the game options but there doesn't seem to be much difference, going back and forth on the slider whether I get to the real maximum throttle seems to be completely random and indipendent from the force or spped with which I move the throttle.

I also have tried the throttle multiple times with other games I have currently installed including FreespaceOpen and there don't seem to be any issues with them.

Comments (13)

  1. Dez E

    I've experienced similar issues with the throttle slider - what I've observed is that it seems to be fast movements that cause the game not to register the full movement somehow.

    E.g. from max throttle, suddenly moving the throttle to zero results in the speed remaining somewhere in the middle of the range, rather than zero. If I then move the throttle slider very slowly from zero, the game will then register the throttle as zero (or nearly zero).

    The deadzone setting doesn't seem to make much difference (on my particular joystick, I've not actually observed a throttle slider deadzone in any games or calibrations so far).

    (Thrustmaster T1600M)

  2. Det_Bullock reporter

    Tested with the new build, I've been trying to fiddle with the calibration settings to see if I could solve it somehow but nothing I did worked. It is possible (NOTE: this is a wild guess) that for some reason Unity tends to read the raw values of the potentiometer instead of the values adjusted by the throttle driver or something similar.

  3. Dez E

    Just to confirm that in the current build (170815), I'm still encountering the issue where I cannot go to maximum throttle via the joystick slider, regardless of the zero setting that I choose in the options. I've attached a screenshot showing the zero configuration, where the joystick slider is set to the maximum (and this is reflected visually in the utility), but in-game, the throttle does not go beyond 95% (for a Y-Wing on normal settings, I cannot increase the speed beyond 76 via the slider, but can go to 80 via the keyboard).

    joystickzero.png

  4. jerstryker

    I have the same issue, though I tried a different method to attempt a workaround (which did not work but might help in troubleshooting). I'm using a Logitech G940 rewired into a BU0836A board. Instead of moving the zero point, I tried to solve it by increasing sensitivity. By increasing the sensitivity, the white indicator on the calibration screen will reach its max point before the controller goes all the way to the stop, and the in-game response to the axis should be the same. After turning the sensitivity all the way up I have a good 15% of extra movement in my throttle beyond which the game registers full input. This is evident on the calibration screen and also in game. However, the actual ship's throttle doesn't always go all the way to 100%. In the Y-Wing on normal ELS settings, with full throttle input, the speed will settle on either 78, 79, or 80. I also think I've seen the little blue throttle indicator lights not fill completely (like the last one is slightly dim, but not always). Like the OP states it doesn't seem to matter if you started from zero or 90% or anywhere in between, nor how fast you move the throttle. Sometimes (often actually) the ship's throttle just doesn't quite get all the way to 100%.

    It's possible this isn't limited to just the throttle axis. It would be difficult to confirm or even notice if pitch/roll/yaw were only registering 99% of the input instead of 100%.

  5. Tad Hashimoto

    Confirming the same issue with my X52 Pro throttle. Craft throttle will max at 95-99% using the throttle axis, but will go all the way to 100% with keyboard inputs.

  6. carlochericoni

    Same issue here with a Thrustmaster USB Joystick. This configuration problem is the same I had with XWA.

  7. Log in to comment