{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/3/2020 9:53:47 AM
1
Watercress, Newt & Fireteam
Loaded game chose Hunter Black Screen 5mins
"Could not connect to Destiny servers Watercress" error code.
Loaded game chose Titan no problem landed tower collected gunsmith bounties back to orbit.
Chose Tangled Shore. Ship now placed in lower bottom os screen.
Similar configuration as seen when two other ships present.
1.37secs later "Unable to find a match for your Fireteam please try again" error code Newt.
"Could not connect to Destiny servers error code watercress"
From my experiences it would seem the game thinks I should have more players with me and is waiting for them to appear hence the orbit screen
I did try my Warlock and got all the way from load to Tower to the Shore and I played completing Gunsmith and Spiders daily bounties.
Going back to the Tower crashed the game again.
First time ever from day one of D1 I've ever had a problem like this that stopped me from playing completely.
-
They are aware that there is an increase of Watercress error messages. They’ve relayed some information to other users earlier today, stating that it had to do with too many play sessions open on an account. They confirmed that this only seems to be affecting XBOX players. If you have cross-save enabled and you have another platform, you can continue playing there. Otherwise, they may have a fix in the works and should have more information on it when they’re ready to discuss it.
