{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
1/15/2021 7:21:09 PM
2
Network error only during PvP?
Hello, two weeks ago, I got restricted from PvP due to supposed connection/network errors. I made sure to double check all my connection settings, and I had no issues doing raids/strikes while I waited for my restriction to get lifted (since I read I could not appeal a temporary restriction). This morning, jumped back into Gambit, and on my third match, got a beaver error. I triple checked my connection settings (UPnP enabled, NAT open, ~15 ping, <5% packet loss).
Are beaver/network codes limited to PvP? Again, I don't have any network problems doing PvE raids/strikes. I want to play Gambit/Crucible with friends but I'm scared if I get any more error codes that I'll be restricted again and for a longer period. I don't have the option to switch to a wired connection.
-
Edited by Crisidelm: 1/15/2021 8:06:10 PMThat packet loss percentage is bad, it should be between 0 to 1% max (and even a 1% will give you problems).
-
pvp does typically place a higher load on your connection due to the increase in players. I would recommend fixing the packet loss as 5% is very high for destiny 2, it should be under 1%
