Input delay, Hitreg, Desync - Where to fix them

[sadboytunaswag31]

Edit - If you want help describe your problem clearly with proper context and your pc specs. If you wanna argue or want to make others feel hopeless please stay away.

I know a lot of you are struggling with your games right now. I've been there, and let me tell you straight up: it's fixable.

The problem is that when you don't really understand what's going wrong, every "fix" you try feels like a drop in the ocean. So before anything else, let's actually understand the problem and name it properly. It can come down to your hardware, your software, or your internet. But let me be clear about one thing: your electricity is not the reason. If it was, it would've been proven with real tests and real numbers by now. From my own experience of 4 years of struggle, research and helping my friends, the eletricity really isn't a problem.

Let's start with the glossary terms you need to describe what you're actually feeling in-game.

Input Delay (floaty aim, heavy mouse)
This is when your actions show up late on screen. People usually describe it as floaty aim or a heavy mouse. If this is your problem, your focus should be entirely on hardware and software settings. Nothing else.

Hitreg issues
Forget "i shot him" for a second and think about sprays and hip fires. You know how a lot of high-rank players get insane hitreg even while spraying or hip firing? That's not random or lucky. If your bullets pass through a character, the game should register a hit. If it doesn't, your game client isn't in sync with the game server. Why does that happen? Hardware and network. So that's where you look.

Interpolation buffer (that "behind the server" feeling)
This one is controlled by the game client, and developers built it in for one main reason: network jitter. You are never shown the exact live state of the game. There's always some delay between you and the server, and the client adds a buffer on top of that so enemy movement stays smooth even when packets arrive unevenly.

Quick example: on a 60Hz server, packets are sent roughly every 16.6ms. If your connection has jitter, the client bumps the buffer up by a tick or so, giving it enough room to interpolate enemy movement instead of stuttering.

This is a completely different headache, and honestly I've suffered with this one for a while. Good internet, good hitreg, and yet I'd still get lasered by people who were clearly bad. Guys I couldn't even react to, or who seemed to have inhuman reactions to my peeks. That feeling is this.

Desync
This is a really wide term that can mean any of the things above or all things combined. That's exactly why you have to fix it layer by layer instead of chasing one magic setting.

---

Where to actually look for fixes

Input Delay - Always hardware and software settings. It has nothing to do with your internet or your electricity. Sure, EMI can technically play a role, but that would be an extreme case, not the small heavy feeling most of us get. Focus on optimizing your hardware and software.
Areas to look at: DPC latency, interrupt latency, RTC/timer resolution, CPU clock speed, bad drivers, core affinity, and BIOS settings.

Hitreg - Network and hardware settings. Frametimes can cause hitreg issues too. Your internet can cause it, and your Windows network settings can play a role as well. So how do you measure it? Tools like iperf3 and hping let you test your UDP connection. With iperf3 you can send small UDP packets that mimic real game traffic almost exactly, which tells you a lot about what your connection is really doing.
Areas to look at: network quality, frametime, 1% lows, and network adapter settings.

Interpolation buffer - This is where most people suffer, because barely anyone actually knows what it is, and there's almost nothing written about it from the player's side. The causes are wide: network, hardware, or OS settings.
Areas to look at: packet pacing, network adapter driver and settings, and CPU/GPU frametime.

If you really want to understand little deep, go read about the PC latency pipeline (Nvidia has documentation on it, and Gamers Nexus made a good video too), and also look into how network packet pacing affect interpolation. I cant post links here yet.

Here's the big takeaway when it comes to gaming: the lowest latency isn't what matters most, consistency is. Whether it's your network packets or your frame times, steady and consistent pacing beats raw speed every time.

I'll be putting together a full optimization guide soon, once I have the time to write everything down properly in a GitHub repo or a single doc. In the meantime, if you really think your problem comes down to factors you can't control, like electricity, reply below and I'll try to prove otherwise by helping you optimize it in my free time. ( preferably someone who has already posted here in the past that had issue for long time).

Being a pro takes skill, no one's denying that. But not a lot of people want to admit that good internet and good hardware play a huge role in separating the top players from everyone else.

Ive had this feeling off being behind the server people shooting too fast to react to and my hit reg feels off IN MULTIPLE Games : Apex legends, Valorant , R6 (I was t3 player in val, champ r6 , master in apex ) so i dont think its a skill issue personally and Ive changed my pc THREE times with all components and still have this problem , sometimes i do some random "tweaks" that remove the issue for lets say a day and it all comes crashing down again.

My pc specs :

Msi b850 Gaming pro
32 gb ddr5 ram g skill ripjaws M5 cl 36
ryzen 7 7800x3d
Msi 5060 gaming
m.2 Kingston SNV321000g

the only thing I think could be the problem is electricity i dont believe the my house has earthing (Not knowlegeble in the "engineering aspect") so can that be the issue Idk at this point

DId you check your udp jitter with iperf3 or any other tests? How does your frametime graph and 1% low look like?
You can dm me on discord - xvenom_03

Private messaged this guy. Got no answer after some time and he wont add my discord either.
Any updates?

[SweatHatesMe?]

Hi bro!
I’ve two Xbox one and a ryzen 5 5500u. My issue is that there’s some type of desync, tbh I don’t know what causes this bc it happens with every software/hardware I use to play and location. I’ve encountered some temporary fixes mainly changing how I do interact with the controller or the composition of my hand’s skin, still the lag returns periodically in minutes.
What happens in rocket league on 50/50s the physics seems to always favor the opponent, my car seems to have some type of disability bc it’s slower than others.
On overwatch enemies always seems to have some type of superpower cuz even if I hit them directly with Sigma when they r almost with no health they seem to survive or directly the game doesn’t register or registers “wrong”the shot. Anyway my question here is on what category does this fall?

[pcenthusiast92]

