{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
This thread is inspired by another: view original post
3/28/2020 1:32:00 AM
12
Newt and Watercress
Newt and Watercress AGAIN. Been happening for three days now. No cross save. Router reset, port forwarding checked and redone, cache cleared....I’ve done everything you outline in your worthless network troubleshooting guide and my problems still persist. Obviously this problem is well beyond your technical expertise. Maybe it’s time to find a new partner that has the technical depth to help you.
-
2 RepliesHi there, Thanks for reaching out. We're currently investigating players receiving WATERCRESS errors.
-
Sam here, tried all the normal things and no luck. Fingers crossed one os these posts will get a positive response from bungie...
-
4 RepliesFor two weeks now. NEWT & WATERCRESS
-
I have had the same issue since the reset this week. They know about the issue and are investigating it so since they are in isolation and don't have access to their proper tools we might have to wait a little while unfortunately.
-
Same here Started last Week for me and has gotten worse. 9 out of ten tries I get the watercress code . On 10th if I return to orbit or change guardians I’ll finally get watercress and locked out Have reset router, uinstalled and reinstalled D2, posted my internet connections on Feedback and Twitter and have done 2 full shutdowns on my X Box One X I did see an article on Game Spot were in 2017 there was a similar problem BUT at the time there was no fix and no idea if they ever got one
-
1 ReplySame issue for alot of us. It's an Xbox and & account issue. But with Bungie working at home, they aren't concerned about it so we'll probably miss majority of the season.
-
Right there with you. My account seems to be screwed. Playing on my wife's account works fine.
-
2 RepliesSame problem here. XB1, NOT a New Light or Cross Save player. Destiny is virtually unplayable for me since Tuesday update - CONSTANT Newt and Watercress errors.
-
1 ReplySame problem here, Xbox One, 200MB/s wired connection, NOT Cross Save or New Light. After D2 being virtually unplayable since reset due to NEWT errors after every single strike, match, lost sector, planetary visit etc, I now can’t get on AT ALL. I pick my character, go to black screen for several minutes, then get WATERCRESS error. If I try to carry on, the game crashes completely with a continual ‘rrrrrrrrrrrrrrrr’ sound. If I launch again, same thing. I’m so desperate now that I’ve uninstalled everything and am spending 5-6 hours downloading it again when all I want to do is finally get into Iron Banner (haven’t been able to at all). PLEASE fix this Bungie, I appreciate things are difficult right now, I really do, but I’d very much like to escape into Destiny today. :(
-
Same since Sunday Our numbers seem to be growing, hopefully they will take it seriously soon.
-
I just stated with newt. If I try to go from destination to destination instead of destination-orbit-destination I get error code newt and a very long black screen.
-
1 ReplyHaving the same problem here.
