registry edit question

[charred epoch]

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 [e-mail]
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

[elder latch]

If you were to make the “Keyboard Data Queue Size” option lower in registry edit will it make the keyboard faster? I heard it does but I don't want to break anything.

[lavish willow]

i wouldnt touch it. i think these days in the age of low latency 1khz+ polling keyboards the advantage it gives is pure placebo

just like some people disabling some network storage service and claiming it made their input lag lower. most are placebo changes

[frail topaz]

This doesn't make any sense to me... You can't reduce the package size for the keyboard input data or the keystroke would not work and it would make no sense to reduce it for the other interfaces.

If you are worrying about overhead just close the Wootility and you are fine.

I may got you wrong... In the case you want to reduce the amount of packages the OS stores in a query until an application picks them up you can in theory reduce CPU overhead. But it depends on the game. Possible that an optimized game already only handles the last received package and drops all other. Then you would not even have a benefit while it can potentially cause a lot of issues.

[lavish willow]

well back in the days of ps2 keyboards this was done so the keyboard buffer of the driver gets cleared faster. in the day of n-key rollover it usually leads to buffer overflows and thus missed inputs or other dirver malfunctions

but people still do it and placebo themselves into thinking it actually changed something

[frail topaz]

Of course it will lead to missed inputs, this is the only reason why reducing the query size can slightly cause a speed improvement. Because the query is faster full and so less data need to be handled.

[lavish willow]

in the age of 125hz and 6key rollover it was probably a solid idea

but nowadays it leads to more issues than not

[frail topaz]

I would say these days it's would even has a bigger impact. Games are working in two phases, the game logic computed by the CPU and then the rendering on the GPU. While the GPU renders the previous frame the CPU can already compute a new one. In the game loop the inputs are handled and the positions updated. So on 60 FPS up to 17 input messages can help back with a 1 kHz polling rate.

The more packages need to be handled the more stuff the CPU has to do. You can skip inputs for the keyboard but you can't for the mouse, because the inputs for the keyboard are absolut while for the mouse they are relative.

[lavish willow]

the default is 1.200 bytes

i dont think you gain much by reducing it further

[frail topaz]

Meaning if one input from the mouse is dropped the detected distance would be short by that amount.

For that reason it causes more CPU demand if you are using a high polled mouse, like 4 or 8 kHz.

If the query is smaller less packages can be stored in it and so less packages are there which the game need to handle which reduces the computation time for the CPU. And that helps if you are CPU limited.