Regedits and other changes that made a difference? I found a few

[davidl41]

Whatever settings you change may have risks. I'd create a restore point as well.

In order from most impactful to least impactful. They all were impactful though.

• Regedit Tweak 1. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile Set Systemresponsiveness to 0. It was explained to me that it makes the system respond faster. The original value is 14 , and value 0 is more responsive. I noticed it was absolutely a difference.

• Control panel tweak. Keyboard setting found in control panel. Can be found in Microsoft search bar by searching for "keyboard". Set repeat delay and repeat rate all the way to the right. When you hold down a key it has no delay for the 2nd letter, which is great for gaming, but for typing it can create repeat letters because it's so instant.

• Regedit Tweak 2. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PriorityControl Win32PrioritySeparation set to 36. People strongly suggest not to go beyond 40 because it can have issues. I set it to 80 which is marginally more smooth, and it's been fine for a month or so. Go beyond 40 at your own risk. It was explained to me that the value is how much time the CPU spends on the foreground app, which is the game.

• Regedit Tweak 3. Computer\HKEY_CURRENT_USER\Control Panel\Keyboard InitialKeyboardIndicators:0 KeyboardDelay:0 KeyboardSpeed:31. It makes the keyboard react more instant. 31 is the highest value for keyboard speed.

There are other obvious things like removing pointer precision, and so on, but most know of those already. Raw accel's sensor rotation is good too, but it is not for latency.


Those are the ones I found to be effective. Use at your own risk, and create a restore point before hand. Consider sharing your top tweaks!

[yehaw]

Whatever settings you change may have risks. I'd create a restore point as well.

In order from most impactful to least impactful. They all were impactful though.

• Regedit Tweak 1. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile Set Systemresponsiveness to 0. It was explained to me that it makes the system respond faster. The original value is 14 which they claim is 14ms, and value 0 is instant. I noticed it was absolutely a difference.

Setting this to 0 clamps it to the default value of 20 with the possibility of introducing issues. The minimum that is safe is 10. I suggest you research your tweaks instead of blindly applying what you read on the internet in the future. You should also fact check the rest of what you've shared. I wouldn't recommend applying anything this user recommends, as it's clearly not researched and just "feels better" type of nonsense.

This key contains a REG_DWORD value named SystemResponsiveness that determines the percentage of CPU resources that should be guaranteed to low-priority tasks. For example, if this value is 20, then 20% of CPU resources are reserved for low-priority tasks. Note that values that are not evenly divisible by 10 are rounded down to the nearest multiple of 10. Values below 10 and above 100 are clamped to 20. A value of 100 disables MMCSS (driver returns STATUS_SERVER_DISABLED).

Source - https://learn.microsoft.com/en-us/windo ... er-service

[cumitmuito]

• Regedit Tweak 2. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PriorityControl Win32PrioritySeparation set to 36. People strongly suggest not to go beyond 40 because it can have issues. I set it to 80 which is marginally more smooth, and it's been fine for a month or so. Go beyond 40 at your own risk. It was explained to me that the value is how much time the CPU spends on the foreground app, which is the game.

you mean 36 in hex right?

[davidl41]

• Regedit Tweak 2. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PriorityControl Win32PrioritySeparation set to 36. People strongly suggest not to go beyond 40 because it can have issues. I set it to 80 which is marginally more smooth, and it's been fine for a month or so. Go beyond 40 at your own risk. It was explained to me that the value is how much time the CPU spends on the foreground app, which is the game.

you mean 36 in hex right?

36, 38 or 40 decimal is what some people say. Most say do not go over 40. I use far more than that at 80 decimal and there hasn't been an issue for over a month. Use at your own risk. It prioritizes the foreground applications much more. I think over 80 and there is an issue as it's deprioritizing the background apps too much. If you use the computer for something intensive other than gaming then setting it at less than 40 is better.

There is a few more that is possible to get go higher than most others put it as well. Again, do at your own risk. This is my own testing and I don't really see anyone doing it. GPU priority can be up to 31 decimal which I set it for. People are setting it to 8. In the games regedit(first link from below) the SFIO I wrote as High with the capital "H". SFIO is IO like the mouse and keyboard. The priority, and scheduling is also set High with the capital "H". Affinity is changed to different affinities for each, 2, 4, 6 so they use different GPU cores, real cores as well. Background only is set to False.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Games

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Audio

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\DisplayPostProcessing

That is what I used so far that has been useful. Use at your own risk. Set restore points.

