VKB-SIM

Yup it's fixed, thanks Alex.

Thanks, 2.19.D(2) fixes it.

I was testing the new MCounter options 2.19.6C when I came across this old friend, so bumping this to say it's still current.

Firmware: 2.19.A, 2.19.C.
Software: 0.93.46

Issue: When a logical axis is set to Relative mode with Linear curve, moving the physical lever in either direction makes the axis go up. The value can never decrease.

Awesome, thank you!

I don't like the new Calibration prompt in devcfg very much. That thing right here, opened by clicking 'Start Calibr.' in the tools tab: Screenshot 2025-06-29 120804.png Issue #1: It captures input. You cannot switch to other tabs after this thing shows up. Forgot to switch to the test tab? Too bad,...

Also if you push hard against the edges during calibration, that is where the maximum/minimum logical value for the axis will be set. Any time you want to reach this logical limit you will have to press equally hard against the edges. This is unnecessary stress on the material and unnecessary applic...

I'm testing on 0.93.36 (running fw 2.19.6) and can use two circular deadzones again.

Confirming that the issue persists with 0.93.34

Fw: 2.19.9-2.19.6 Sw: 0.93.34 Issue: Relative axes only react to the default physical axis. Moving the physical axis identified by AxID has no effect if AxID is not the default value. Here I set logical axes 1 and 2 as relative, controlled by physical axis 2 on my Gladiator. Both should move by the ...

You can do that via axis trimmers (you can trim either actual axes, or completely virtual axes). VKB has tutorials on this topic:

https://www.youtube.com/watch?v=kfxYCqUgU7E
https://www.youtube.com/watch?v=GB-pf6dEICM

For testing I created this profile on the Gladiator (cleaner set up than my MCGU + T-Rudder tangle): Screenshot 2025-04-13 214750.png The behaviour expected and observed in 2.18.F: Logical 5 & 6 (X and Y) controlled by the joystick's main axes (roll and pitch, physical 1 and 2). Logical 3 (RotZ)...

I'm experiencing the same issue, my toe brakes set up using BrakeV3 no longer works on GF4 MCGU + Trudder V plugged into a single BB. The same profile works fine in 2.18.F, breaks on 2.19.7. Here's a video of the issue: https://www.youtube.com/watch?v=ab4bUjnVvKA Physical axis 7 is the T-rudder axis...

Adding that software version v0.93.10 is the last version of VKBDevCfg that displayed the Tempo Timer option when a Tempo button is used (these screenshot are all taken without user=developer of course): Screenshot 2025-04-10 084422.png Screenshot 2025-04-10 084457.png The issue appeared in v0.93.11...

Bumping this bug as the issue has come up again in the Discord. Tempo is a fairly basic and widely used function, the fact access to Tempo Time is hidden behind the user=developer option (or assigning a Fix Axes button) is a problem Plus adding user=developer to zconfig.ini displays all the options,...