+1
I too am experiencing this issue. I decided to log out and hop back in the queue since I couldn't do anything else.
Unfortunately, because we can not launch story missions from the Director, I found that I was blocked from progressing since any attempt to land at the first destination public zone invariably results in a CURRANT or CACAO error. I had tried about 30 times in a row, and I figured that was sufficient.
* Even after passing through queue, I find my experience plagued with ATTENTION pop-ups, indicating connection issues, and then- again- a CACAO or CURRANT error every single attempt to land at the destination spot.
** It seems like the game will permit a landing and play if the zone I'm attempting to land in has an available, empty instance. In that case, I can land just fine (e.g. the EDZ patrol zone) and do things in the local area. But, if I attempt to head into another area I am presented with an infinite load screen (or long enough that I tried fast traveling instead and was booted with a CURRANT error). While in the local area nobody else loads in either - it remains a solo instance but otherwise functions normally.
English
-
This is my experience exactly. Sad to admit how much time I spent discovering all this.
-
It's just so sad because I want to enjoy the story, but I get CURRANT as I finish a mission and miss a cut scene... Then I get a banner across my screen with I take a break to the Tower that says "Please return to the Pale Heart because this story is supposed to be played end-to-end". LMAO Like what?! The audacity. And THEN I cannot even load into the Pale Heart because it's back to back to back to back to back CURRANT errors