{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Sekuiya:
6/13/2020 1:49:04 AM
1
A lot of Weasel error codes
This is new for this season. The platform is PC
In the previous season I was able to stay in the Tower for more than 2 hours and watch the Almighty explode.
This season I can barely stay 10 minutes in the Tower before flashing "Contacting Destiny 2 servers" warnings start flashing on screen. Sometimes it is able to re-establish the connection, but most of the time I'm thrown to the Title Screen after a "weasel" error.
This same pattern also happens in the Crucible. It starts fine, but the experience gradually degrades. Respawns start taking longer (aka more than "Respawning in 0"), then "Contacting Destiny 2 Servers" start popping and then... "weasel".
Oddly enough, [u]the Tower and Crucible are the only places where this phenomenon happens[/u]. Been able to play the Contact event on Io just fine, spent some time on Mars, did some solo quests, strikes also fine and Gambit Prime was fine too. Haven't tried Raids yet.
I suspect that it might have to do with my low upload bandwidth, which is just 1Mbps.
But having in mind everything was fine in the previous season, I'm guessing something changed in this season and the upstream requirements must have gone up for some reason.
Is there any information regarding this type of situation or some setting that I can change to lower Destiny's upload needs?
-
Bump. Just wanted to inform that this situation is still reoccurring. It's a little frustrating, especially this week since the Arrival weeklies are all based on Crucible. While I usually have enough time to do what I need to do in the Tower, Crucible is a whole other beast. I'm usually able to play the first half of the match just fine but it only gets worse after that and, for some ironic reason, seems that when the match is almost ending is when I get "weasel"ed out of the game. Sometimes, the game gives me a chance and leaves me with a "bee" code, allowing me to reconnect to the match, ( Sidenote: Rejoining the match in that way and having all your score reset, not cool. ) but usually, when that happens, a "weasel" isn't that far off. Although, when at the end of match, it's just enough to be able to pull through. Anyway, frustrating as hell this situation. At least PvE still works just fine, so at least I have that.
