How to avoid the worst bugs in Star Citizen (as of v4.1.1)
A decent number of the 4.1.0 issues have been fixed/removed since the last list. The Pyro V quantum issue isn't new, but getting stranded out there is not fun, so I added it in. I also updated the ATLS teleport issue with a new possible workaround.
The first trick you'll need to learn is how to Server/Region Hop. Some of the worst bugs require just leaving the current server and going to a different one.
To force a server change you'll need to exit back to menu and change your region to something else.
Note: If you attempt to start the game in the same region, the game leans toward placing you in the server where you've been most recently.
Elevators
Don't press up against the door when waiting for an elevator to arrive, it might push you out of the station as it arrives and physicalizes.
Do not enter an elevator immediately, always wait for the doors to open and verify that the elevator is actually there.
There was only ever one exception to this at a particular Lagrange point station where an elevator would always open up to a black void, but crossing the wall of black would reveal that the elevator was actually there. 99% of the time this is not the case. If you're truly curious, just try to put half of your body over the line, if your body dips down a foot or two, there is no elevator.
Don't sprint into an elevator full of other players.
Particularly in some of the executive hangar locations, at worst you risk glitching your buddy into the station interior. At best, nothing happens or you only slightly injure someone else in the elevator.
To avoid falling out of your ship during quantum:
- Don't stand up immediately from your seat the second you enter quantum.
- Don't jump around like the floor is lava.
- Don't use the stairs on the Idris while it is in Quantum.
- Don't change armor/undersuit while in quantum (might be fixed in 4.1.1?).
If you're encountering frequent game crashes...
Check the information in this post here:
https://robertsspaceindustries.com/spectrum/community/SC/forum/51473/thread/crash-due-to-old-string-data
The game.log file can be found at the default install location:
C:\Program Files\Roberts Space Industries\Star Citizen\LIVE\Game.log
Open it up, then scroll all the way to the bottom, then scan through from bottom to top looking for any crash info.
If you're seeing out of memory errors and you only have 16GB of RAM, you'll want to increase your page file or upgrade your hardware so you have more RAM:
https://support.robertsspaceindustries.com/hc/en-us/articles/360000083387-Out-of-memory-errors-set-your-pagefile
Only use the ASOP terminals inside of your hangar to spawn your ship.
Sometimes the external ASOP terminals work, but there's a decent chance for the spawn order to be off/out of sync between your hangar, the elevator and your ship. This will cause you ship to be clipped partially into the hangar elevator floor and has a chance of destroying the ship as the hangar elevator moves into position.
https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-167618
If you collect a refinery job send the cargo to the station instead of to a ship.
Alternative workaround: store and then re-retrieve the ship to get the cargo to appear.
I have had to do this a few times in a row to get the cargo to finally appear (well I haven't had to do it more than 2 times in a row... Yet).
If you happen to be using a Hull-A for this, I would recommend extending the spindle first before storing the ship.
https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-112825
Workaround in 4.1.1 - Just collect the order to the station inventory instead.
Whenever warping around a planet ALWAYS be ready to cancel the warp by switching from NAV to SCM.
There is a rare bug where the warp path will take you through the planet. You will (almost always) die a fiery death from this.
Switching nav modes will immediately cancel the warp. You can also power off your ship with "U".
Note: While turning off your engines with "i" works when warping between planets... It does not work when warping to a ground location on a planet.
Don't jump between Orbital Markers (OMs) at Pyro V Green Gas Giant (or be extremely careful)
When choosing a Quantum Travel point around Pyro V, the orbital markers above the planet are all appearing as option, regardless of whether or not the planet itself is between you and said marker. Selecting one of these points will cause the quantum travel to go through the planet, which will destroy most ship components and stranding the ship and its passengers.
If you come across an invincible player, use a takedown move, then again while they're on the ground.
Some players may accidentally get bugged, other players have figured out how to consistently recreate the invincibility bug.
It's common to encounter them at executive hangars. The best way to handle them is to use take-down moves on them and then finish them off with another takedown move while they're unconscious.
if you come across invincible/desynced NPCs, use a takedown move or...
use a weapons with a wide area of effect (grenades, grenade launcher, etc.), or use a vehicle to ram them.
Knocking them down usually re-syncs their location with the server allowing them to be killed normally.
If using a vehicle with an interior, they can glitch inside, so hit them with your wheels.
These NPCs often can be identified by how much they glitch and teleport compared to other NPCs in the area. Their hit box is typically offset from their location onscreen so hits on the body appear to do nothing.
Always turn off engines when landing anywhere with gravity.
Ships have a bad habit of becoming airborne, if it does become air-borne, try to climb a nearby structure and jump to your ship... If it's barely off the ground you can remove certain armor components and stack them as boxes to try to get a little higher.
Note: The only exception to this is if you're bed logging while landed on a planet. In that case, the next time you load in, there's a chance that your ship spawns in before the ground does, and you will fall under the planet's surface. So leave your engines on if you plan to bed log while landed (or in atmosphere in general).
Always leave engines on when exiting your ship anywhere without gravity.
As long as your engines are on in space (and you're in the default coupled mode) your ship will slow to a stop even if something crashes into it.
The exception to this would be gravlev vehicles, if you'll be out for a while, since they burn through fuel quickly.
Do not land on asteroids (particularly the ones outside of the Pyro asteroid bases).
This has a decent chance of causing a "purple glow" to highlight your ship just as the server decides that something is wrong and it needs to clean up your ship. After this, your ship will be considered lost or destroyed.
https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-145631
How to not die when using the ATLS.
Touch the ATLS by walking into it, if it teleports around, repeat until it stops glitching out, and then get in.
The ATLS currently has an occasional bad habit of glitch teleporting into walls/vehicles/containers as you're entering it.
https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-133112
If you can't get a hospital room...
Set spawn to the current hospital location and backspace
or
Go to any room in the med facility. Stand as close as possible to the middle of the door and type /flex3. You should do a flex emote that pokes your head through the door, spam F throughout and you can open the door from the inside and use the bed. Might take a few tries, but it's pretty easy to do. Quicker than backspacing in any case
If you're unable to jump through a wormhole...
There's a bug where the jump drive gets removed from the quantum drive if you ever swap it out. You can buy another jump drive at the station on either end of the wormhole.
https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-143761
If you get stuck in a wall/rock...
Take off your arm armor first and place it at your feet. Sometimes this is enough to push you out.
If that's not enough, attempt to use a multi-tool tractor beam to pick up the armor box and then pull it in close to your character's body. If you have a friend nearby they can also attempt to throw boxes at you (if some portion of you is sticking out) or they can incapacitate you, then drag your body out with a tractor beam, then revive you.
Don't send/receive party invites while the sender/recipient are in an instanced location (any elevator or hangar) or else you will not see their marker.
Something about how you are in a different dimension messes around with the party markers and then you'll need to kick/reinvite the player to have their marker show up again.
https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-124715
If you can't put a fuse into a fuse door...
Try using a tractor beam instead and manually pushing it into the fuse slot.
If a broken fuse is taking up the slot, use a repair tool to slightly repair the current fuse, and then it will become interactable/removable.
Refueling/repairing "landing" screen issues
Sometimes repair/refuel options appear for a second before dissappearing and being replaced with the generic window for when you're not landed at a pad with vehicle services.
Workaround: Go to a different tab (like "Wallet") then return to the "Landing" tab and quickly click on the services you need.
Sometimes landing services don't appear at all. You can try to take off and land again (not likely to fix it anymore) but most likely you will need to try a different landing pad or store/retrieve if you are in your hangar. Sometimes you just need to wait an extra minute before landing services will appear if the servers are overloaded.
If you're at an outpost in Pyro that claims to have vehicle services, make sure you're landed at the pad that's completely surrounded by a structure and dips into the ground a bit.
If you use Nvidia DLSS, hold off on updating to Nvidia app version 11.3.01.218 since this will break DLSS in Star Citizen, stick with version 11.2.01.337 for now.
Issue that one of my org mates pointed out.
This will most likely be fixed in a later version.
~~If you're always respawning at the wrong hospital, have a friend incapacitate you and then quickly revive you.~~
https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-112051
Update: issue is marked fixed as of LIVE 9768350
For other known issues, check the information here:
https://support.robertsspaceindustries.com/hc/en-us/articles/360056254754-Star-Citizen-Alpha-4-1-Known-Issues
Or search through the issue council and look for workarounds on the ticket or in the comments.
The image from this post is from an old bug we had years ago.
Tap for Edits
Edit 1: Marked respawn issue as fixed.
Edit 2: Updated Issue Council link for the ASOP issue.
Edit 3: Added repair tool trick on fuses.
Edit 4: Added workaround for hospital issue.
I really hope that this lawsuit helps to invalidate any sort of terms of service which uses this language and forces you to agree to their terms simply by loading up their site for the first time.