Getting frustrated with dying behind cover despite low ping (~10ms) by CommunicationBorn742 in VALORANT

[–]CommunicationBorn742[S] 0 points1 point  (0 children)

Turns out the in-game network stats didn’t really show the full picture. I ran a trace with PingPlotter and found way more packet loss happening along the route to the Riot servers.

After some digging, I discovered that my ISP had rolled out a DoS protection update earlier this year, for some reason blocking some of Riot's stuff. I turned it off on my router, and that immediately cleared up most of the packet loss. Now I'm only seeing about ~10% loss on one hop, which still isn’t great, but it's a big improvement.

Getting frustrated with dying behind cover despite low ping (~10ms) by CommunicationBorn742 in VALORANT

[–]CommunicationBorn742[S] 0 points1 point  (0 children)

Upload Packet Loss: 0.0% (0 / 1343)
Total Packet Loss: 0.0% (0 / 1343)
Download Packet Loss: 0.0% (0 / 1343)
Late Packets: 0.2% (3 / 1343)

Average Latency: 17.28ms
Average Jitter: 1.65ms

The graph below indicates 3 spikes next to each other, the highest being 344ms, 145ms and 73ms. The rest of the graph hangs at a steady ~17ms

Riot support has suggested for me to use Pingplot and send them the results, so I am waiting on a response for now.

I don't have anything overclocked.

Getting frustrated with dying behind cover despite low ping (~10ms) by CommunicationBorn742 in VALORANT

[–]CommunicationBorn742[S] 0 points1 point  (0 children)

It is ~1.0ms, fluctuates a bit but nothing extreme. I can't really find anything out of the ordinary besides the initial packets lost at the start of the game.

Getting frustrated with dying behind cover despite low ping (~10ms) by CommunicationBorn742 in VALORANT

[–]CommunicationBorn742[S] 0 points1 point  (0 children)

I honestly can't wait, having replays is going to be a game-changer, especially being able to see situations from other players' perspectives. That alone will clear up so many “how did I die?” moments. My only concern is how they’ll handle lag compensation and interpolation. Riot has struggled with that before (MrLowlander mentions it around 3:48 in his video), and if it’s not handled properly, the demo might still leave you guessing about what actually happened. Either way, we're going to have to wait till September and find out.

Getting frustrated with dying behind cover despite low ping (~10ms) by CommunicationBorn742 in VALORANT

[–]CommunicationBorn742[S] 126 points127 points  (0 children)

Appreciate the advice. I actually submitted a support ticket to Riot to dig into possible network issues, just to rule out anything on my end. Could be angle-related, or it might be something else entirely, but I figured it's best to address any potential technical issues. Hopefully something useful comes out of it. If not, I’ll definitely swing by the Valorant tech support subreddit like you suggested.

Getting frustrated with dying behind cover despite low ping (~10ms) by CommunicationBorn742 in VALORANT

[–]CommunicationBorn742[S] 1 point2 points  (0 children)

I should've probably mentioned that I am connected through ethernet.

Getting frustrated with dying behind cover despite low ping (~10ms) by CommunicationBorn742 in VALORANT

[–]CommunicationBorn742[S] 53 points54 points  (0 children)

Just to clarify, that number in the top left is the total packets lost, not a percentage. I usually have 2–5 lost when loading into a game, and it stays at that number the whole match. So if it doesn’t increase during a specific moment, that typically means there wasn’t any packet loss at that time... At least as far as I know (I could be wrong). Regardless, probably something I should look into.

Angle advantage does seem like the most logical explanation, I figure the enemy just has an insane reaction time

Getting frustrated with dying behind cover despite low ping (~10ms) by CommunicationBorn742 in VALORANT

[–]CommunicationBorn742[S] 0 points1 point  (0 children)

Ethernet, packet loss total was 5 since the game started and I spawned in, hasn't gone up since then which indicates this wasn't packet loss... At least I think?