Below are some of the issues and bugs that we are aware of within Star Citizen Alpha 3.19.x. We are still actively working to address these issues fully and Issue Council reports on the problems are greatly appreciated.
Also be sure to check the RSI Status page for updates on any service issues that have been noted:
Quick Jump Links:
Newer additions to this list and any especially impactful ones are added at the top, with longer standing issues towards the bottom.
- Newly Acquired Items May Be Lost on Logout If Not Placed In Inventory
- Ship Persistence and Vanishing Ships
- "Invalid Buy-Back SKU" Error in the RSI Pledge Store
- No Atmosphere in Parts of Bajini Point
- ARC-L4 Refinery Has no Elevator Access
- Client Crash around Lorville
- Player Ships in "Unknown" Status After a Game Crash
- Drake Cutlass Hatches are Not Working
- FieldLite Underbarrel Attachments are Missing
- Landing Services Issues
- Error 19003 and 19004, and "player unstowed"
- Error 60015
- Error 40014
- Error 15008/16008
- Issues with Shuttles, Trains, Trams, and Elevators
- Party Members Become Invisible
- Unexpected Collisions when Flying Near Other Ships
- Invisible Cargo
- Error 0 / Code 0
- Ground Vehicles and Initial Spawn Points
- Game/Launcher Issues after a Server Crash
- Running and Installed Application Conflicts
- Hangar Module Not Available
- Select System Menu is Empty
- mobiGlas is Missing or Non-Functional
- Mouse Cursor is Flickering in the mobiGlas
- Loadout Service Issues
Newly Acquired Items May Be Lost on Logout If Not Placed In Inventory
We are tracking and investigating a fix for an issue with player inventories, ships, and items that have been recently acquired during a play session. Certain items, such as those looted from out in the verse, can sometimes not be properly saved to Long-Term Persistence (LTP) which can result in any new additions to a player's inventory simply seeming to vanish on their next login.
This seems to occur most frequently when a newly acquired item isn't properly stowed in a location or ship-based inventory or a logout occurs away from a landing zone or a bed.
We are working on a fix for this and will be attempting to get it resolved as soon as possible. To prevent item loss until the fix can be deployed, make sure that any newly acquired items/equipment are retrieved and stowed in a location or ship-based inventory before you logout.
Basically, moving new items from one inventory location to a different inventory should ensure that LTP can work to preserve your hard work in the verse so you can pick up where you left off when you return.
Please note: Ship components and FPS items acquired prior to the patch are being reported missing in 3.19.0. If they were not placed in inventory before 3.19.0, these items are lost.
Ship Persistence and Vanishing Ships
We have identified and are also working on a fix for some issues with ships, similar to items as noted above. Newly acquired ships are being observed to vanish if they have not been properly delivered and stowed before logout. Some specifics for this issue:
- Filing an insurance claim will result in the loss of your ship or vehicle unless you retrieve and store it before logging out of the game.
- New ships purchased with aUEC will need to be delivered and then stowed to ensure it remains available on next login.
- Rentals need to be delivered and stowed or they will not be available on next login, regardless of the time left on the rental.
Basically, to ensure you don't lose a new ship, however it was acquired, make sure you deliver and stow it at least once before you logout of the game.
This is obviously a hugely frustrating issue and our teams are working on a fix for this as quickly as they can.
"Invalid Buy-Back SKU" Error in the RSI Pledge Store
Our teams have identified the cause of an error and are working on a fix for an issue that may happen with the RSI Pledge Store. The symptoms will be receiving an error that says "Invalid Buy-Back SKU" when attempting to add anything to your cart. Typically this occurs after a player has added and then removed a buy-back pledge from their cart.
We are working to get this resolved as quickly as possible, but if you encounter this error it can be resolved by signing out of your RSI Account and then logging back in.
No Atmosphere in Parts of Bajini Point
When walking about Bajini Point, specifically one of the walkways in Sec Port B, players may encounter a section that has no atmosphere. If the player is not wearing a helmet, this means they will suffocate and die if they enter the area.
Until a fix can be put in to remedy this, we recommend wearing proper safety equipment (i.e. your helmet) when walking about or arriving at this location.
ARC-L4 Refinery Has no Elevator Access
Regardless of how you, a player, arrived at the rest stop refinery area at ARC-L4, once inside this particular refinery location the elevator access panel is not accessible after entering. This means any players that enter will be stuck as there is no way to leave.
Unless you have a very specific reason for going to this specific refinery, we recommend heading to an alternative location for your refining needs.
If you still need to go to this refinery or arrived here and then found yourself stuck, to escape you will need to exit and relogin to the game.
Client Crash around Lorville
We have investigated reports and confirmed a game client crash that can occur in the Lorville area of the game. This is related to graphics issues and can be solved by updating your video card drivers.
Graphics cards typically come with software to help manage driver updates, but if for some reason you have decided not to use those, you will need to head to the website for your video card manufacturer and download/install the most recent driver update from there.
Player Ships in "Unknown" Status After a Game Crash
Should a player experience a game crash, usually with some flavor of a 30000 error, any ships or vehicles that were in use (i.e. not stowed), will show on ASOP terminals with "unknown" status. A fix for this is being worked on and will be implemented as soon as possible.
If you find your ship in such a state, the only solution is to file a claim on it to recover it for use again.
Drake Cutlass Hatches are Not Working
Specifically with regards to the Cutlass Red and Blue, the ship can enter a state where the hatch on the ship will not function. More often than not this occurs when multiple players are trying to use or access the ship. A fix for this is already being planned for a future patch.
To get around this, players can still access the Cutlass via the ramp.
FieldLite Underbarrel Attachments are Missing
Players have reported that the yellow, red, and blue FieldLite attachments are missing from their inventory on login. At the moment, there is no solution remedy this issue, however the proper teams are aware and it will be resolved in a future patch.
Landing Services Issues
We have been made aware of an issue players are encountering that is causing landing services at various stations and settlements to not function. As this is a detrimental bug that highly impacts game play, we would greatly appreciate submitting your findings to the Issue Council, as this means the developers can collect the data and work on a solution.
The relevant report can be found here: STARC-53655.
As a potential workaround, you can try landing your ship near the station and entering the terminal on foot. If you're at a Space Station you will need to hover your ship just outside of the restricted area to avoid impounding, this means you should hopefully be able to exit your ship and collect supplies from the station.
Error 19003 and 19004, and "player unstowed"
We are aware of and currently tracking the 19k and other login related errors and the causes behind them. Our teams are actively investigating the cause and will have more information when available, but currently this appears to be caused due to extreme server load and so it may take some time for things to clear up.
A great deal of changes were made to the way the game handles certain things and this is part one of growing pains as all our players come to see the new things added in the 3.18 patch.
We have had reports of players able to get in after receiving these errors but it may take several hours for that to happen. If you haven't already, please add information about your experience with these errors to relevant Issue Council reports, including what you have attempted that has allowed you to login, if applicable.
The error message that players receive after encountering this error is not showing the proper information in the notification window. The proper text should say "Requested location instance is full or not available."
Additionally, there have been a few reports that joining a friend after seeing the 60015 error may resolve or at least allow for a login after. If you haven't already, please add information about your experience with these errors to relevant Issue Council reports, including what you have attempted that has allowed you to login, if applicable.
We have seen an increase of reports of players receiving the 40014 error, which can unfortunately prevent them from entering the game. There has been some mentions that some players have been able to access Arena Commander, but this does not seem to be consistent with all instances of the error.
We are actively tracking and looking for a solution to this and are seeking additional information, including any possible workarounds that have been found. If you encounter this error, please help us out by adding your information to this Issue Council report: STARC-62473
This error appears when there is a service outage or when there is trouble connecting to the login service. It is fairly common when our servers are under heavy traffic loads, such as after a major patch or during an event, and generally will be fixed with time.
There are also reports that some instances of this error are from Easy Anti-Cheat interaction and might be causing this error to appear. If you feel this might be the case, try updating your graphics drivers and uninstalling/re-installing the Epic Games Launcher (if you have it installed).
We have a more in-depth article to address this error here: Error Code 15008/16008
Issues with Shuttles, Trains, Trams, and Elevators
We have seen and verified reports for various issues with certain options for player transit, like trams, shuttles, and elevators. This can present itself from the tram or elevator flickering or appearing jittery to shuttles not arriving on time. While not common, there are also reports of players falling through the floor to their death unexpectedly.
A fix for many of these issues is planned for a future patch, but additional reports of issues to help document problems and locate new ones is always appreciated on the Issue Council.
Party Members Become Invisible
If players are together in a party are forced to respawn at the same time, reports are that some of the party members become unable to see each other or their ships. Should this occur for you and your party members, leaving the game instance for another or returning to the game menu to use party launch option again should resolve it.
Unexpected Collisions when Flying Near Other Ships
At certain times when flying in formation or in close proximity to another ship, it may appear that an invisible object was hit that will force your ship into another direction.
We are investigating the cause of this and expect a fix to be implemented in a future patch. In the meantime, maintain some distance between you and other ships to avoid unexpected and unexplained collisions and contribute information on this issue to the Issue Council.
After purchasing or otherwise acquiring cargo in some way, the cargo itself may not appear in the designated ship cargo hold. However, the cargo is indeed there, simply invisible and can still be transported and sold normally.
A fix for this is expected in a future patch.
Error 0 / Code 0
This is an issue related to Easy Anti-Cheat (EAC) and we are investigating the cause. In the meantime, to correct this, follow these steps:
- Delete the EAC folder located in the Roberts Space Industries\StarCitizen\LIVE folder.
- Fully close the RSI Launcher. Use the task bar and/or the task manager to ensure the process is killed if need be.
- Re-open the RSI Launcher
- Click the SETTINGS option
- Press the VERIFY button next to "Analyze game files".
Allow this process to finish. If this does not correct the issue, consider totally uninstalling the game and all related files for a fresh install to ensure all files are correct.
Ground Vehicles and Initial Spawn Points
If you own ground vehicles that have been acquired from the pledge store, selecting an initial spawn location that supports ground vehicles will ensure that you can access and claim them without troubles.
New Babbage is a good choice for this, if you are uncertain which starting locations support ground vehicles.
Game/Launcher Issues after a Server Crash
In the unfortunate event of a game server crash, players may encounter issues reconnecting to the game. This issue may present itself as an infinite loading screen or being unable to interact with the game menu.
If you encounter this issue, you will need to fully exit the game and restart to correct it.
Running and Installed Application Conflicts
There are cases where certain specific programs may conflict with the RSI Launcher or game client and prevent it from running properly. It is difficult to form a list, but if you are running into constant issues with consistently launching the game or persistent and pervasive game client crashes within the first five minutes of play, considering turning off other running programs and applications and trying again.
Though rare, simply having certain applications installed may also cause troubles, which is much harder to identify.
A recent such conflict our Tech Support Agents have identified is with Sonic Studio 3 / Sonic Studio Virtual Mixer which will need to be fully uninstalled for the RSI Launcher to properly function.
Hangar Module Not Available
As of Star Citizen Alpha patch 3.13.1a, the Hangar Module is currently disabled while we examine needed fixes for issues with the module.
There is currently no time frame for when it will return. Check the patch notes on Spectrum for updates on when it has returned.
Select System Menu is Empty
In rare cases the option to select a system to begin playing is totally missing from the game's main menu screen for entering the Persistent Universe. Should this occur, completely close both the game and the RSI Launcher and wait a few minutes before restarting the application. Ensure the tasks are completely ended in the Windows Task Manager as well.
Should the restart not work, a few players have reported that totally restarting their computer has helped.
If you encounter this, please consider adding your report to the Issue Council so we can work towards sorting out the root cause of the troubles.
mobiGlas is Missing or Non-Functional
We have continued to receive reports of this issue happening with the latest patch. Entering character customization and changing your character's gender, appearance, and eye color a few times may correct these issues. After changing your appearance, enter the Public Universe. If not resolved please try customizing again.
If your issue continues, please do the following steps before you repair your character:
- Login to your RSI account on the website.
- Report the issue and any details regarding what you were doing when it happened on the Issue Council.
- Attempt the workaround listed above.
- Head to this article to review what you will need to do: Character Repair
Mouse Cursor is Flickering in the mobiGlas
The problem prevents some ease of use of the mobiGlas as clicking will sometimes not function. This is due to a strange interaction from certain types of control peripherals, such as flight sticks.
We are actively looking for additional information and reports on this issue so should you experience it, please consider adding your report and experience, including any additional control peripherals you might be using, to an Issue Council report.
For now, if this occurs some players have reported that repeatedly clicking with the mouse can sometimes bypass the problem.
Loadout Service Issues
We are aware of and actively investigating an issue impacting some loadout services. Some commonly reported services issues may manifest through some of the following symptoms:
- Difficulties with proceeding on ship storage and retrieval, or an insurance claim, through the ASOP terminals
- Difficulties with completing shop purchases or commodity transactions
- Difficulties in accessing or saving changes through the Vehicle Loadout Manager on your mobiGlas
- Increased Inventory loading and adjustment times
- Increased Server Crash Recovery ship retrieval times
- Increased Character Repair completion times
Please note that a Character Repair will not resolve these issues. Our development team is working as fast as possible toward clearing up these microservice issues, but any additional reports you can provide through the Issue Council would help our developers tack down the root causes for these issues!
When you have a moment, consider heading to the Issue Council to add information to any current reports to help us track down the root cause of the problems.