Star Citizen Invalid Location ID: As of this writing, there is no estimated time of arrival (ETA). But our teams are working to resolve issue as quickly as safely as they can. We ask for your patience because we are aware how frustrating this is for everyone involved.
Here are a few problems and flaws with Star Citizen Alpha 3.18.x that we are aware of. The Issue Council’s reports on the issues are much valued as we continue to actively endeavour to properly address them.
The list of issues that have been noticed during testing but have not yet been duplicated. For which our teams lack sufficient data to launch an investigation is provided below. Players are urged to gather data and post it on the Issue Council if they run into any of these circumstances.
Read Also: How to Fix Star Citizen 30018 Error
Read Also: Star Citizen Entitlement Processing- How to Fix
It’s possible for some harvestable deposits to become invisible. Cause collisions, or to stop being accessible for mining, scanning, and salvage. A player could run into an error saying “Something went wrong (Error code: 20)” when trying to start a refinery job. On missions, Combat Service Beacon progress and/or rating can vary.
Player Unstowed:
We are aware of and are investigating the reasons of the 19k and other login-related problems. Although this looks to be caused by an extremely high server load at the moment. It may take some time for things to get back to normal. Our teams are actively looking into the problem. Will have more information when it becomes available.
This is the first stage of growing pains as all of our players get used to the new features added in the 3.18 patch because there have been several modifications made to how the game handles specific situations.
There have been reports of players being able to log in after obtaining these issues. However it can take a while. If you haven’t already, kindly provide details about your encounters with these errors in pertinent Issue Council reports, including, if applicable, the steps you took to successfully log in.
Error 60015:
Players that experience this mistake are given an error notice that states that the notification window is not displaying the correct information. “Requested location instance is full or not available,” should be the correct text.
According to a few reports, the 60015 problem may be fixed or at the very least allow for a login after joining a friend. If you haven’t already, kindly provide details about your encounters with these errors in pertinent Issue Council reports. Including, if applicable, the steps you took to successfully log in.
Error 40014:
The 40014 problem has been reported by more players. Which is bad because it can prohibit them from starting the game. Although some players have reportedly been able to access Arena Commander, this does not appear to be true in all cases of the problem.
We are actively tracking this issue, trying to find a solution, and gathering further details, including any potential workarounds that may have been discovered. Please assist us if you run into this issue by contributing your information to this Issue Council report: STARC-62473
There are times when using an ASOP terminal to fetch a ship for usage is impossible because the screen may become blank or otherwise become unusable. We are looking into a fix for this and will make an effort to get a hotfix as soon as we can.
In the meanwhile, if you come across this, kindly gather details about the occurrence and let us know about it on the Problem Council. To promptly address this, it is essential that we have access to as much data and information as possible.
Read Also:
Star Citizen 3.18.1 Patch Note Rewards and More
Star Citizen Fleet Manager Black Screen Error – Fix Now
