{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Bearbeitet von mowren:
12/3/2022 8:26:37 AM
4
[Solved] Changes and progress are not being saved, rolled back to previous state
I'm aware of the current server and match making issues and also ran in the WEASEL error several times. Already checked the different trouble shooting guides but those didn't help yet.
Additionally I ran into the problem, that everytime I log out or get disconnected, my characters are rolled back to the state they had in my previous play session after the servers became available again after maintenance (Saved state from December 1, ~3PM PST).
I tried shorter play session in case the WEASEL error means that there was an error with data synching. But logging out after playing without a WEASEL disconnect doesn't change the outcome.
Everytime I log back in:
- Changed loadouts are set back
- Quest progress isn't saved and completed and turned in bounties are incomplete again. Or aren't bought at all if they where bought since the last play session.
- Pickedup Loot isn't saved and not send to the postmaster (i.g. the number of Captain's Coins stays the same)
- Strangely, progress for the Sweet Business catalyst is actually saved between play sessions
-
Update December 3rd 00:00 am The rollback issues appears to be solved in my case. Progress like bounties and loot is being saved again, so the game appears to be playable again. The most important thing I noticed, is that my connection to the Bungie servers in Washington state isn't routed through the lasvegas1.level3.net node anymore. This was the case for the last few day when the issues appeared and I'm now routed through the zayo.com network. This just might be a coincidence, but Tier 1 routings usually don't change that easily for regular customers. No wonder all this is taking so long, if you had to change the static routes to the Bungie IP range network.
-
2 AntwortenHello mowren. Bungie is working on this issue right now. They just took the game offline temporarily to fix the issue. [b][url=https://twitter.com/BungieHelp/status/1598722332201488384]Bungie Help Tweet[/url][/b] [quote]The issue causing server, matchmaking, and egregious error codes has been identified and a fix is being implemented. Destiny 1 and 2 will be brought back online soon. Standby for updates.[/quote]
-
same here.. still..
-
Bearbeitet von mowren: 12/2/2022 4:54:00 PMI tested some more and I could narrow down the rollback trigger a little bit more. It actually happens when I'm disconnected with the WEASEL error and I can reliably cause it to happen. I was able to get into the game, to complete and turn in a bounty, quit the game, start it again and everything looked normal. Loadout and bounty progression was still there. Landing on a destination, walking around and quiting the game and login in again works normally. The progression was saved. But if I complete the Atrium lost sector in the EDZ with my Titan and try to leave, I reliably get a WEASEL error and get disconnected. Logging in after this disconnect rolls back my charakter to the state I meantioned in the opening post. No difference if I restart the game or just log in from the character screen. So everything I do in the game before a disconnect gets lost.
