#New keyboard dropping inputs
1 messages · Page 1 of 1 (latest)
Thanks for posting your support request!
Please note, the support center is only for community-based support with technical troubleshooting and general questions.
For official Wooting Customer Support, please use the Contact Us button on the Wooting Hub or email your request to social@wooting.io
note: use the email address associated with your order for fastest resolution
Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, change/confirm your shipping address, and much more.
Is your order about to ship and you need to pause it for any reason?
Place it On Hold via the Wooting Hub!
https://hub.wooting.io/login
just to check but have you attempted to
- restarted the computer
- tested another keyboard if it happens to that as well
did that
i also tried disabling tachyon mode, tried to change some stuff, disable raw input in my game, nothing changed
have you check if it is related to gamepad by doing the following
- in wootility
- settings
- keyboard settings
- gamepad mode
- Select "no gamepad"
what's gamepad
wooting keyboards can emulate a (xbox controller / gamepad) device
just to check if the computer is having issue/problems with it and trying to temporally disable it by steps above
just to check can you try the keyboard on another computer?
if it is isolated to the computer
i dont have another one atm
last thing i would check is lowering down brightness to see if it is power related
and to ask/clarify when you say it is freezing / dropping inputs
witch one of these situation happen ?
- i type " abc " then it takes computer a bit to type " abc "
2.i type " abc " output is "ac" with B being dropped
====
if it is (1.) it would be computer related as keyboard dose not store keypress output but sends raw data to computer of witch could be delayed by the OS or CPU so not keyboard related
2nd
but its lasting for a couple seconds, not just some strokes
its in a usb 3.1 port, but that shouldn't be a problem
i am not sure ill write up a summary and ping some one that knows more about this subject that may know what the cause could be
for reference could you answer a few questions
- what model keyboard do you have
-Wooting One
-Wooting Two
-Wooting Two he
-Wooting 60he - did this problem occur recently or when received your keyboard
- could you record a video to showcase the problem
- are you using the stock cable / or other cable
- dose this happen for everything or just in a certain application/game
- is the keyboard plugged directly into the motherboard or is there a USB hub or KVM between the computer
@solid rover after typing up that list i realized i did not check a few factors that could be the problem
sorry about that
60he, when received, I'm trying, stock cable, i dont know yet, motherboard
here
skip to 12 sec
@rocky trail
***summary ***
**Model:**60he
**Problem: ** keyboard is dropping/freezing for all keys inputs
Timeline: when received
set up: Directly Plugged into Computer
Attempted:
- restarted computer
- tried another keyboard (isolated to wooting)
- Disabling tachyon mode
- disable "gamepad" in wootility
Note
- stock Cable
- USB port 3.1
just to ask/check is this only happening in a game
or for every thing
this site is a good one to showcase if button is triggering that or notepad
https://config.qmk.fm/#/test
doesnt seem to happening on a different game
i guess osu is trash and cant handle the wooting
if this is isolated to just to a game then not much i can do about it beside maybe checking out
#1019723042244534282 for similar siltation's / solutions
im not sure yet though
because it happens randomly
ah no, it just happened in a different game
best to test if this happens outside of any game the URl
https://config.qmk.fm/#/test
is a good way to test to see if a key activate
QMK Configurator is an online tool used for easily creating firmware files for keyboards supported in qmk_firmware
@solid rover Please re-plug the device, if that helped the issue was that the device was still in the sleep mode. This can happen rarely on some USB setups after the PC was put to sleep.
Otherwise please check that you hit the right keys and not some others. For example I'm aware of a case where the user accidental hit the shift key and so the arrow keys on the num pad became page up and down. It may can happen when a key is hardly bottomed out that other keys are activated due to the shock, especially on very sensitive settings.
In general, as untamedx2 suggested please check it outside any game.
Also please check the CPU usage in the task manager while the kernel utilization is shown. Especially when you want to check it in a game. If that is high the OS maybe can't handle the inputs in time.
Otherwise I need more intel about how the issue. Like if a key press is just delayed and will be registered a few seconds later it should be an issue with the OS.
If a key press is not registered at all the question if what happened when you still hold it and are pressing another key in addition? If the key is then registered the key event got dropped.
But it can also be caused by unideal settings, like if the downstroke detection is less sensitive than the upstroke detection. So please share the profile ID.
i did everything suggested, i hit the right keys, i dont have 2 screens to check while playing
here you can see that it just drops all keys for a couple seconds
You can use the windowed mode to check the CPU utilization while playing a game.
profile id: 640668280bcaa53c09b379a54b1b93402d4d
But again, as mentioned to rule out any game specific issues you should use a keyboard tester and test it outside any game. If the issue is caused by the Wooting the issues should occur there too.
The profile looks fine to me.
I still need the info if the inputs are dropped or just handled delayed. I'm not a OSU player so I don't get anything from the video.
I also need the answer of the other questions. I can only help if I exactly know what the issue is.
dropped
all inputs (buttons)
for a time span like a couple seconds
Please be more precise, what happened when you are still holding the keys?
nothing
And when you then are pressing a key in addition?
nothing
So only the new key is then registered?
only after that couple seconds it would suddenly register again a new press
But not the still hold ones.
I'm interested in the exact behavior when it's working again.
Also please use the touch RGB effect. That way the detected analog value if shown on the keyboards number row. So the question is if these are still lit when the input isn't detected.
If the number row is still lit it would indicate an OS problem, if that not it means the keyboard didn't registered the input anymore.
Hmm, it looks somehow high to me. Nearly the entire CPU utilization is dedicated to the kernel. It's also around 15%. So I guess it's a multi core CPU and so it can be that only one core is doing kernel stuff with a high load. For reference, on my system the idle load is around 3 to 5%.
that spike is after i quit the game, it was something else
I'm not familiar with the game but normally if a game is running the majority of the CPU utilization is done by the app while only a small percentage is done in the kernel. But on the picture only around 3% is for the app while 15% is for the kernel. So it seems huge to me.
Meaning it should be the other way around, 3% for the kernel while 15% for the app. So I assume the game likely don't uses multiple threads and may only use just one. On an eight thread system this would mean that one core is basically only doing kernel stuff.
@solid rover was für nh CPU hast du
i9-9900k
also die ist denke ich mal nicht das problem (ist nh gute CPU)
The CPU isn't the cause and no-one wrote that this would be the case.
As mentioned, I'm not familiar with OSU but it looks not normal to me that this game causes such a high kernel utilization.
As I pointed out multiple times, if I don't know how the issue appears in detail I can't help.