When using a throttle axis, moving the full range of the throttle axis only allows for a maximum input of 50% throttle
Turning off "Use throttle negative region" causes for no input to be detected.
I am using an X-56 Rhino HOTAS system.
#Throttle axis maxes out at 50%
shrewd jungle
west oasis
it sounds like your axis may be inverted, and outputting a range from 0 to -1? The calibration menu might give you some hints as to why this is the case
shrewd jungle
Yes, the X-56 outputs an inverted signal.
Though it never has been an issue before in any other game. Just pressing the invert-axis in controls would fix it
and when it has been an issue, it would still output 100%
shrewd jungle
have you adjusted these settings? They should be able to convert the output to 0...
I have just figured that out. thank you.
shrewd jungle
have you adjusted these settings? They should be able to convert the output to 0...
Redact the previous statement. Could you clarify which arrow (white/blue) is the physical input and which is the processed input?
Still only getting 50%
west oasis
white is the processed input
shrewd jungle
white is the processed input
Ok, I have tried multiple configurations, and while the throttle input operates in the correct direction, it will still only output 50% max throttle.
I am unsure if it is operator error, or a quirk of the throttle causing the calibration to be confused
west oasis
can you disable "Use negative throttle region" and invert the controller in the calibration screen?
if you're able to get outputs from 0 to 1, that should work
shrewd jungle
if you're able to get outputs from 0 to 1, that should work
I was able to configure it for inputs 0-1, and the throttle still maxed out 50%
Uploading a video now
uncompressed 
shrewd jungle
Till then, I will go back to using V-Joy and HID hide.
Can confirm throttle works when used through V-Joy
shrewd jungle
thanks, this doesn't look like correct behavior
It has mysteriously fixed itself by removing it as detectable in the HID device list and then restarting the game then re-assigning it. I can confirm it was not just because of a restart of the game since previous attempts at restarting the game had no effect.
west oasis
good to hear it's working for now. I want to investigate why a 0 to -1 axis wasn't able to be converted into 0 to 1 or -1 to 1 output, but will wait until after the hotfix to ensure I don't break anything
shrewd jungle
If you need additional information, let me know
shrewd jungle
The reset fix seems to be temporary.
burnt summit
Can confirm it does this on the TM warthog also with using only 50 percent of the axis no matter what I do
shrewd jungle
Can confirm it does this on the TM warthog also with using only 50 percent of th...
Further testing allowed me to conclude that as a fix you can remove the device from the device list and then re-assign it as a detected device to fix it. This is a temporary fix as you will have to do this every time you start up the game.
tired silo
Having the same trouble. Would love a perm fix for this. As I only really want to play the game on the X-56. Just spent 3 hours on my only day off this week trying to fix the thing.
radiant vault
when calibrating try having your throttle at the center of range in the beginning
worked instantly for me
tired silo
when calibrating try having your throttle at the center of range in the beginnin...
Do you have a X-56 ? My problem occurred about ahlf an hour to an hour of play time.
radiant vault
Do you have a X-56 ? My problem occurred about ahlf an hour to an hour of play t...
yessir
visual flicker
Yes, the X-56 outputs an inverted signal.
This is really common, back in the early days of the PC the joystick's upper range would change as it heated up in use, so it was common to set 0 as max so at least max throttle would stay consistent
burnt summit
Further testing allowed me to conclude that as a fix you can remove the device f...
tried this but still isnt working
shrewd jungle
tried this but still isnt working
Interesting. So the fix works for the X56 but not the Warthog.
Just to be clear, you have it calibrated correctly in the control settings to output 0 to 1? And it still outputs in-game to 50%?
After that, you go into the control bindings tool and remove the device from the detected devices list along the top, and then use the assign controller to reassign it? You shouldn't have to do any more than that.
