Скачать с ютуб Why Lowering Your KB & Mouse DataQueueSize, Using Interrupt Affinity Tool Will Lower Input Latency в хорошем качестве

Why Lowering Your KB & Mouse DataQueueSize, Using Interrupt Affinity Tool Will Lower Input Latency

I have held off on posting this video for about a year now. I wanted to test this for myself to see if there are any side effects worth mentioning. To date I haven't found any. However that depends on what numeric setting you are using for your keyboard and mouse dataqueuesize. If you go too low you will experience issues with input from the mouse and keyboard. If any of your mouse clicks or keyboard keys presses don't register the 1st time but, you have to click on them twice...You have to increase the numeric values by at least 10. Furthermore, setting your usb to work off a specific cpu core will help elevate the strain windows put on core 0 more so than anything else. The by-product of that is lower latency using LatencyMon. There are videos showing you how to put your GPU, etc on different cores but I do not recommend doing that. Just use it for the USB port(s). Tools like Ryzen Master can help you determine the "best" core you can use for moving the USB to. Here is the link to the Interrupt Affinity Policy Tool: https://www.techpowerup.com/download/... Regedit: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Kbdclass\Parameters Dword: KeyboardDataQueueSize Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mouclass\Parameters Dword: MouseDataQueueSize May Have to Add Sub-Key Paramters (after mouclass) 1st then add the dword MouseDataQueueSize I've been using this tweak for over a year now. And lowering the numeric value does provide quicker results to mouse clicks. But there are some caveats: A. USB hubs on chipset won't work well if at all. B. When changing the mouse/kb/dataqueuesize you must use decimal. There are knuckleheads out there only changing hexadecimal. C. When changing the mouse/kb/dataqueuesize avoid numeric decimal values that create a partial numeric hexadecimal value. IE: As shown in the video. D. Make sure you have a motherboard that doesn't port all the usbs to the chipset. For whatever reason any numeric decimal value that creates a partial numeric hexadecimal value (IE: 1e, 2d, 5g, etc) always messes up the mouse clicks. And causes your key presses to not register correctly more so then selecting a decimal value that's "to low". For example going from 100 to Eighty 'something' that causes a partial numeric hexadecimal value will cause more problems with the mouse/kb more so then going to a decimal value of Fifty "something" that has a complete numeric hexadecimal value. This sort of information isn't discussed because I actually took the time to research this for the past year. People don't realize: A. You must use decimal and not hexadecimal B. Stay away from chipset usb hubs C. Don't use decimal values that create a number/letter hexadecimal value. Which is why I am confident in sharing this in the video.