As you know (from previous bug reports) I'm working on complex mapping that implement shifted functions on the vjoy.
My config has a normal mode + 3 shifted modes allowing to map the mouse movement in 4 pairs of axes (i.e. aircraft control, view control, trim control, etc..) and the real joystick and mouse buttons too.
How this work
Normal mode: Axes 1
Shifted A (Right click): Axes 2
Shifted B (Shift click): Axes 3
Shifted C ( Right click + Shift Click): Axes 4
Unfortunately these config don't work well in the practice because Enable/Disable bind is a too slow operation, easily visible when increase the number (6+ become an important control timming issue) of these kind of operations in the config.
You could se the issue comparing the attached config files.
Only need to replace you mouse device.
Is possible to optimize the Enable/Disable Bind operation in the program code?
Hi Vritual!
As you know (from previous bug reports) I'm working on complex mapping that implement shifted functions on the vjoy.
My config has a normal mode + 3 shifted modes allowing to map the mouse movement in 4 pairs of axes (i.e. aircraft control, view control, trim control, etc..) and the real joystick and mouse buttons too.
How this work
Normal mode: Axes 1
Shifted A (Right click): Axes 2
Shifted B (Shift click): Axes 3
Shifted C ( Right click + Shift Click): Axes 4
Unfortunately these config don't work well in the practice because Enable/Disable bind is a too slow operation, easily visible when increase the number (6+ become an important control timming issue) of these kind of operations in the config.
You could se the issue comparing the attached config files.
Only need to replace you mouse device.
Is possible to optimize the Enable/Disable Bind operation in the program code?
The same config without enable/disable bind lines...
You will see how fast the SHIFT STATE BUTTONS (80, 96, 112, 128) changes without problem comparing the previous config.
Yes, already working on it.
Try the new version.
Sorry for delay... no time for play.
GREAT!!!
Issue solved.
Thank you!