VKB-SIM

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:

When POV1 is enabled, logical 5 and 6 are still reacting to ministick movement:


The rest of the config:
Couple buttons set as uSSW for POV 1 and 2, POV mode on start is disabled:

Axis config is stock, no shenanigans with the axes there:

When POV2 is enabled, logical axes 5 and 6 are correctly disabled and centered:

This is obviously a conflict configuration by its very nature - without adopting additional rules, this will be the case.
In this case, POVs operate independently and POV2 knows nothing about POV1.

But I have a question - is this configuration practical?

Generally speaking, to foresee all sorts of conflicts and deal with them means to increase the size of the firmware without any real need. There is not as much free space left as we would like.

Use case was having three different modes on a ministick - pov, mouse and axes.

But for this case you don't need 2x uSSw.

Alex Oz wrote:

Delta wrote:Use case was having three different modes on a ministick - pov, mouse and axes.

But for this case you don't need 2x uSSw.
https://www-njoy32-vkb--sim-pro.translate.goog/home/medley/limitations?_x_tr_sl=ru&_x_tr_tl=en&_x_tr_hl=ru&_x_tr_pto=wapp

upd
fw 2.19.F / VKBDevCfg-C v0.93.61





Mice must be last