I’ve been around since 2009. I actually started playing Counter-Strike on Steam back in 2006. People online might know me as haze, cloudhaze, or x58haze on GitHub and other platforms.I vividly remember when this whole issue became a hot topic. It was all thanks to a legendary Steam forum thread that has since been deleted. It was titled "CS isn't smooth in 2009." It was so iconic that it sparked the entire community conversation around desync, input lag, hit registration issues (bullets doing zero damage), "Ferrari peeking," and that awful heavy mouse feeling. It made you feel like you were trapped in a 4:3 stretched jail—your heart racing just trying to aim, while other players looked completely relaxed, jumping around and enjoying a flawless, crisp connection. That thread was amazing; it had thousands of comments analyzing different PC builds, power conditioners, and tweaks.Yet, here we are today, still facing the exact same weird issues. We all know that rare feeling when the game suddenly behaves perfectly: footsteps are crystal clear, utility trajectories look incredibly smooth, your reaction time peaks, and enemies seem to move in slow motion, making them easy to aim at.I’ve been down the ultimate rabbit hole trying to fix this. I used to mod BIOS files, revive bricked motherboards using CH341A programmers, desolder chips, mess with USB latencies, disable Windows background services, and tweak OS kernels and timers like crazy. I’ve formatted Windows thousands of times, but nothing ever provided a permanent fix. I spent years studying netcode, frame rates, frame pacing, 1% and 0.01% lows, and tools like Perfmoon. Honestly, I'm grateful that Counter-Strike 1.6 turned me into a tech geek.At this point, I believe it’s a combination of multiple factors:Network Jitter and UDP Packets: This is the hardest variable to measure. It is the hidden enemy of online gaming. Many ISPs actively prioritize UDP packets for streaming services like Netflix over the tiny, time-sensitive data packets used by competitive games like Counter-Strike.Offline Judder and Visual Lag: This issue exists even offline. If you search YouTube for the "Bruce Willis Juddering" clip, you’ll see a perfect example of what this visual stuttering looks like. It completely destroys competitive gameplay.Years ago, I used to have more "good gaming days." Nowadays, it feels like it only happens 1 out of 30 days, or even 1 out of 300. It’s incredibly rare to get a flawless session. Sometimes you can temporarily fix online issues by reducing Total Harmonic Distortion (THD), but the fix never lasts.For instance, you can temporarily clear static and residual energy from your PC by unplugging the PSU, removing the 24-pin motherboard cable, and holding down the case power button so the PSU capacitors drain the motherboard. You can then completely wipe the NVRAM by removing the CMOS battery and shorting the CLRTC jumpers. I only resort to this when my local power grid is so dirty that it corrupts the GPU or monitor OPROM, causing it to fail UEFI recognition. While this helps in both offline and online environments, it still doesn't permanently solve desync.If you look at professional gaming houses, they have a "perfect" environment. They use a high-end modem in bridge mode (zero NAT) paired with an enterprise-grade router running isolated VLANs and a single DHCP setup to completely avoid double NAT or CGNAT. They implement strict QoS/VLAN rules to prioritize game executables (hl.exe, hl2.exe, etc.) over any Windows background data.Furthermore, they operate on pristine electrical grids. Developed countries heavily regulate Total Harmonic Distortion (keeping it around 3-5%), whereas in Venezuela and other parts of LATAM, THD can easily spike to 15%, 20%, or even 30%. In environments like mine, you absolutely need a high-end, double-conversion online UPS with a strict 2% THD output, proper grounding that avoids daisy-chaining, and deep knowledge of your hardware limitations.To summarize, for a game to feel truly smooth today, we need:A strict 2-5% Total Harmonic Distortion (THD).Stable electrical voltage (110-120V or 220-240V).A rock-solid grid frequency that doesn't fluctuate (50Hz in Europe, 60Hz in LATAM). If you disassemble a monitor, the internal labels show their sweet spot for power frequency, usually allowing only a tiny 4% margin of error. If your power grid constantly fluctuates outside of that margin, it directly degrades the clarity of the image on your screen.It’s an incredibly complex mix of variables. Unfortunately, living here in Venezuela makes it very difficult and expensive to acquire the high-end equipment needed to test and isolate all of these electrical and network issues.It’s incredibly frustrating because it completely drains the fun out of gaming. I can’t even enjoy offline games anymore because I constantly notice the visual judder, micro-stutters, and desync.God bless you all. I'm not a religious person, but I just wanted to share my story and send some love to this community! <3"

PS: had to help myself with the AI fixing my Grammar, thanks again.

[xVenom]

Hi bro!
I’ve two Xbox one and a ryzen 5 5500u. My issue is that there’s some type of desync, tbh I don’t know what causes this bc it happens with every software/hardware I use to play and location. I’ve encountered some temporary fixes mainly changing how I do interact with the controller or the composition of my hand’s skin, still the lag returns periodically in minutes.
What happens in rocket league on 50/50s the physics seems to always favor the opponent, my car seems to have some type of disability bc it’s slower than others.
On overwatch enemies always seems to have some type of superpower cuz even if I hit them directly with Sigma when they r almost with no health they seem to survive or directly the game doesn’t register or registers “wrong”the shot. Anyway my question here is on what category does this fall?

How is your internet connection? Have your measured your jitter and bufferbloat?

[xVenom]

Edit - If you want help describe your problem clearly with proper context and your pc specs. If you wanna argue or want to make others feel hopeless please stay away.

I know a lot of you are struggling with your games right now. I've been there, and let me tell you straight up: it's fixable.

The problem is that when you don't really understand what's going wrong, every "fix" you try feels like a drop in the ocean. So before anything else, let's actually understand the problem and name it properly. It can come down to your hardware, your software, or your internet. But let me be clear about one thing: your electricity is not the reason. If it was, it would've been proven with real tests and real numbers by now. From my own experience of 4 years of struggle, research and helping my friends, the eletricity really isn't a problem.

