Who you gonna call? The Blur Busters! For Everything Better Than 60Hz™
https://forums.blurbusters.com/
you just lower power consumption with fix fps to 6. It like windows reinstall or full power off pc.13n47 wrote: ↑03 Aug 2025, 06:11For Valorant the issue comes down purely down to netcode. The most consistent way I can fix my match is to change the FPS limit to very low(like 6fps) before joining the match. Let it sit for the first 15 seconds and then back to unlimited. It's not guaranteed to work but with this method I gained a shitton more consistency whereas before every match felt like shit. Also limiting to 128 fps is still giving more consistency.
There's something happening during match init that heavily impacts the game feel. Most likely network buffers or some interp calculations.
There is absolutely nothing wrong with your hardware or internet. And I'm pretty sure CS2 could have something similar although i haven't tested on that yet.
For example, if you introduce packet loss during a match or match init and then remove the packet loss, the hit reg might get slightly faster but enemy player models start moving much faster. I don't understand why the game engine cannot restore the game to a previous state.
Also duplicating outgoing packets to the server has similar effect but less wonky movement for enemy models. I'm assuming server now receives packets slightly faster because some are bound to arrive faster and thus lowers the network buffering on server side, making your shots register faster.
Hi. from my side , i've noticed that jitter (flat green line or spikes) has nothing to do with hit registration problem , same for the ping. I have played many many games and noticed that sometimes you can hit well with jitters even with red lines ! sometimes not at all . same for flat green one. 35 or 100 ping , same . i had some really good hit register on few 100ms games (like 2 out of 100 games ) , it felt better than 99% of my 35 ping games.andrelip wrote: ↑04 Aug 2025, 16:59Nice topic, OP!
I noticed the same issue and did some testing with OpenWRT (Cake QoS, traffic control, and so forth).
Some observations:
1) Here, using Cake QoS and having some load, I get lower latency (by about 2 ms) compared to when the connection is idle. It's probably due to power saving on the ISP's fiber modem. If you enable the CS2 network graph, it's the difference between green spikes and a completely flat line.
2) It actually seems to perform worse when it's flat. The game feels smooth, but it really feels like everyone else suddenly got better.
Now, some points to consider:
1) We may be seeing some form of batching (like interrupt moderation), which could occur on your PC or at any other node. Small packets might be delayed until a batch is full or a time limit is reached. So larger requests may force packets to be sent or received immediately.
2) A "clean" connection might also mean your packets are reaching the server faster, so enemies’ reactions feel quicker too. That could make hitting them feel harder. It’s plausible—but I suspect that’s not the main cause.
3) The attacker might be experiencing connectivity issues, allowing them to see and shoot you before your game is updated. This gives them several milliseconds of advantage. You're basically seeing their past movements, so peekers' advantage gets amplified a lot.
4) I think there are some ways to check prediction and lag compensation/hitbox behavior. That might help troubleshoot what’s really going on.
5) When watching demos, we may or may not be seeing the "normalized" version. The server’s real-time view of a player might not match what’s shown in the demo.
6) CS2 left-down numbers are 100% network related and added by Valve to investigate some weird video. Maybe it can help identifying good and bad state. See more here: https://www.reddit.com/r/GlobalOffensiv ... _this_sub/
----
[cs2 network info in left-down]
Gameplay captures must include legible r_show_build_info 1
V = valve / S = dedicated / L = loopback
22 = receive latency, accurate jitter, counts buffering to smooth over packet loss
33 = latency average, send + receive, no buffering (lazy like the scoreboard value)
06 = client receive margin, spikes on interp
18 = send packet loss, this is actually 2% - more than 10% clamped to 99
09 = receive packet loss, this is actually 1% - more than 10% clamped to 99
1:0 = server issues like yellow on net graph when it can't keep up with the command queue
16 = render interpolation ms (correction: at tickrate)
07 = minimum frametime ms for the past few seconds
08 = maximum frametime ms for the past few seconds
That u think about 50% winrare balance? I have 900+ matches on one map in cs2 and game balance me noobs and absolute stacks of 5 hackers just to keep this 50% rate. Thats why game feels not the same, cause i play vs noobs and vs hackers/absolute pros who peeks and move like crazySyykfk wrote: ↑09 Jul 2025, 05:12Totally agree,MontyTheAverage wrote: ↑08 Jul 2025, 23:25It is like when the problem is mitigated, the anomaly lag breaks it again causing the temporary mitigation to not work anymore until after awhile again. FYI: this behavior has been same across games, PC systems, networks and location and hard to correlate to one cause for the problems. That is why at this point I can not make sense of this anymore. Drives me crazy
I could kill anyone in yesterday's Valorant ranked match,
and then be killed by anyone in today's ranked match, the Desync keeps changing.
I usually have no Desync after reinstalling the system, and then it keeps getting worse within a few days,
until I was killed instantly by anyone, and I angrily reinstalled Win11.
I think it's a problem with the network and the game network code.
I now only hope that Valorant can solve this problem after changing to Unreal Engine V.
{DEF3A0BE-285D-4990-B25D-5A8926E6C2F6}.png
How to explain my KD changing so drastically?
In the last game I was the god of the game, and in the next game I would be kicked to death by a randomly picked passerby like a stray dog on the roadside.
It was too hard to accept, as if all the efforts were in vain.
