VKB-SIM

Issue: the new UI for Axis Combine operations counts indices for virtual axes starting from zero. AxisNN = 1 uses Virtual axis 2. AxisNN = 8 uses Virtual axis 1.

Firmware: 2.18F(3), 2.18.9
Software: v0.93.18

Steps to reproduce:

• On default NXT Gladiator, enable Combi1 operation for Logical axis 8, using AxisNN = 1, + , 100%. Combine column reads +A1
• Roll the stick right:
  
  • Observe that Logical 8 does not move along with Logical 1.
• Pitch the stick out of center:
  
  • Observe that Logical 8 matches Logical 2's movement.
• Change AxisNN for Logical 8 to 8. Combine column now reads +A0.
• Roll the stick out of center:
  
  • Logical 8 now matches Logical 1.

Reproduction video:
https://streamable.com/tzsxkt (Sorry for the streamable link, YT is being difficult)

I want to emphasize that this is just a UI issue. When using an older version of the software to display the older Combine UI, the #Axis value shows the actual virtual axis index used in the Combine operation.
So this Combi1 on Logical 8 in 0.93.18:

Displays like this in 0.92.95 (no manual change to the profile):

In either case, when this profile is applied Logical 8 is the result of the addition of virtual axes 8 and 2.

This doesn't affect the functionality of Combine functions, it's merely a usability annoyance as the user has to subtract one from the virtual axis index to use in the combine operation to enter the proper AxisNN value. And since AxisNN = 0 is not permitted, using virtual 1 requires entering AxisNN = 8 to overflow back to 0.

Check VKBDevCfg-C_v0.93.19

Version 0.93.19 displays the correct axis index, both in the summary box and the Combine Options window. Thanks, that's one less headache
The yellow hover popup which appears when the cursor is held over the Combine box still displays the incorrect index though.

Here +A1 is the correct index, Axis #2 is wrong.

Thanks, fixed.

He even snuck in a fix on the weekend!

Thanks for all your work.