(Update 2) Firmware releases after v.1.99.6 have incorrect defaults for throttle axis on Gladiator MK.II

[Thinking]

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.

[Thinking]

Update!:

To fix issues with Switch 0 on newer firmware, you have to go into the axis settings (Profile -> Axes) and uncheck/disable "Cn" on throttle axes (Logical Axes panel) and then make sure to check/enable "ACn" (in the Physical Axes panel) on the throttle axes. (Throttle axes = The actualy axis of the throttle + the virtual axes you want to use with it)

Fix tested with firmware version v.2.03.7(3) and VKBDevCfg 0.91.81

---Original Post (Not Applicable)---

Update: I found when the bug started. Versions after v1.99.6 are faulty

If you need the function use this firmware/software from http://alex-oz.strana.de/ (the firmware developer) the older firmware/software is found in the "Archive" folder.

Firmware: 1.99.6 (3)

Software: v0.91.30

Also, Fix Axis is probably not broken, I simply forgot to enable it in the Global tab. I could go back to the newest firmware and test this now that I know but I don't want to flash the firmware too many times, especially since I did it a lot of times now to find the last working version.

Edit: I am using a Gladiator MK.II with the default KG 12 grip