CrossSave Active Characters not appearing on Steam despite verified setup
My Cross Save setup appears to be configured correctly on Bungie.net:
Cross Save is active.
- My PlayStation account is selected as the active character set.
- My Steam account is linked correctly.
The Cross Save page shows my [b]PlayStation [/b]characters as the [b]active characters[/b].
I've verified the following:
1. Logging into Bungie.net through [b]PlayStation [/b]shows the expected CrossSave setup.
2. Logging into Bungie.net through [b]Steam [/b]shows the exact same Bungie account and Cross Save setup.
3. When launched through Steam, the in-game Bungie Name and Bungie ID shown in the character selection screen [b]match [/b]the expected Bungie account.
4. Expected active characters are still there on PlayStation.
However, when I launch Destiny 2 through Steam, instead of seeing my PlayStation-based active characters, I see a completely different character: a single Exo Hunter that does not belong to my PlayStation account. It may be a remnant from Steam from before the accounts were linked, it is certainly not at all part of the PlayStation characters.
Additional details:
- This is not a new Cross Save setup. It has been configured this way for a long time.
- The issue persists after fully logging out of Steam and logging back in. I have relaunched the game many times.
In sum, Bungie.net and the game both appear to recognize the correct Bungie account, but Steam is still loading the wrong character(s).
Your role as a moderator enables you immediately ban this user from messaging (bypassing the report queue) if you select a punishment.
7 Day Ban
7 Day Ban
30 Day Ban
Permanent Ban
This site uses cookies to provide you with the best possible user experience. By clicking 'Accept', you agree to the policies documented at Cookie Policy and Privacy Policy.
Accept
This site uses cookies to provide you with the best possible user experience. By continuing to use this site, you agree to the policies documented at Cookie Policy and Privacy Policy.
close
Our policies have recently changed. By clicking 'Accept', you agree to the updated policies documented at Cookie Policy and Privacy Policy.
Accept
Our policies have recently changed. By continuing to use this site, you agree to the updated policies documented at Cookie Policy and Privacy Policy.