Let's start with the glossary terms you need to describe what you're actually feeling in-game.

Input Delay (floaty aim, heavy mouse)
This is when your actions show up late on screen. People usually describe it as floaty aim or a heavy mouse. If this is your problem, your focus should be entirely on hardware and software settings. Nothing else.

Hitreg issues
Forget "i shot him" for a second and think about sprays and hip fires. You know how a lot of high-rank players get insane hitreg even while spraying or hip firing? That's not random or lucky. If your bullets pass through a character, the game should register a hit. If it doesn't, your game client isn't in sync with the game server. Why does that happen? Hardware and network. So that's where you look.

Interpolation buffer (that "behind the server" feeling)
This one is controlled by the game client, and developers built it in for one main reason: network jitter. You are never shown the exact live state of the game. There's always some delay between you and the server, and the client adds a buffer on top of that so enemy movement stays smooth even when packets arrive unevenly.

Quick example: on a 60Hz server, packets are sent roughly every 16.6ms. If your connection has jitter, the client bumps the buffer up by a tick or so, giving it enough room to interpolate enemy movement instead of stuttering.

This is a completely different headache, and honestly I've suffered with this one for a while. Good internet, good hitreg, and yet I'd still get lasered by people who were clearly bad. Guys I couldn't even react to, or who seemed to have inhuman reactions to my peeks. That feeling is this.

Desync
This is a really wide term that can mean any of the things above or all things combined. That's exactly why you have to fix it layer by layer instead of chasing one magic setting.

---

Where to actually look for fixes

Input Delay - Always hardware and software settings. It has nothing to do with your internet or your electricity. Sure, EMI can technically play a role, but that would be an extreme case, not the small heavy feeling most of us get. Focus on optimizing your hardware and software.
Areas to look at: DPC latency, interrupt latency, RTC/timer resolution, CPU clock speed, bad drivers, core affinity, and BIOS settings.

Hitreg - Network and hardware settings. Frametimes can cause hitreg issues too. Your internet can cause it, and your Windows network settings can play a role as well. So how do you measure it? Tools like iperf3 and hping let you test your UDP connection. With iperf3 you can send small UDP packets that mimic real game traffic almost exactly, which tells you a lot about what your connection is really doing.
Areas to look at: network quality, frametime, 1% lows, and network adapter settings.

Interpolation buffer - This is where most people suffer, because barely anyone actually knows what it is, and there's almost nothing written about it from the player's side. The causes are wide: network, hardware, or OS settings.
Areas to look at: packet pacing, network adapter driver and settings, and CPU/GPU frametime.

If you really want to understand little deep, go read about the PC latency pipeline (Nvidia has documentation on it, and Gamers Nexus made a good video too), and also look into how network packet pacing affect interpolation. I cant post links here yet.

Here's the big takeaway when it comes to gaming: the lowest latency isn't what matters most, consistency is. Whether it's your network packets or your frame times, steady and consistent pacing beats raw speed every time.

I'll be putting together a full optimization guide soon, once I have the time to write everything down properly in a GitHub repo or a single doc. In the meantime, if you really think your problem comes down to factors you can't control, like electricity, reply below and I'll try to prove otherwise by helping you optimize it in my free time. ( preferably someone who has already posted here in the past that had issue for long time).

Being a pro takes skill, no one's denying that. But not a lot of people want to admit that good internet and good hardware play a huge role in separating the top players from everyone else.

Ive had this feeling off being behind the server people shooting too fast to react to and my hit reg feels off IN MULTIPLE Games : Apex legends, Valorant , R6 (I was t3 player in val, champ r6 , master in apex ) so i dont think its a skill issue personally and Ive changed my pc THREE times with all components and still have this problem , sometimes i do some random "tweaks" that remove the issue for lets say a day and it all comes crashing down again.

My pc specs :

Msi b850 Gaming pro
32 gb ddr5 ram g skill ripjaws M5 cl 36
ryzen 7 7800x3d
Msi 5060 gaming
m.2 Kingston SNV321000g

the only thing I think could be the problem is electricity i dont believe the my house has earthing (Not knowlegeble in the "engineering aspect") so can that be the issue Idk at this point

DId you check your udp jitter with iperf3 or any other tests? How does your frametime graph and 1% low look like?
You can dm me on discord - xvenom_03

Private messaged this guy. Got no answer after some time and he wont add my discord either.
Any updates?

Ive already told you multiple times to post it in this topic instead of private forum messages as i dont look in it. Also if you sending a req in discord do send with a message. I wont accept req without proper context.

[xVenom]

