{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Editado por BNGHelp0:
4/15/2018 3:49:22 PM
22
Error codes: CABBAGE and CURRANT
Hello!
I've been playing Destiny 2 since release with no problems except for minor hiccups. Last night I got a couple server errors, but my friends had one of those too so I didn't worry much.
Today, the game was near unplayable. I did have a centipede error too, and that prompted me to follow the upnp steps and nat configuration stuff. Did it all on my pc, started getting cabbage and currant. Slightly better connectivity, lets me at least play for a bit before disconnecting, but getting errors eventually.
My router isn't a thompson or technicolor either, as far as I know the brand's mitrastar.
Any reason why this might be happening? Any other steps I should follow? Didn't do the redirect step in rooting (nat thing) because I don't really know how so that might be it.
-
4 RespuestasEditado por mikethor007: 4/18/2018 12:42:34 AMSame thing here. Problems seem to have started friday or saturday. PS4 system. Brazil. VIVO ISP (which is a company related to movistar). Cabbage, lettuce, coconut and centipede here, at the very least. I can at most get into the tower. Can't join other player's sessions. Can't start a matchmade strike. I spawn into the world, see no one whatsoever for a time (no enemies/npcs/players) and then get booted with the error. The thing here is that this particular problem might not be easily solvable on bungie's side. Or our side either. It's starting to look like some router along the way on the internet is interfering with our games badly. Might be Movistar dropping/filtering/blocking certain stuff that passes through their network. And for me it's not only D2 that's affected. I'm getting tons of errors in Monster Hunter World too.
