{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
1/6/2015 3:15:14 AM
1
If you haven't done so already, I strongly recommend reading this thread for possible solutions to your issue. I hope this helps!
http://www.bungie.net/en/Forum/Post/86667001/0/0
English
-
None of which solves anyone's problem. The culprit has been mentioned several times, if you play a different game and try to play Destiny, you get marionberry errors until you "quit" the game. Then you log back in and you do a download... EVERY time. If you play Destiny, then log out and later come back to DESTINY, no errors. But if you play a different game between Destiny sessions, you get errors. It's not on the players end, this is clearly on Bungies end.