[davidl41]

• Regedit Tweak 2. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PriorityControl Win32PrioritySeparation set to 36. People strongly suggest not to go beyond 40 because it can have issues. I set it to 80 which is marginally more smooth, and it's been fine for a month or so. Go beyond 40 at your own risk. It was explained to me that the value is how much time the CPU spends on the foreground app, which is the game.

you mean 36 in hex right?

36, 38 or 40 decimal is what some people say. Most say do not go over 40. I use far more than that at 80 decimal and there hasn't been an issue for over a month. Use at your own risk. It prioritizes the foreground applications much more. I think over 80 and there is an issue as it's deprioritizing the background apps too much. If you use the computer for something intensive other than gaming then setting it at less than 40 is better.

There is a few more that is possible to set higher than most others put it as well. Again, do at your own risk. This is my own testing and I don't really see anyone doing it. GPU priority can be up to 31 decimal which I set it for. People are setting it to 8. In the games regedit(first link from below) the SFIO I wrote as High with the capital "H". SFIO is IO like the mouse and keyboard. The priority, and scheduling is also set High with the capital "H". Affinity is changed to different affinities for each, 2, 4, 6 so they use different GPU cores, real cores as well. Background only is set to False.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Games

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Audio

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\DisplayPostProcessing

That is what I used so far that has been useful. Use at your own risk. Set restore points.

[Hyote]

• Regedit Tweak 2. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PriorityControl Win32PrioritySeparation set to 36. People strongly suggest not to go beyond 40 because it can have issues. I set it to 80 which is marginally more smooth, and it's been fine for a month or so. Go beyond 40 at your own risk. It was explained to me that the value is how much time the CPU spends on the foreground app, which is the game.

you mean 36 in hex right?

36, 38 or 40 decimal is what some people say. Most say do not go over 40. I use far more than that at 80 decimal and there hasn't been an issue for over a month. Use at your own risk. It prioritizes the foreground applications much more. I think over 80 and there is an issue as it's deprioritizing the background apps too much. If you use the computer for something intensive other than gaming then setting it at less than 40 is better.

There is a few more that is possible to set higher than most others put it as well. Again, do at your own risk. This is my own testing and I don't really see anyone doing it. GPU priority can be up to 31 decimal which I set it for. People are setting it to 8. In the games regedit(first link from below) the SFIO I wrote as High with the capital "H". SFIO is IO like the mouse and keyboard. The priority, and scheduling is also set High with the capital "H". Affinity is changed to different affinities for each, 2, 4, 6 so they use different GPU cores, real cores as well. Background only is set to False.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Games

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Audio

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\DisplayPostProcessing

That is what I used so far that has been useful. Use at your own risk. Set restore points.

Win32PS doesn't work like that. You can use FFFFFFFF. These modifications don't do anything useful. They either max out certain values or return them to their auto states.

[davidl41]

Win32PS doesn't work like that. You can use FFFFFFFF. These modifications don't do anything useful. They either max out certain values or return them to their auto states.

Win32priorityservice with the value FFFFFFFF? I never head of that value for that Win32priortyservice. What that does that do?

The tweaks seem fine and my mouse doesn't feel like it's dragging through mud anymore. I'll take what I can get.

Any you recommend that are effective? Most tweaks have no effect and I don't want to try a million of them since it seems like tweaking everything is kind of risky, since the odds of one setting having a knock on effect on another setting is kind of inevitable when there are a lot of regedits going on.

[soul4kills]

Use 41 Decimal/29 hex for Win32PrioritySeperation.

Also the values in decimal only range from 20-42. Does not go beyond that. They are mask values for 3 separate settings. Short/Long Quantum, Fixed/Variable Quantum Intervals, And High/Medium/None Process Priority Boosting.

41 Decimal/29 hex is Short Quantum/Fixed Interval/Medium Boost

Keep the game task profile default with Priority: 6, Scheduling Category: Medium, SFIO Priority: Normal.

Trust. Insane input latency and frame times. The medium boost makes it so it doesn't cause issues with other processes or drivers where High would cause your game process to hog resources and actually cause latency and jitter.

[Hyote]

Everything is wrong here in all the comments. Short answer: decimal 36 or 38. On 24H2+ you can get the shortest quantums on dec 36 due to a rule change.

[soul4kills]

https://github.com/LuSlower/win32ps-changer

This may offer some convenience when testing which one is best for your usage/setup. I personally don't use it because I created something for myself that works in a similar way.