Problem using (understanding?) SubShift function
Posted: Wed Jan 04, 2023 3:48
I recently purchased:
Gladiator NXT EVO SCG Premium OTA (Left)
Gladiator NXT EVO SCG Premium (Right)
Both sticks came with firmware 2.122
I am using VKBDevCfg(v0.92.51)
My plan was to assign the center button of each HAT switch a different SubSwitch function number.
That way the other keys of that same HAT could have multiple functions without affecting any other buttons.
The other HATs could use their own SubShift or not as needed.
This would leave the global SHIFT keys (#1 & #2) for truly "Global" changes.
I am able to assign the SubShift without any problems.
A programmed LED indicates the state change takes place as expected.
The problem comes when I try to use the "ButtonS" type for the other buttons (Up, Down, Left, Right).
Using HAT A3 (the middle one) as an example:
Center button Physical layer #14 gets the SubShift #1 function, set as Alternate so it latches.
The "Down" button Physical layer #21 gets set as "ButtonS".
By default the V.Button Drop Down Menu has "22" assigned (one more than the original button)
#22 is another one of the HAT's buttons however (A3-Up), so I changed it to #41 (a free location).
As soon as I make this change, the cell identifier changes to "BM #1" instead of staying "BS 1"
If you leave and then re-enter the Button Mapping Wizard for cell #21 it is now described as "Modal Switch controlled Button".
If you use the "Set" action to write this configuration to the stick, and then use the "Test" page to watch what happens:
Light #8 (A3-Down) turns on for a normal press (as expected).
When the SubShift is activated (press and release A3-Center) Light #8 still lights instead of #45 when the "Down" button is pressed.
The manual I have (controller2_17En.pdf) has no mention of "Modal Switch controlled Button" or the BM #n identifier.
It does show a "Type" Drop Down Menu in the "ButtonS" page of the Button Mapping Wizard.
According to the manual this allows "Single" or "Multi", so you can have one (or more) SubShifts controlling the button.
My system using VKBDevCfg(v0.92.51) the current version available, does not present ButtonS options like the manual does.
I have this same problem on both sticks (left and right).
I also tried doing this with VKBDevCfg(v0.92.57) and firmware v2.12B with the same results.
Is there a more current manual that describes v0.92.51 or later versions of the VKBDevCfg program?
Is my thinking of how SubShifts "should" work at fault?
Is it possible to re-map the "shifted" destination?
Thanks for any help you can provide for this matter.
I haven't found anything on the web to suggest anyone else is having this problem.
Gladiator NXT EVO SCG Premium OTA (Left)
Gladiator NXT EVO SCG Premium (Right)
Both sticks came with firmware 2.122
I am using VKBDevCfg(v0.92.51)
My plan was to assign the center button of each HAT switch a different SubSwitch function number.
That way the other keys of that same HAT could have multiple functions without affecting any other buttons.
The other HATs could use their own SubShift or not as needed.
This would leave the global SHIFT keys (#1 & #2) for truly "Global" changes.
I am able to assign the SubShift without any problems.
A programmed LED indicates the state change takes place as expected.
The problem comes when I try to use the "ButtonS" type for the other buttons (Up, Down, Left, Right).
Using HAT A3 (the middle one) as an example:
Center button Physical layer #14 gets the SubShift #1 function, set as Alternate so it latches.
The "Down" button Physical layer #21 gets set as "ButtonS".
By default the V.Button Drop Down Menu has "22" assigned (one more than the original button)
#22 is another one of the HAT's buttons however (A3-Up), so I changed it to #41 (a free location).
As soon as I make this change, the cell identifier changes to "BM #1" instead of staying "BS 1"
If you leave and then re-enter the Button Mapping Wizard for cell #21 it is now described as "Modal Switch controlled Button".
If you use the "Set" action to write this configuration to the stick, and then use the "Test" page to watch what happens:
Light #8 (A3-Down) turns on for a normal press (as expected).
When the SubShift is activated (press and release A3-Center) Light #8 still lights instead of #45 when the "Down" button is pressed.
The manual I have (controller2_17En.pdf) has no mention of "Modal Switch controlled Button" or the BM #n identifier.
It does show a "Type" Drop Down Menu in the "ButtonS" page of the Button Mapping Wizard.
According to the manual this allows "Single" or "Multi", so you can have one (or more) SubShifts controlling the button.
My system using VKBDevCfg(v0.92.51) the current version available, does not present ButtonS options like the manual does.
I have this same problem on both sticks (left and right).
I also tried doing this with VKBDevCfg(v0.92.57) and firmware v2.12B with the same results.
Is there a more current manual that describes v0.92.51 or later versions of the VKBDevCfg program?
Is my thinking of how SubShifts "should" work at fault?
Is it possible to re-map the "shifted" destination?
Thanks for any help you can provide for this matter.
I haven't found anything on the web to suggest anyone else is having this problem.