VKB-SIM

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,...

So in zconfig.ini I have these lines under [user]: Screenshot 2025-04-09 185540.png These are respectively the names for the STECS and MCGU configs I use for Nuclear Option. If I change the 'Profile ID' field to 60 in VKBDevCfg in the Global > Common page, the text field next to Profile ID as well a...

The profile ID is stored in the profile, so if you assign the correct profile ID to your profile, it will automatically be named according to the value found in zconfig. Of course you should take care to not have several profiles with the same profile ID to avoid confusion.

Firmware: v2.19.6 Software: v0.93.32 Issue: When the Trimmer Options window is opened with either Ph.Ax or L.Ax option already selected, the AxisNN field does not display. Selecting Ph.Ax or L.Ax again displays the field correctly. This is purely visual and does not affect the already selected AxisN...

Firmware: v2.19.6 Software: 0.93.29 Issue: When two MCounter booleans share the same R input (same layer and button number), sending a R input will only reset the counter permanently for the M Counter with the smallest boolean ID. The other M Counters will reset to zero only as long as the R input i...

In VKBDevCfg go to the Tools tab, click 'Make Reg File'. This will create a .reg file in the same folder as VKBDevCfg. Running this file (double click it, you may need admin privileges) will remove the calibration data saved in the Windows registry for that device.

A convenient improvement would be a variant of the GT+ generator which merely refreshes the timer when pulsed again (i.e. button pressed and released in succession), as opposed to adding up timers. I use GT+ generators a lot, but the queueing behaviour when pulsing it repeatedly is a problem as it c...

Flashing _STECS_v2_19_6.vkb to Standard STECS with MK1 MTG results in Device Signature Error. Both the Cosmo and Unified files flash just fine. Screenshot 2025-03-26 201638.png Screenshot 2025-03-26 201701.png Screenshot 2025-03-26 201705.png Screenshot 2025-03-26 202025.png Edit: This is using the ...