{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/3/2022 11:44:25 AM
2
Severe Lag
Anyone able to help me trouble shoot?
I am getting really bad lag where I can't see capture points being captured in crucible, players and PVE adds are severely rubber banding. For example the barricades in the first phase of the Fallen S.A.B.E.R. strike do not spawn until after the warmind is captured.
Speedtest.net connection is great, no issues I can tell with my ISP getting the normal 90Mbps down and 30Mbps up
No packet loss identified
Issues occur on both wired and wireless connection.
I have tested to see and I have had no issues with Apex, Overwatch, TF2
-tried both UPNP & Port Forwarding (seperatly ofc) Using the guide [url=https://help.bungie.net/hc/en-us/articles/360049496751]here[/url]
-tried disabling the windows firewall.
-all caches cleared
-no windows updates
-no other devices on network & not streaming
-game files verifed, even tried a clean install.
Anyone got any ideas on what to try next?
-
https://youtu.be/qtklis8Ff50 Video of said lag
-
1 ReplyEdited by haps: 7/6/2022 10:48:44 AMMicrosoft Windows [Version 10.0.22000.739] (c) Microsoft Corporation. All rights reserved. C:\Users\***>ping 8.8.8.8 Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=7ms TTL=118 Reply from 8.8.8.8: bytes=32 time=7ms TTL=118 Reply from 8.8.8.8: bytes=32 time=7ms TTL=118 Reply from 8.8.8.8: bytes=32 time=7ms TTL=118 Ping statistics for 8.8.8.8: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 7ms, Average = 7ms C:\Users\***>ping bungie.net Pinging bungie.net [104.20.29.30] with 32 bytes of data: Reply from 104.20.29.30: bytes=32 time=16ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=8ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Ping statistics for 104.20.29.30: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 16ms, Average = 9ms C:\Users\***>ping bungie.net Pinging bungie.net [104.20.29.30] with 32 bytes of data: Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=6ms TTL=58 Ping statistics for 104.20.29.30: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 7ms, Average = 6ms C:\Users\***>ping bungie.net -t Pinging bungie.net [104.20.29.30] with 32 bytes of data: Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=6ms TTL=58 Reply from 104.20.29.30: bytes=32 time=12ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=8ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58 Reply from 104.20.29.30: bytes=32 time=6ms TTL=58 Reply from 104.20.29.30: bytes=32 time=7ms TTL=58
