VKB-SIM

MSFS24 is a game that's struggling with virtual controllers (necessary if you are combining more than 8 axes together), so that's one case where having your GNX module on a dedicated USB controller would be beneficial. Some games don't have great controller support (BF6 is another game where having ...

The EVO upgrade kit does not change the electronics so you would still use the Gladiator_NXT firmware. If the GNX module is plugged into the NXT controller (with the JST cable) then it is not its own device but becomes part of the NXT controller config. If the GNX module independently plugs into the...

Fixed in 0.93.90, thanks Alex.

Bumping this too as it is still present in 0.93.89 :]

Bumping this as it's still current with software version 0.93.89. I realize I was less than thorough with the step by step in the original post: ⋅ In Profile > Axis open the Curve Wizard for any curve ⋅ Enable Proportional ⋅ Drag the last control point (100% deflection)...

Try and keep the multiplier to a power of two. 1024 should work perfectly rather than 999.

Click the inverted chevron button and enable 'New Opt'. This will allow you to input an axis id higher than 8 (then also do as Fallout9 says).

As for making the axis loop around, there is no built-in option for that (it would be a nice feature). It's possible to scrounge something like it together with some heavy boolean use, but it's kind of janky and I have instead found that simply playing with the additional encoder options is usually ...

Great, thx a lot! I managed to setup the two Axis which are linked to the Encoder and are toggled with a Modal Switch. That works so far. Encoder.png Profile_Axes.png However, Axis 8 won't go beyond 25087 (see screenshot). Axis 7 works fine. Might that be a bug? All settings are equal between Axis ...

Thanks Alex, 2.20.6(2) fixes it.

Firmware: 2.20.6 Software: 0.93.72 Issue: The Axis2Buttons boolean function for Logical or Virtual axis 9 freezes the device if the axis is moved towards the max value. The device must be restarted to recover. For this test I set up logical axis 9 to read from physical axis 1 on the SCE Gladiator: S...

You cannot assign and use the function for axes greater than 8. Boolean A2B allows referencing axes beyond 8: Screenshot 2025-10-15 093718.png This works fine if axis 11 is set to 8 bit. However if the axis is set to 9 bit, the A2B range is offset and maps to only one half of the axis: Screenshot 2...

Firmware: 2.17.6 - 2.19.E Software: 0.93.59 Issue: When multiple uSSW buttons are used to enable different POVs using the same axes, only the uSSW button for the highest POV# will disable the logical axes. POV1 and 2 read virtual axes 5 & 6: Screenshot 2025-09-03 233419.png When POV1 is enabled,...

Software: v0.93.46 The accepted range of manually-entered Bias values in the software is [-2047;2048]; Unfortunately this range is sometimes too small for some sensors. Fortunately bias values automatically set via ACn do not have this limitation, but sometimes manual calibration is necessary or mor...

This sounds like your deadzone is too small so the stick is never seen as centered, therefore the creeping value? Increase DzLo for the axis in question under profile > axes. Or is it that the value only increases no matter which side of the center you're moving? That's fixed in the latest experimen...