*!*!*We are investigating an issue where some players are seeing a "login failed for unknown reason" error at the log-in screen.*!*!*
We are investigating a bug where some Gold Members may not have received their additional character slot -- details here (Will be fixed ASAP!).
UPDATE! We are also investigating reports of slow patching and are working on a resolution. For a better patch experience, please restart your launcher. It will pick up where it left off and should be faster to complete.
If you have purchased a Legacy or Starter Pack, please see this thread for instructions on how to claim your items in-game.
If you have additional questions about the Legacy or Starter pack, please read this FAQ.
i am doing a mission called secret order's entangled in the briars, i have done most of the mission but i can't beam down to the base due to a bird of prey stuck in the asteroid wall and i can't destroy it, please can you do anything
You don't actually have to delete the mission if you leave to work around a bug. If you keep the mission and just leave the mission map long enough for it to reset, you should lose less progress.
In general, missions are set up with a "wrapper" mission which sits in your journal and "open" missions which are based on the map the mission takes place on. Often each open mission completing will tick off a extra check mark on your wrapper mission objectives. When you leave a mission to exit to sector space, you will typically lose progress on the open mission and its matching objective, but you won't lose earlier progress. Most mission bugs can be resolved by just letting the current map reset and starting from there.
Being aware of this can mean that if you run into trouble on part 3 of a mission, and leave, you just start over on part 3 instead of going back to part 1.
You don't actually have to delete the mission if you leave to work around a bug. If you keep the mission and just leave the mission map long enough for it to reset, you should lose less progress.
In general, missions are set up with a "wrapper" mission which sits in your journal and "open" missions which are based on the map the mission takes place on. Often each open mission completing will tick off a extra check mark on your wrapper mission objectives. When you leave a mission to exit to sector space, you will typically lose progress on the open mission and its matching objective, but you won't lose earlier progress. Most mission bugs can be resolved by just letting the current map reset and starting from there.
Being aware of this can mean that if you run into trouble on part 3 of a mission, and leave, you just start over on part 3 instead of going back to part 1.
How can I get rid of "[Lt 1] Line in the Sand" ... a mission from the ST:O intro ... I'm now Cm 2 and I *still* have that mission in my Episode log.
We're looking into whether we can automatically remove that from everyone's mission trackers (if you're out of the tutorial), but for now please submit a GM ticket. We should be able to manually deal with that for you.
It is the Vulcan Ambassador mission where an Udine is disguised as a Vulcan Ambassador. I completed the mission and destroyed the Udine ship in orbit. Then I got a phone call and I talked to the phone. When I got back there was a red window message telling me that there is nobody in this system and I can warp out. I warped out but the mission still showed in progress although I had completed it. I warped in the same system and the map was reset. Is this is a bug or a mistake from my part? Namely should I leave the map when I complete the mission without delaying much?
Another problem was related to the Vulcan Sector Patrol - Bhea System. When I got there there were Orions but no shipyards. I destroyed all the Orion ships and left the map but the misson was shown as still in progress. I re-entered the system several times with no luck. Finally the map reset and this time there were both Orions and shipyards. I destroyed them all and this time the mission was listed as completed. Am I doing something wrong? Or is there a general instance synchronization bug in the game?