I’ve been around since 2009. I actually started playing Counter-Strike on Steam back in 2006. People online might know me as haze, cloudhaze, or x58haze on GitHub and other platforms.I vividly remember when this whole issue became a hot topic. It was all thanks to a legendary Steam forum thread that has since been deleted. It was titled "CS isn't smooth in 2009." It was so iconic that it sparked the entire community conversation around desync, input lag, hit registration issues (bullets doing zero damage), "Ferrari peeking," and that awful heavy mouse feeling. It made you feel like you were trapped in a 4:3 stretched jail—your heart racing just trying to aim, while other players looked completely relaxed, jumping around and enjoying a flawless, crisp connection. That thread was amazing; it had thousands of comments analyzing different PC builds, power conditioners, and tweaks.Yet, here we are today, still facing the exact same weird issues. We all know that rare feeling when the game suddenly behaves perfectly: footsteps are crystal clear, utility trajectories look incredibly smooth, your reaction time peaks, and enemies seem to move in slow motion, making them easy to aim at.I’ve been down the ultimate rabbit hole trying to fix this. I used to mod BIOS files, revive bricked motherboards using CH341A programmers, desolder chips, mess with USB latencies, disable Windows background services, and tweak OS kernels and timers like crazy. I’ve formatted Windows thousands of times, but nothing ever provided a permanent fix. I spent years studying netcode, frame rates, frame pacing, 1% and 0.01% lows, and tools like Perfmoon. Honestly, I'm grateful that Counter-Strike 1.6 turned me into a tech geek.At this point, I believe it’s a combination of multiple factors:Network Jitter and UDP Packets: This is the hardest variable to measure. It is the hidden enemy of online gaming. Many ISPs actively prioritize UDP packets for streaming services like Netflix over the tiny, time-sensitive data packets used by competitive games like Counter-Strike.Offline Judder and Visual Lag: This issue exists even offline. If you search YouTube for the "Bruce Willis Juddering" clip, you’ll see a perfect example of what this visual stuttering looks like. It completely destroys competitive gameplay.Years ago, I used to have more "good gaming days." Nowadays, it feels like it only happens 1 out of 30 days, or even 1 out of 300. It’s incredibly rare to get a flawless session. Sometimes you can temporarily fix online issues by reducing Total Harmonic Distortion (THD), but the fix never lasts.For instance, you can temporarily clear static and residual energy from your PC by unplugging the PSU, removing the 24-pin motherboard cable, and holding down the case power button so the PSU capacitors drain the motherboard. You can then completely wipe the NVRAM by removing the CMOS battery and shorting the CLRTC jumpers. I only resort to this when my local power grid is so dirty that it corrupts the GPU or monitor OPROM, causing it to fail UEFI recognition. While this helps in both offline and online environments, it still doesn't permanently solve desync.If you look at professional gaming houses, they have a "perfect" environment. They use a high-end modem in bridge mode (zero NAT) paired with an enterprise-grade router running isolated VLANs and a single DHCP setup to completely avoid double NAT or CGNAT. They implement strict QoS/VLAN rules to prioritize game executables (hl.exe, hl2.exe, etc.) over any Windows background data.Furthermore, they operate on pristine electrical grids. Developed countries heavily regulate Total Harmonic Distortion (keeping it around 3-5%), whereas in Venezuela and other parts of LATAM, THD can easily spike to 15%, 20%, or even 30%. In environments like mine, you absolutely need a high-end, double-conversion online UPS with a strict 2% THD output, proper grounding that avoids daisy-chaining, and deep knowledge of your hardware limitations.To summarize, for a game to feel truly smooth today, we need:A strict 2-5% Total Harmonic Distortion (THD).Stable electrical voltage (110-120V or 220-240V).A rock-solid grid frequency that doesn't fluctuate (50Hz in Europe, 60Hz in LATAM). If you disassemble a monitor, the internal labels show their sweet spot for power frequency, usually allowing only a tiny 4% margin of error. If your power grid constantly fluctuates outside of that margin, it directly degrades the clarity of the image on your screen.It’s an incredibly complex mix of variables. Unfortunately, living here in Venezuela makes it very difficult and expensive to acquire the high-end equipment needed to test and isolate all of these electrical and network issues.It’s incredibly frustrating because it completely drains the fun out of gaming. I can’t even enjoy offline games anymore because I constantly notice the visual judder, micro-stutters, and desync.God bless you all. I'm not a religious person, but I just wanted to share my story and send some love to this community! <3"

PS: had to help myself with the AI fixing my Grammar, thanks again.

