{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by toneDef Weary:
4/2/2020 5:36:19 PM
9
Bump for later info.
Edit - Going to add what I've been able to glean so far.
[quote]Some things that seem to remain constant.
- This seems to be affecting XB accounts only, from what I can see.
- A user only has issue with a specific account. This account has issue whether used by the account holder, or by a friend in a different region.
- The same user doesn't have issue in the same environment on a different account.
- The same user(if cross-save is active) doesn't have issue using that account on a different platform.[/quote]
English
-
t happens the same to me. For about three weeks the error "watercress" has not allowed me to start a session with any of my three characters. Apart from this error, the "newt" appears. On the other hand my girl enters with her characters and the mentioned errors do not appear to her. This, then, very clearly that the problem is in the bungie servers, it is not an internet connection problem. Even if I try to enter from another console with my character the same errors appear again.
-
I just hope I haven't been banned for some reason. If you check all my stuff I'm a average player and I'm just curious if the newt and Seacress issue is because I was banned. Just got me curious due to the amount of people who are getting banned recently.
-
Edited by toneDef Weary: 4/2/2020 6:18:09 PMUnlikely. Those that have been banned would get a splash screen stating something along the lines of "Not so fast...". The fact that they have, at the very least, acknowledged that it is an issue they are investigating(even if just a forum reply), tells me that you shouldn't have anything to worry about. I'll be surprised if they don't actually address it in tonight's TWAB. Seems like a prevalent enough issue that they should, at the very least, address in their official weekly letter to the players. Edit - Punctuation Edit 2 - They've also now added several error codes as well as crashing on PS and Steam to the Known Issues thread.
-
Do you know what could cause such an issue? Like is it us at home doing something, internet connection, or is it something completely on Destiny’s side?
-
Unfortunately, I have absolutely no idea. It's unlikely a user issue scenario. Based on a best guess, it seems to me like something in MS's networking is taking issue with something in Bungie's networking, and only with certain users and specifically on the XB platform. Other than that, I'm at a loss as to the why.
-
Has anyone else since this all started also had their custom gamerpic revert back to a past generic gamerpic and cant update or change it? these two things coincided at the exact same time for me. literally after my first watercress and newt boot haven't been able to load past character select and gamerpic reverted back to a previous generic pic. it is strange that likewise on my alt I can load perfectly into the game, but on my main I cannot. hope they mention this in TWAB. Wondering if it is an xbox to Destiny server issue. But why would it only effect some accounts?
-
I noticed this. Also my ship changed, old weapons equipped that were in vault, armor changed, and sparrow different. This happened just before my first newt disconnect, then watercress started when trying to log back in
-
I probably have same issues. On the black screen after character select I was starting to hear stuff being put in my inventory but I could not see it as the screen was black. Maby bungie was trying to fix the issue by role back without advising the user but failed to fix it. This just my opinion.
-
Edited by toneDef Weary: 4/2/2020 10:44:06 PM[quote]Has anyone else since this all started also had their custom gamerpic revert back to a past generic gamerpic and cant update or change it? these two things coincided at the exact same time for me.[/quote] That's an odd one. You would be the first that I've seen mention that, but I'll make note of it in my mental lockbox, to keep an eye out for that. [quote]it is strange that likewise on my alt I can load perfectly into the game, but on my main I cannot.[/quote] Even stranger when you add in that(assuming this is your main with cross-save active) I'd put money on you being able to play on PS or Steam with no issue. [quote]Wondering if it is an xbox to Destiny server issue. But why would it only effect some accounts?[/quote] My guess is that it's something between MS's and Bungie's networking that is causing an issue on some accounts, but what it is, I have no idea. As to the question in that quote, that is definitely the question of the hour. Hopefully they do address it in the TWAB, but I really don't know what else they can say but "we're looking into it". I saw that they did at least add it to the known issues thread now. Edit - While they did note it in the known issues part of the TWAB, that was the extent of it. Apparently no solution yet.
