Wooting One keyboard compatibility

[paname]

tested new update but now R2 and L2 are always at 50% in monitor.

[J2Kbr]

tested new update but now R2 and L2 are always at 50% in monitor.

Okay, so I assume the Titan Two -with the update released today- is now recognizing the joystick interface and reporting HID:KG on Device Monitor.

Despite the R2 and L2 at 50%, does the stick is working? and the keyboard have dedicated buttons for the triggers (R2/L2)?

Thank you.

[paname]

tested new update but now R2 and L2 are always at 50% in monitor.

Okay, so I assume the Titan Two -with the update released today- is now recognizing the joystick interface and reporting HID:KG on Device Monitor.

Despite the R2 and L2 at 50%, does the stick is working? and the keyboard have dedicated buttons for the triggers (R2/L2)?

Thank you.

Hi,

the joystick works as intended now and when mapped WASD is now analog too LX/LY.

only R2/L2 have a 50 offset position. the joystick button they are mapped to are :

R2 = Y rotation UP and Y rotation down (2 keyboard keys)
L2 = X rotation left and X rotation right (2 keyboard keys)

also here is a capture at resting position (ACCEL also affected)
maybe those button should be mapped to something else allowing -100,100 range

https://imgur.com/a/Rgg8ffb

it may be a non issue as i think we may just fix this via remapper()

Code: Select all

 
const uint8 FixWootingLayout[39] = {
    RMP_USB_B ,
    BUTTON_1,  BUTTON_2,  BUTTON_3,  BUTTON_4,  RMP_NULL,  BUTTON_6,  BUTTON_7, 
    RMP_NULL,  BUTTON_9,  BUTTON_10, BUTTON_11, BUTTON_12, BUTTON_13, BUTTON_14, 
    BUTTON_15, BUTTON_16, BUTTON_17, BUTTON_18, BUTTON_19, BUTTON_20, BUTTON_21, 
    STICK_1_X, STICK_1_Y, STICK_2_X, STICK_2_Y, 
    POINT_1_X, POINT_1_Y, POINT_2_X, POINT_2_Y, 
    ACCEL_1_X, ACCEL_1_Y, ACCEL_1_Z, RMP_NULL, RMP_NULL, RMP_NULL, 
    GYRO_1_X,  GYRO_1_Y,  GYRO_1_Z
};
 

using following remap so it doesnt mess with R2/L2 state in script.

thanks

[Tech_geek]

XY joystick WASD movement and I can confirm it's working and registering 100%.

(R2/L2) they are stuck at 50%.

-The keyboard does not have dedicated buttons for the triggers (R2/L2).

to test this I had to disable (R2/L2) to get the full true list of the dedicated buttons,
just to make sure I tested it without input translator there was not changes to the value of 50% .

in the picture below you will see all the dedicated buttons in Keyboard:

[J2Kbr]

Hi guys, the Gtuner IV released yesterday have a new HID configuration file for the Wooting One keyboard, please try to check if the buttons mapping issues are solved (specially with L2/R2).

Remember to reconfigure the sd card to copy the new HID configuration file. (Device Configurations -> Configure)

thanks,

[Tech_geek]

Hi J2Kbr,

I just tested it works for the left analog sticks only, the right analog sticks does not work,

what I don't understand is why we have to limit the keyboard dedicated buttons,
for example driving game.. now I cant use the other analog dedicated buttons to control throttle or turn..

the previous update where the L2/R2 were always stuck at 50% all the other buttons worked just fine..

Many thanks.

[J2Kbr]

For the Left Analog use DirectInput X Axis and Y Axis.

For the Right Analog use DirectInput Z Axis and Z Rotation.

As for the buttons, I will be including in the next update. Just wanted a confirmation for the sticks before be okay proceed.