(Update 2) Firmware releases after v.1.99.6 have incorrect defaults for throttle axis on Gladiator MK.II
Posted: Wed Feb 17, 2021 18:54
Edit: I found the issue and changed the title to match it, please see my updated findings and workaround in my reply below.
Update!: It seems that the axis behavior was changed and the defaults not updated accordingly. I have once again updated my reply with the information for the workaround.
---Original Post (Not Applicable)---
I use a setup where the trigger button switches the throttle axis into a braking axis and sets the respective disabled axis to 0.
I recently decided to update my firmware, I first used 2.02.5(2) but since it has the bug with axis jittering I went straight for the newer 2.03 firmwares.
Unfortunately it seems that there is some sort of bug with software controlled axis positions, when using the Switch 0 function (between throttle and a virtual axis), the respective disabled axis will be set to 32511 instead of the expected 0. It is noteworthy that if the function would set the axis to the middle position, it would have to set it to 32767, though the two numbers are close, something isn't right here.
By the way, the throttle axis is by default configured to have a center, I tried to disable this but it just resulted in only the upper half of the axis range actually changing the response value, calibrating also didn't change anything. I believe this was also the case in previous firmware, but I thought I'd just mention it.
As a workaround I tried using Fix Axis in the FA1 and FA3 modes, unfortunately for some reason it had no effect on physical nor virtual axes despite the LEDs blinking in accordance to the Fix Axes event.
I have had my Gladiator MK.II's throttle axis configured to toggle between throttle and braking for a long time and it is an important feature to me.
Update!: It seems that the axis behavior was changed and the defaults not updated accordingly. I have once again updated my reply with the information for the workaround.
---Original Post (Not Applicable)---
I use a setup where the trigger button switches the throttle axis into a braking axis and sets the respective disabled axis to 0.
I recently decided to update my firmware, I first used 2.02.5(2) but since it has the bug with axis jittering I went straight for the newer 2.03 firmwares.
Unfortunately it seems that there is some sort of bug with software controlled axis positions, when using the Switch 0 function (between throttle and a virtual axis), the respective disabled axis will be set to 32511 instead of the expected 0. It is noteworthy that if the function would set the axis to the middle position, it would have to set it to 32767, though the two numbers are close, something isn't right here.
By the way, the throttle axis is by default configured to have a center, I tried to disable this but it just resulted in only the upper half of the axis range actually changing the response value, calibrating also didn't change anything. I believe this was also the case in previous firmware, but I thought I'd just mention it.
As a workaround I tried using Fix Axis in the FA1 and FA3 modes, unfortunately for some reason it had no effect on physical nor virtual axes despite the LEDs blinking in accordance to the Fix Axes event.
I have had my Gladiator MK.II's throttle axis configured to toggle between throttle and braking for a long time and it is an important feature to me.