Wooting One keyboard compatibility
37 posts
• Page 2 of 4 • 1, 2, 3, 4
Re: Wooting One keyboard compatibility
wootingkb wrote:Wooting guy here. Made an account to clarify something that might help.
In the Wootility you can select to use either Xinput or DirectInput in each analog profile. It's in the left top dropdown in the controller button mapping card.
If I'm right, DirectInput will still work when you disable Xinput in the General settings (small cog left down of Wootility).
I don't actively keep an eye here, but if you have any other questions, always welcome to reach out to us by email social@ or our discord.
Thanks.
Hi Wootingkb,
I have Tried that already... It didn't work and it disabled the analog input compleatly.
Im not sure if you're familiar with Gtuner IV but when trying to remap buttons and create input translator for and key binding you have limited keys to work with as (analog) with digital actuation points while analog still functional it does not work ,
That been said the XIM apex is fully functional with all options as if its plugged to a PC its recognizing the actuation points,
but with xim you have no macro or script supported.
Thanks.
-
Tech_geek - Sergeant First Class
- Posts: 23
- Joined: Sun Feb 25, 2018 12:37 pm
Re: Wooting One keyboard compatibility
J2Kbr wrote:Xbox 360? this explains why this keyboard is not working with the Titan Two, added to GitHub for fix:
https://github.com/J2Kbr/TitanTwo/issues/175
when plugin this keyboard to T2, i cant use spacebar and none of those char keys :
{}_+=-
-
paname - Sergeant Major of the Army
- Posts: 204
- Joined: Wed Jan 07, 2015 3:02 pm
Re: Wooting One keyboard compatibility
paname wrote:when plugin this keyboard to T2, i cant use spacebar and none of those char keys :
{}_+=-
that's the issue where addressing here, you can remap few buttons only with analog input at the moment, till this issue is fixed hopefully with the next update.
-
Tech_geek - Sergeant First Class
- Posts: 23
- Joined: Sun Feb 25, 2018 12:37 pm
Re: Wooting One keyboard compatibility
that is not the issue i am describing at all.
the keyboard when plugged to titan2 even with last update 98.1.72 doesnt output some keys, like :
- spacebar
- - = { }
here is my descriptor fetch
the keyboard when plugged to titan2 even with last update 98.1.72 doesnt output some keys, like :
- spacebar
- - = { }
here is my descriptor fetch
- Code: Select all
[USB DESCRIPTOR]
12 01 00 02 00 00 00 40 EB 03 01 FF 11 01 01 02 00 01 09 02 CE 00 07 01 00 A0 C8 09 04 00 00 02 FF 5D 01 00 11 21 00 01 01 25 81 14 00 00 00 00 13 02 08 00 00 07 05 81 03 20 00 04 07 05 02 03 20 00 08 09 04 01 00 01 03 01 01 00 09 21 11 01 00 01 22 3B 00 07 05 83 03 08 00 0A 09 04 02 00 02 03 00 00 00 09 21 11 01 00 01 22 35 00 07 05 85 03 40 00 04 07 05 04 03 40 00 04 09 04 03 00 01 03 00 01 00 09 21 11 01 00 01 22 7B 00 07 05 86 03 40 00 01 09 04 04 00 01 03 00 01 00 09 21 11 01 00 01 22 19 00 07 05 87 03 08 00 10 09 04 05 00 01 03 00 00 00 09 21 11 01 00 01 22 51 00 07 05 88 03 20 00 08 09 04 06 00 01 03 00 00 00 09 21 11 01 00 01 22 17 00 07 05 89 03 40 00 04
[STRING 1 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 01 04 09 00 10
10 03 57 00 6F 00 6F 00 74 00 69 00 6E 00 67 00
[STRING 2 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 02 04 09 00 16
16 03 57 00 6F 00 6F 00 74 00 69 00 6E 00 67 00 4F 00 6E 00 65 00
[INTERFACE 1 HID DESCRIPTOR]
00 00 00 02 00 00 02 01 81 06 22 00 00 01 00 3B
05 01 09 06 A1 01 05 07 19 E0 29 E7 15 00 25 01 75 01 95 00 81 02 81 01 19 00 29 65 15 00 25 65 75 08 95 00 81 00 05 08 19 01 29 05 15 00 25 01 75 01 95 05 91 02 95 03 91 01 C0
[INTERFACE 2 HID DESCRIPTOR]
00 00 00 02 00 00 02 01 81 06 22 00 00 02 00 35
06 37 13 09 01 A1 01 09 02 09 03 15 00 26 FF 00 75 08 95 80 81 02 09 04 09 05 15 00 26 FF 00 75 08 95 80 91 02 09 06 09 07 15 00 26 FF 00 75 08 95 07 B1 02 C0
[INTERFACE 3 HID DESCRIPTOR]
00 00 00 02 00 00 02 01 81 06 22 00 00 03 00 7B
05 01 09 06 A1 01 75 01 95 05 05 08 19 01 29 05 91 02 75 03 95 01 91 03 75 01 95 08 15 00 25 01 05 07 19 E0 29 E7 81 02 75 01 95 2E 15 00 25 01 05 07 19 04 29 31 81 02 75 02 95 01 81 03 75 01 95 69 15 00 25 01 05 07 19 33 29 9B 81 02 75 07 95 01 81 03 75 01 95 08 15 00 25 01 05 07 19 9D 29 A4 81 02 75 01 95 2E 15 00 25 01 05 07 19 B0 29 DD 81 02 75 02 95 01 81 03 C0
[INTERFACE 4 HID DESCRIPTOR]
00 00 00 02 00 00 02 01 81 06 22 00 00 04 00 19
05 0C 09 01 A1 01 75 08 95 01 15 01 26 EA 00 05 0C 19 01 2A EA 00 81 00 C0
[INTERFACE 5 HID DESCRIPTOR]
00 00 00 02 00 00 02 01 81 06 22 00 00 05 00 51
05 01 09 05 A1 01 A1 00 05 09 19 01 29 0C 15 00 25 01 95 0C 75 01 81 02 75 04 95 01 81 03 05 01 09 30 09 31 09 32 09 33 09 34 09 35 16 00 80 26 FF 7F 75 10 95 06 81 02 05 02 09 BB 09 B8 09 C4 09 BA 09 C0 15 00 26 FF 00 75 08 95 05 81 02 C0 C0
[INTERFACE 6 HID DESCRIPTOR]
00 00 00 02 00 00 02 01 81 06 22 00 00 06 00 17
06 FF FF 09 01 A1 01 09 02 09 03 15 00 26 FF 00 75 08 95 20 81 02 C0
-
paname - Sergeant Major of the Army
- Posts: 204
- Joined: Wed Jan 07, 2015 3:02 pm
Re: Wooting One keyboard compatibility
Hi,
any idea ?
any idea ?
J2Kbr wrote:..
-
paname - Sergeant Major of the Army
- Posts: 204
- Joined: Wed Jan 07, 2015 3:02 pm
Re: Wooting One keyboard compatibility
I will be checking this for the next firmware update. thanks
ConsoleTuner Support Team
-
J2Kbr - General of the Army
- Posts: 20323
- Joined: Tue Mar 18, 2014 1:39 pm
Re: Wooting One keyboard compatibility
After checking the descriptors it seems this keyboard just need a dedicated HID configuration in order to fully work.
In the attachment you will find a HID configuration file. Download and copy this file to the “configsd” folder in the Gtuner IV installation and then, with the Titan Two connected to the computer, go to the Device Configuration panel and click on the button labeled “Configure”. This will copy this file to the sd-card inserted on the Titan Two.
Now plug the Wooting keyboard to check. Please let me know the results, if everything is good I will include this config file into the official release.
Thank you.
In the attachment you will find a HID configuration file. Download and copy this file to the “configsd” folder in the Gtuner IV installation and then, with the Titan Two connected to the computer, go to the Device Configuration panel and click on the button labeled “Configure”. This will copy this file to the sd-card inserted on the Titan Two.
Now plug the Wooting keyboard to check. Please let me know the results, if everything is good I will include this config file into the official release.
Thank you.
ConsoleTuner Support Team
-
J2Kbr - General of the Army
- Posts: 20323
- Joined: Tue Mar 18, 2014 1:39 pm
Re: Wooting One keyboard compatibility
J2Kbr wrote:After checking the descriptors it seems this keyboard just need a dedicated HID configuration in order to fully work.
In the attachment you will find a HID configuration file. Download and copy this file to the “configsd” folder in the Gtuner IV installation and then, with the Titan Two connected to the computer, go to the Device Configuration panel and click on the button labeled “Configure”. This will copy this file to the sd-card inserted on the Titan Two.
Now plug the Wooting keyboard to check. Please let me know the results, if everything is good I will include this config file into the official release.
Thank you.
Hi, installed and configured the HID file to T2 sdcard but still the same keys doesnt output anything. :/
to be more precise the key that arent working are :
KEY_SPACEBAR 0x2C // Spacebar
KEY_HYPHEN 0x2D // - or _
KEY_OPENBRACKET 0x2F // [ or {
KEY_CLOSEBRACKET 0x30 // ] or }
KEY_BACKSLASH 0x31 // \ or |
they are in that exact order in the header file.
-
paname - Sergeant Major of the Army
- Posts: 204
- Joined: Wed Jan 07, 2015 3:02 pm
Re: Wooting One keyboard compatibility
Please try with this updated version:
To install, same procedure as previously described.
To install, same procedure as previously described.
ConsoleTuner Support Team
-
J2Kbr - General of the Army
- Posts: 20323
- Joined: Tue Mar 18, 2014 1:39 pm
Re: Wooting One keyboard compatibility
J2Kbr wrote:Please try with this updated version:
To install, same procedure as previously described.
same result, maybe it is an issue with the keyboard or its firmware.
if you need me to run aspecific gpc code i can.
-
paname - Sergeant Major of the Army
- Posts: 204
- Joined: Wed Jan 07, 2015 3:02 pm
37 posts
• Page 2 of 4 • 1, 2, 3, 4
Who is online
Users browsing this forum: No registered users and 107 guests