Strange interaction between CPU settings and resolution
Posted: 31 May 2026, 19:45
Just factory reset, if you've read my previous posts on here I have spoken on my resolution tweaks and how it aided my desync and hitreg issues for some odd reason. Well now I've reached another revelation
I have just set my resolution from 2560x1600 to 1920x1080 and usually this would have done absolutely nothing for my desync/hitreg issues. enemies would still ferrari peek, etc. But for some strange reason, whenever I utilize the 'win32priorityseparation' values, they actually affect my latency in a perceptible way as opposed to trying to change these values when using my native res (2560x1600).
Not only that, I have kept my power plan on balanced and changed my processor power management to min 100% and max 100% and I have been having responsive, smooth gameplay in three games that I've tested.
The question I have is this. How come none of these settings do anything on their own? I can change cpu related settings and they'll have no affect but once I implement the resolution change then things start to happen, why?
I have just set my resolution from 2560x1600 to 1920x1080 and usually this would have done absolutely nothing for my desync/hitreg issues. enemies would still ferrari peek, etc. But for some strange reason, whenever I utilize the 'win32priorityseparation' values, they actually affect my latency in a perceptible way as opposed to trying to change these values when using my native res (2560x1600).
Not only that, I have kept my power plan on balanced and changed my processor power management to min 100% and max 100% and I have been having responsive, smooth gameplay in three games that I've tested.
The question I have is this. How come none of these settings do anything on their own? I can change cpu related settings and they'll have no affect but once I implement the resolution change then things start to happen, why?