F5F Stay Refreshed Power Users Networks Have you noticed consistently late packets while gaming?

Have you noticed consistently late packets while gaming?

Have you noticed consistently late packets while gaming?

9
992x
Senior Member
506
03-19-2016, 05:43 AM
#1
I've been struggling a lot trying to get this working, always missing packets, tested both Wi-Fi and wired connections, updated every driver I could find, even tried on my phone, but it's still slow no matter what.
https://imgur.com/a/xm7YgC3
https://imgur.com/mFyx5bf
https://imgur.com/OoTALCY
https://imgur.com/9zeLASf
Occasionally it works sometimes.
https://imgur.com/a/yaDlkPr
I don't see any issues with browsing the web or watching videos, except when I'm playing games.
Internet speeds are around 950 Mbps download and 220 Mbps upload (fiber).
I have an Asus-AX53U and I live in an apartment block, if that affects it.
9
992x
03-19-2016, 05:43 AM #1

I've been struggling a lot trying to get this working, always missing packets, tested both Wi-Fi and wired connections, updated every driver I could find, even tried on my phone, but it's still slow no matter what.
https://imgur.com/a/xm7YgC3
https://imgur.com/mFyx5bf
https://imgur.com/OoTALCY
https://imgur.com/9zeLASf
Occasionally it works sometimes.
https://imgur.com/a/yaDlkPr
I don't see any issues with browsing the web or watching videos, except when I'm playing games.
Internet speeds are around 950 Mbps download and 220 Mbps upload (fiber).
I have an Asus-AX53U and I live in an apartment block, if that affects it.

1
11_JOEL_11
Member
247
03-20-2016, 08:24 AM
#2
Partially this appears as if you are relying on a tool that highlights some problem, and you immediately attribute it as the reason for your game difficulties.
It’s quite absurd to claim a packet arriving 60ms when it should be 40ms; such delays will impact your performance.
Adjusting the acceptable delay to 200ms should eliminate most late packets.
Your actual jitter—the main factor for smooth gameplay—is impressively low.
Current games are sufficiently advanced to calculate the time needed for data to travel from the server to your PC and anticipate how the game will appear on the server when your computer receives it.
They transmit data with this predicted state in mind.
If your average latency to the server is around 200ms, the results will be disappointing.
Your current average is only 40ms.
Recent test outcomes reveal significant packet loss.
This definitely poses a risk for gameplay issues.
Ensure you’re always connected via Ethernet.
Wifi can be affected by interference from nearby devices.
It’s challenging to maintain a steady ping to 8.8.8.8 in the background while playing.
Check if packet loss occurs during gameplay problems.
If you don’t notice loss, other game settings might be the culprit.
Shooter titles often exaggerate network issues, suggesting poor ping times, but what’s really happening is the game becomes unresponsive during rendering and then requests ping data.
They shift responsibility for delays onto the network, even though the data was consistently present waiting to be processed.
You need to exercise caution when using tools and relying on in-game statistics to confirm their validity.
1
11_JOEL_11
03-20-2016, 08:24 AM #2

Partially this appears as if you are relying on a tool that highlights some problem, and you immediately attribute it as the reason for your game difficulties.
It’s quite absurd to claim a packet arriving 60ms when it should be 40ms; such delays will impact your performance.
Adjusting the acceptable delay to 200ms should eliminate most late packets.
Your actual jitter—the main factor for smooth gameplay—is impressively low.
Current games are sufficiently advanced to calculate the time needed for data to travel from the server to your PC and anticipate how the game will appear on the server when your computer receives it.
They transmit data with this predicted state in mind.
If your average latency to the server is around 200ms, the results will be disappointing.
Your current average is only 40ms.
Recent test outcomes reveal significant packet loss.
This definitely poses a risk for gameplay issues.
Ensure you’re always connected via Ethernet.
Wifi can be affected by interference from nearby devices.
It’s challenging to maintain a steady ping to 8.8.8.8 in the background while playing.
Check if packet loss occurs during gameplay problems.
If you don’t notice loss, other game settings might be the culprit.
Shooter titles often exaggerate network issues, suggesting poor ping times, but what’s really happening is the game becomes unresponsive during rendering and then requests ping data.
They shift responsibility for delays onto the network, even though the data was consistently present waiting to be processed.
You need to exercise caution when using tools and relying on in-game statistics to confirm their validity.

J
Ject09
Junior Member
11
03-20-2016, 11:49 AM
#3
Performing a traceroute to the server reveals approximately 20 hops, with some potentially causing minor delays. The only paths affecting performance are from your PC to the router and from the router to your ISP, both typically under 1ms. ICMP pings are treated as the highest priority by most networks; ISPs along the route may discard them if traffic is heavy, only forwarding them once other packets have cleared within acceptable limits. This behavior introduces latency and packet loss during pings (12.6% remains significant, making it hard to pinpoint the exact drop point). Traceroute can help visualize which hop is causing issues. Sending standard game data packets that the server consistently responds to offers a genuine test of connectivity, though it also adds extra delay since it traverses the full application stack instead of just the network layer.
J
Ject09
03-20-2016, 11:49 AM #3

Performing a traceroute to the server reveals approximately 20 hops, with some potentially causing minor delays. The only paths affecting performance are from your PC to the router and from the router to your ISP, both typically under 1ms. ICMP pings are treated as the highest priority by most networks; ISPs along the route may discard them if traffic is heavy, only forwarding them once other packets have cleared within acceptable limits. This behavior introduces latency and packet loss during pings (12.6% remains significant, making it hard to pinpoint the exact drop point). Traceroute can help visualize which hop is causing issues. Sending standard game data packets that the server consistently responds to offers a genuine test of connectivity, though it also adds extra delay since it traverses the full application stack instead of just the network layer.