First, it is impressive that you have covered so many topics. I suffered for such a long time myself that I quit competitive gaming back in 2021. I know that feeling when everything is in sync and no one can touch you unless they outplay you. But while I agree with all your points on the network side (VLANs, QoS at the proper interface for outbound and inbound, and making sure your connection isn't CGNAT), I am not really convinced of this "dirty electricity" concept causing desync. Now, I am not saying it won't cause *any* issues, but if it did, you would know. Your clocks, voltage, BCLK, and in extreme cases, your monitor would fluctuate, and your frametimes would show symptoms of it at the very least.

Game netcodes have come a long way, so even subtle network jitter will only put you behind by one tick (which is still not great, but so much better than the desync described by most people here). While not every pro starts from a gaming house, I have known and seen a lot of players with incredible gaming experience. There are many layers where testing can go wrong, and a lot of popular guides already cover them.

Since you are already too deep into it:

Hardware Side:

CPU & RAM: Make sure your clocks are stable and that the system is not thermal or power throttling. Ensure your RAM is running in 1:1:1 (though technically, a 1:1 UCLK to MEMCLK ratio is more important, along with finding a stable FCLK for your system on Ryzen). Also, remember that finding stability depends heavily on your motherboard's VRM quality.
Network Adapter: A NIC with built-in hardware queues works best.

Measuring on the Windows Side:

ISR / DPC: LatencyMon. While a lot of people concentrate on the highest DPC values, the equal important thing is your average DPC values aswell.
RTTS & CapX: Use these for frametimes, 1% and 0.1% lows, and your game thread clock speed.

I will share one observation I made while trying to help a friend: his P-state in the BIOS was set to P-state 1, which played a huge role in poor 0.1% lows that weren't really visible on the monitor except for a few hitches. But it's not just the main game logic thread that spoils the experience; the network thread can also be affected, adding another layer to the poor experience.

WPT (Windows Performance Toolkit): This is the most interesting and revealing part if everything else looks fine. Here, you can see all your game threads and what cores are being used for them (checking whether some other process or app is using the same threads as the game). The tricky part is that while processes are named, game threads themselves are not explicitly named (they could be the game network thread, main game logic thread, or render thread), so you have to use logic to isolate them.

For example, to isolate and crosscheck the network thread, you have two options:

1. Under your game process threads, you can check for threads that have had interrupts matching your game server Hz (you would have interrupts every 8.3ms if its 120h server , so you check in a variance close to your network jitter, and you will find your network thread easily).
2. The easiest way is to look under your network driver process (usually NDIS), where you can see interrupts with connection IPs. Note the time and check which game thread matches that timing. This gives you a more realistic way to measure if a packet that hit your PC is being delayed or instantly delivered to your game process.

While WPT is really for advanced users, it will help you isolate problems specific to drivers, OS scheduling of your game process, network thread delays, ISR times, and saturation.

Network Side:

If you want a simple way without a lot of hassle, record a Wireshark capture while playing a game, then isolate the downstream of your game traffic and give it to Claude along with your game server tick rate so the AI can check for packet pacing jitter. It will tell you if feeling behind the server is due to network jitter, which causes the game client to set a high interpolation buffer. Of course, this will only tell you the downstream quality, not the upstream. If you want to measure both, iperf3 measures it somewhat accurately.

If you want to fully isolate it, we have to split it into:

1. Internet - Your WAN Device (Your First Router)
To test this, I personally use a 60Hz UDP test script I coded to test pacing from and to servers via my first WAN device. It helps me measure pacing, gaps, and packet batching. I run it on a server that mimics similar routing to and from game server locations (some say routing is different so it doesn't tell the whole story, but ignore them—most saturation occurs at the OLT collection point anyway, which is before peering; otherwise, gpns like ExitLag would have already fixed it). If this gives you perfect values (generally a good jitter below 2ms), then your internet connection is fine.

2. Your Local Setup (Router to PC)
If you have a router running a Linux OS like OpenWrt, it is easy to measure using tcpdump. The best run is when playing a game. Run tcpdump on the WAN interface and run Wireshark on your PC at the same time. Make sure you isolate your game connection either by IP or port before running it, otherwise it will be a mess.

Then, compare them both, find the packet ID, and crosscheck the timings. While you can't perfectly match timings (since there will be a slight difference the moment you start the test on both sides), the proper way to check is by analyzing the pacing through interpacket gaps, which will give you a clear picture of your local network quality and bufferbloat. Though remember, bufferbloat can also create queuing on the WAN interface itself for downstream traffic, so this isn't a completely reliable way to measure bufferbloat entirely.

But properfix for local bufferbloat would be Limiting your bandwidth with an qos and dscp values for traffic priority.

This post assumes familiarity with these technical terms, it's not aimed at basic users. I'd like to turn it into a full guide at some point, but that's a much bigger undertaking it needs a lot of background explanation for everyone who don't already have this knowledge, and that takes real time to put together properly.

[astroasis]

The blurriness and desync is coming back at my new house after 6 months since moving in. The old thing of moving random cables effecting it and turning light switches on and off has returned. When I first moved in this wasn't happening. The creator doesn't want us playing games or something, unlucky guys maybe next life will be better

[TN_fun]

The blurriness and desync is coming back at my new house after 6 months since moving in. The old thing of moving random cables effecting it and turning light switches on and off has returned. When I first moved in this wasn't happening. The creator doesn't want us playing games or something, unlucky guys maybe next life will be better

You know, man, your message made me cry (I'm not kidding). My life is pretty shitty, and online PC games were the only thing that brought me joy and fun. I used to play a lot with my friends, etc. But this input lag issue ruined everything; I became nervous, irritable, and even aggressive. For about a year now, I haven’t been playing online, but my life (IRL) has gotten even shittier, with even more pain and suffering. It feels like I'm just meant to suffer. And now, the suffering I had from the input lag doesn't seem that bad anymore. I don't know, man. Try to do whatever brings you joy and causes less suffering.I hope we can all find happiness and joy in something, at least.Or that someone will manage to fix this input lag issue and be happy too.

[darkbebe]

I’ve been around since 2009. I actually started playing Counter-Strike on Steam back in 2006. People online might know me as haze, cloudhaze, or x58haze on GitHub and other platforms.I vividly remember when this whole issue became a hot topic. It was all thanks to a legendary Steam forum thread that has since been deleted. It was titled "CS isn't smooth in 2009." It was so iconic that it sparked the entire community conversation around desync, input lag, hit registration issues (bullets doing zero damage), "Ferrari peeking," and that awful heavy mouse feeling. It made you feel like you were trapped in a 4:3 stretched jail—your heart racing just trying to aim, while other players looked completely relaxed, jumping around and enjoying a flawless, crisp connection. That thread was amazing; it had thousands of comments analyzing different PC builds, power conditioners, and tweaks.Yet, here we are today, still facing the exact same weird issues. We all know that rare feeling when the game suddenly behaves perfectly: footsteps are crystal clear, utility trajectories look incredibly smooth, your reaction time peaks, and enemies seem to move in slow motion, making them easy to aim at.I’ve been down the ultimate rabbit hole trying to fix this. I used to mod BIOS files, revive bricked motherboards using CH341A programmers, desolder chips, mess with USB latencies, disable Windows background services, and tweak OS kernels and timers like crazy. I’ve formatted Windows thousands of times, but nothing ever provided a permanent fix. I spent years studying netcode, frame rates, frame pacing, 1% and 0.01% lows, and tools like Perfmoon. Honestly, I'm grateful that Counter-Strike 1.6 turned me into a tech geek.At this point, I believe it’s a combination of multiple factors:Network Jitter and UDP Packets: This is the hardest variable to measure. It is the hidden enemy of online gaming. Many ISPs actively prioritize UDP packets for streaming services like Netflix over the tiny, time-sensitive data packets used by competitive games like Counter-Strike.Offline Judder and Visual Lag: This issue exists even offline. If you search YouTube for the "Bruce Willis Juddering" clip, you’ll see a perfect example of what this visual stuttering looks like. It completely destroys competitive gameplay.Years ago, I used to have more "good gaming days." Nowadays, it feels like it only happens 1 out of 30 days, or even 1 out of 300. It’s incredibly rare to get a flawless session. Sometimes you can temporarily fix online issues by reducing Total Harmonic Distortion (THD), but the fix never lasts.For instance, you can temporarily clear static and residual energy from your PC by unplugging the PSU, removing the 24-pin motherboard cable, and holding down the case power button so the PSU capacitors drain the motherboard. You can then completely wipe the NVRAM by removing the CMOS battery and shorting the CLRTC jumpers. I only resort to this when my local power grid is so dirty that it corrupts the GPU or monitor OPROM, causing it to fail UEFI recognition. While this helps in both offline and online environments, it still doesn't permanently solve desync.If you look at professional gaming houses, they have a "perfect" environment. They use a high-end modem in bridge mode (zero NAT) paired with an enterprise-grade router running isolated VLANs and a single DHCP setup to completely avoid double NAT or CGNAT. They implement strict QoS/VLAN rules to prioritize game executables (hl.exe, hl2.exe, etc.) over any Windows background data.Furthermore, they operate on pristine electrical grids. Developed countries heavily regulate Total Harmonic Distortion (keeping it around 3-5%), whereas in Venezuela and other parts of LATAM, THD can easily spike to 15%, 20%, or even 30%. In environments like mine, you absolutely need a high-end, double-conversion online UPS with a strict 2% THD output, proper grounding that avoids daisy-chaining, and deep knowledge of your hardware limitations.To summarize, for a game to feel truly smooth today, we need:A strict 2-5% Total Harmonic Distortion (THD).Stable electrical voltage (110-120V or 220-240V).A rock-solid grid frequency that doesn't fluctuate (50Hz in Europe, 60Hz in LATAM). If you disassemble a monitor, the internal labels show their sweet spot for power frequency, usually allowing only a tiny 4% margin of error. If your power grid constantly fluctuates outside of that margin, it directly degrades the clarity of the image on your screen.It’s an incredibly complex mix of variables. Unfortunately, living here in Venezuela makes it very difficult and expensive to acquire the high-end equipment needed to test and isolate all of these electrical and network issues.It’s incredibly frustrating because it completely drains the fun out of gaming. I can’t even enjoy offline games anymore because I constantly notice the visual judder, micro-stutters, and desync.God bless you all. I'm not a religious person, but I just wanted to share my story and send some love to this community! <3"

PS: had to help myself with the AI fixing my Grammar, thanks again.

First, it is impressive that you have covered so many topics. I suffered for such a long time myself that I quit competitive gaming back in 2021. I know that feeling when everything is in sync and no one can touch you unless they outplay you. But while I agree with all your points on the network side (VLANs, QoS at the proper interface for outbound and inbound, and making sure your connection isn't CGNAT), I am not really convinced of this "dirty electricity" concept causing desync. Now, I am not saying it won't cause *any* issues, but if it did, you would know. Your clocks, voltage, BCLK, and in extreme cases, your monitor would fluctuate, and your frametimes would show symptoms of it at the very least.

Game netcodes have come a long way, so even subtle network jitter will only put you behind by one tick (which is still not great, but so much better than the desync described by most people here). While not every pro starts from a gaming house, I have known and seen a lot of players with incredible gaming experience. There are many layers where testing can go wrong, and a lot of popular guides already cover them.

Since you are already too deep into it:

Hardware Side:

CPU & RAM: Make sure your clocks are stable and that the system is not thermal or power throttling. Ensure your RAM is running in 1:1:1 (though technically, a 1:1 UCLK to MEMCLK ratio is more important, along with finding a stable FCLK for your system on Ryzen). Also, remember that finding stability depends heavily on your motherboard's VRM quality.
Network Adapter: A NIC with built-in hardware queues works best.

Measuring on the Windows Side:

ISR / DPC: LatencyMon. While a lot of people concentrate on the highest DPC values, the equal important thing is your average DPC values aswell.
RTTS & CapX: Use these for frametimes, 1% and 0.1% lows, and your game thread clock speed.

I will share one observation I made while trying to help a friend: his P-state in the BIOS was set to P-state 1, which played a huge role in poor 0.1% lows that weren't really visible on the monitor except for a few hitches. But it's not just the main game logic thread that spoils the experience; the network thread can also be affected, adding another layer to the poor experience.

WPT (Windows Performance Toolkit): This is the most interesting and revealing part if everything else looks fine. Here, you can see all your game threads and what cores are being used for them (checking whether some other process or app is using the same threads as the game). The tricky part is that while processes are named, game threads themselves are not explicitly named (they could be the game network thread, main game logic thread, or render thread), so you have to use logic to isolate them.

For example, to isolate and crosscheck the network thread, you have two options:

1. Under your game process threads, you can check for threads that have had interrupts matching your game server Hz (you would have interrupts every 8.3ms if its 120h server , so you check in a variance close to your network jitter, and you will find your network thread easily).
2. The easiest way is to look under your network driver process (usually NDIS), where you can see interrupts with connection IPs. Note the time and check which game thread matches that timing. This gives you a more realistic way to measure if a packet that hit your PC is being delayed or instantly delivered to your game process.

While WPT is really for advanced users, it will help you isolate problems specific to drivers, OS scheduling of your game process, network thread delays, ISR times, and saturation.

Network Side:

If you want a simple way without a lot of hassle, record a Wireshark capture while playing a game, then isolate the downstream of your game traffic and give it to Claude along with your game server tick rate so the AI can check for packet pacing jitter. It will tell you if feeling behind the server is due to network jitter, which causes the game client to set a high interpolation buffer. Of course, this will only tell you the downstream quality, not the upstream. If you want to measure both, iperf3 measures it somewhat accurately.

If you want to fully isolate it, we have to split it into:

1. Internet - Your WAN Device (Your First Router)
To test this, I personally use a 60Hz UDP test script I coded to test pacing from and to servers via my first WAN device. It helps me measure pacing, gaps, and packet batching. I run it on a server that mimics similar routing to and from game server locations (some say routing is different so it doesn't tell the whole story, but ignore them—most saturation occurs at the OLT collection point anyway, which is before peering; otherwise, gpns like ExitLag would have already fixed it). If this gives you perfect values (generally a good jitter below 2ms), then your internet connection is fine.

2. Your Local Setup (Router to PC)
If you have a router running a Linux OS like OpenWrt, it is easy to measure using tcpdump. The best run is when playing a game. Run tcpdump on the WAN interface and run Wireshark on your PC at the same time. Make sure you isolate your game connection either by IP or port before running it, otherwise it will be a mess.

Then, compare them both, find the packet ID, and crosscheck the timings. While you can't perfectly match timings (since there will be a slight difference the moment you start the test on both sides), the proper way to check is by analyzing the pacing through interpacket gaps, which will give you a clear picture of your local network quality and bufferbloat. Though remember, bufferbloat can also create queuing on the WAN interface itself for downstream traffic, so this isn't a completely reliable way to measure bufferbloat entirely.

But properfix for local bufferbloat would be Limiting your bandwidth with an qos and dscp values for traffic priority.

This post assumes familiarity with these technical terms, it's not aimed at basic users. I'd like to turn it into a full guide at some point, but that's a much bigger undertaking it needs a lot of background explanation for everyone who don't already have this knowledge, and that takes real time to put together properly.

Hello , i would like to know if changing my ethernet card "speed & duplex" from as example " 10gb/s to 100mb/s is the same as "limiting my bandwidth with a qos please"?
If it's not the same , what do you recommend as a bandwidth limit with the qos?

[Kipperii]

I’ve been around since 2009. I actually started playing Counter-Strike on Steam back in 2006. People online might know me as haze, cloudhaze, or x58haze on GitHub and other platforms.I vividly remember when this whole issue became a hot topic. It was all thanks to a legendary Steam forum thread that has since been deleted. It was titled "CS isn't smooth in 2009." It was so iconic that it sparked the entire community conversation around desync, input lag, hit registration issues (bullets doing zero damage), "Ferrari peeking," and that awful heavy mouse feeling. It made you feel like you were trapped in a 4:3 stretched jail—your heart racing just trying to aim, while other players looked completely relaxed, jumping around and enjoying a flawless, crisp connection. That thread was amazing; it had thousands of comments analyzing different PC builds, power conditioners, and tweaks.Yet, here we are today, still facing the exact same weird issues. We all know that rare feeling when the game suddenly behaves perfectly: footsteps are crystal clear, utility trajectories look incredibly smooth, your reaction time peaks, and enemies seem to move in slow motion, making them easy to aim at.I’ve been down the ultimate rabbit hole trying to fix this. I used to mod BIOS files, revive bricked motherboards using CH341A programmers, desolder chips, mess with USB latencies, disable Windows background services, and tweak OS kernels and timers like crazy. I’ve formatted Windows thousands of times, but nothing ever provided a permanent fix. I spent years studying netcode, frame rates, frame pacing, 1% and 0.01% lows, and tools like Perfmoon. Honestly, I'm grateful that Counter-Strike 1.6 turned me into a tech geek.At this point, I believe it’s a combination of multiple factors:Network Jitter and UDP Packets: This is the hardest variable to measure. It is the hidden enemy of online gaming. Many ISPs actively prioritize UDP packets for streaming services like Netflix over the tiny, time-sensitive data packets used by competitive games like Counter-Strike.Offline Judder and Visual Lag: This issue exists even offline. If you search YouTube for the "Bruce Willis Juddering" clip, you’ll see a perfect example of what this visual stuttering looks like. It completely destroys competitive gameplay.Years ago, I used to have more "good gaming days." Nowadays, it feels like it only happens 1 out of 30 days, or even 1 out of 300. It’s incredibly rare to get a flawless session. Sometimes you can temporarily fix online issues by reducing Total Harmonic Distortion (THD), but the fix never lasts.For instance, you can temporarily clear static and residual energy from your PC by unplugging the PSU, removing the 24-pin motherboard cable, and holding down the case power button so the PSU capacitors drain the motherboard. You can then completely wipe the NVRAM by removing the CMOS battery and shorting the CLRTC jumpers. I only resort to this when my local power grid is so dirty that it corrupts the GPU or monitor OPROM, causing it to fail UEFI recognition. While this helps in both offline and online environments, it still doesn't permanently solve desync.If you look at professional gaming houses, they have a "perfect" environment. They use a high-end modem in bridge mode (zero NAT) paired with an enterprise-grade router running isolated VLANs and a single DHCP setup to completely avoid double NAT or CGNAT. They implement strict QoS/VLAN rules to prioritize game executables (hl.exe, hl2.exe, etc.) over any Windows background data.Furthermore, they operate on pristine electrical grids. Developed countries heavily regulate Total Harmonic Distortion (keeping it around 3-5%), whereas in Venezuela and other parts of LATAM, THD can easily spike to 15%, 20%, or even 30%. In environments like mine, you absolutely need a high-end, double-conversion online UPS with a strict 2% THD output, proper grounding that avoids daisy-chaining, and deep knowledge of your hardware limitations.To summarize, for a game to feel truly smooth today, we need:A strict 2-5% Total Harmonic Distortion (THD).Stable electrical voltage (110-120V or 220-240V).A rock-solid grid frequency that doesn't fluctuate (50Hz in Europe, 60Hz in LATAM). If you disassemble a monitor, the internal labels show their sweet spot for power frequency, usually allowing only a tiny 4% margin of error. If your power grid constantly fluctuates outside of that margin, it directly degrades the clarity of the image on your screen.It’s an incredibly complex mix of variables. Unfortunately, living here in Venezuela makes it very difficult and expensive to acquire the high-end equipment needed to test and isolate all of these electrical and network issues.It’s incredibly frustrating because it completely drains the fun out of gaming. I can’t even enjoy offline games anymore because I constantly notice the visual judder, micro-stutters, and desync.God bless you all. I'm not a religious person, but I just wanted to share my story and send some love to this community! <3"

PS: had to help myself with the AI fixing my Grammar, thanks again.

First, it is impressive that you have covered so many topics. I suffered for such a long time myself that I quit competitive gaming back in 2021. I know that feeling when everything is in sync and no one can touch you unless they outplay you. But while I agree with all your points on the network side (VLANs, QoS at the proper interface for outbound and inbound, and making sure your connection isn't CGNAT), I am not really convinced of this "dirty electricity" concept causing desync. Now, I am not saying it won't cause *any* issues, but if it did, you would know. Your clocks, voltage, BCLK, and in extreme cases, your monitor would fluctuate, and your frametimes would show symptoms of it at the very least.

Game netcodes have come a long way, so even subtle network jitter will only put you behind by one tick (which is still not great, but so much better than the desync described by most people here). While not every pro starts from a gaming house, I have known and seen a lot of players with incredible gaming experience. There are many layers where testing can go wrong, and a lot of popular guides already cover them.

Since you are already too deep into it:

Hardware Side:

CPU & RAM: Make sure your clocks are stable and that the system is not thermal or power throttling. Ensure your RAM is running in 1:1:1 (though technically, a 1:1 UCLK to MEMCLK ratio is more important, along with finding a stable FCLK for your system on Ryzen). Also, remember that finding stability depends heavily on your motherboard's VRM quality.
Network Adapter: A NIC with built-in hardware queues works best.

Measuring on the Windows Side:

ISR / DPC: LatencyMon. While a lot of people concentrate on the highest DPC values, the equal important thing is your average DPC values aswell.
RTTS & CapX: Use these for frametimes, 1% and 0.1% lows, and your game thread clock speed.

I will share one observation I made while trying to help a friend: his P-state in the BIOS was set to P-state 1, which played a huge role in poor 0.1% lows that weren't really visible on the monitor except for a few hitches. But it's not just the main game logic thread that spoils the experience; the network thread can also be affected, adding another layer to the poor experience.

WPT (Windows Performance Toolkit): This is the most interesting and revealing part if everything else looks fine. Here, you can see all your game threads and what cores are being used for them (checking whether some other process or app is using the same threads as the game). The tricky part is that while processes are named, game threads themselves are not explicitly named (they could be the game network thread, main game logic thread, or render thread), so you have to use logic to isolate them.

For example, to isolate and crosscheck the network thread, you have two options:

1. Under your game process threads, you can check for threads that have had interrupts matching your game server Hz (you would have interrupts every 8.3ms if its 120h server , so you check in a variance close to your network jitter, and you will find your network thread easily).
2. The easiest way is to look under your network driver process (usually NDIS), where you can see interrupts with connection IPs. Note the time and check which game thread matches that timing. This gives you a more realistic way to measure if a packet that hit your PC is being delayed or instantly delivered to your game process.

While WPT is really for advanced users, it will help you isolate problems specific to drivers, OS scheduling of your game process, network thread delays, ISR times, and saturation.

Network Side:

If you want a simple way without a lot of hassle, record a Wireshark capture while playing a game, then isolate the downstream of your game traffic and give it to Claude along with your game server tick rate so the AI can check for packet pacing jitter. It will tell you if feeling behind the server is due to network jitter, which causes the game client to set a high interpolation buffer. Of course, this will only tell you the downstream quality, not the upstream. If you want to measure both, iperf3 measures it somewhat accurately.

If you want to fully isolate it, we have to split it into:

1. Internet - Your WAN Device (Your First Router)
To test this, I personally use a 60Hz UDP test script I coded to test pacing from and to servers via my first WAN device. It helps me measure pacing, gaps, and packet batching. I run it on a server that mimics similar routing to and from game server locations (some say routing is different so it doesn't tell the whole story, but ignore them—most saturation occurs at the OLT collection point anyway, which is before peering; otherwise, gpns like ExitLag would have already fixed it). If this gives you perfect values (generally a good jitter below 2ms), then your internet connection is fine.

2. Your Local Setup (Router to PC)
If you have a router running a Linux OS like OpenWrt, it is easy to measure using tcpdump. The best run is when playing a game. Run tcpdump on the WAN interface and run Wireshark on your PC at the same time. Make sure you isolate your game connection either by IP or port before running it, otherwise it will be a mess.

Then, compare them both, find the packet ID, and crosscheck the timings. While you can't perfectly match timings (since there will be a slight difference the moment you start the test on both sides), the proper way to check is by analyzing the pacing through interpacket gaps, which will give you a clear picture of your local network quality and bufferbloat. Though remember, bufferbloat can also create queuing on the WAN interface itself for downstream traffic, so this isn't a completely reliable way to measure bufferbloat entirely.

But properfix for local bufferbloat would be Limiting your bandwidth with an qos and dscp values for traffic priority.

This post assumes familiarity with these technical terms, it's not aimed at basic users. I'd like to turn it into a full guide at some point, but that's a much bigger undertaking it needs a lot of background explanation for everyone who don't already have this knowledge, and that takes real time to put together properly.

Hello , i would like to know if changing my ethernet card "speed & duplex" from as example " 10gb/s to 100mb/s is the same as "limiting my bandwidth with a qos please"?
If it's not the same , what do you recommend as a bandwidth limit with the qos?

Buy a router with cake/sq_fodel and set it to like 80-90% bandwidth