In Destiny 2, there are issues with the Steam transfer and the new cross-save feature. The launch was anything but smooth.
“Never play on Patch Day” is an old gamer wisdom that has often proven true for Destiny in the past. And in hindsight, many Guardians would have liked to have adhered to this on the day of the cross-save launch, as it went quite bumpy and was unsuccessful for most players.
This is what happened at the start of cross-save: Last night, on August 21st at 7 PM, the long-awaited cross-save for Destiny 2 was initiated.
However, in the forums, Guardians immediately reported in droves that something was wrong and the cross-save process was not functioning properly. Bungie promptly responded and announced on Twitter that maintenance for cross-save had to be conducted on Bungie.net. The feature is expected to start 2.5 hours later than announced.
After these 2.5 hours, Bungie tweeted again excitedly that the maintenance needed to be extended. There were numerous “500” error messages, and account authentication was problematic.
Around midnight our time, Weasel and Baboon errors were reported in Destiny 1 and Destiny 2 – this issue has since been resolved.
Just a few hours ago, the developers tweeted that the maintenance was now complete, but they were still chasing Olive errors and advised players to restart the Destiny 2 app to avoid potential issues.
Is everything working with cross-save now?
This is what the Guardians say: On Twitter and in the forums, there are mixed user reports. Some write that the cross-save link finally worked, while others report that it still doesn’t work for them.
These are the known issues: In the help forum, Bungie lists some problems they are still investigating in connection with cross-save:
- “Something weird happened” – This error message is sometimes displayed when trying to activate cross-save.
- There are issues with account authentication.
- “500” errors occur on Bungie.net.
What is cross-save? Cross-save refers to the feature that allows you to share a save file between different platforms on which you play Destiny 2. We have a guide for cross-save here for you.
What is the problem with the Steam transfer?
This is what it’s about: Since August 20th, you can link your Battle.net account with your Steam account. This is a necessary step if you want to continue playing Destiny 2 on PC after October 1st.
These are the problems with Steam linking:
- If you want to link your account to Steam, the “Confirm” button cannot be pressed on mobile devices.
- The “Microsoft Edge” browser has issues during the linking process.
- Not all content licenses for Destiny 2 are displayed.
This last issue caused a lot of commotion. Bungie writes that they received multiple reports that not all licenses are displayed correctly.
They assure, however, that all content licenses in your possession (i.e., purchased DLCs) will later be transferred to Steam. You can ignore the warning.
For more information on the Steam transfer of Destiny 2, read it here.
A Twitter user summarizes the current problems as follows: “And that’s the reason they are bringing cross-save a month before the release [of Shadowkeep]” – and Bungie agrees with him:
Bottom line: If you are still encountering issues with cross-save or the Steam transfer, you know that you are not alone.
Did you try cross-save yesterday without success – or even successfully?
