💥 Crashes
Code 3 crash with error: Star Citizen process exited abnormally (code: 3) : Command failed
- EAC bootstrapper failed to start up
- Explicitly set the DXVK device name
- identify device name using command
vulkaninfo --summary | grep deviceName - set device name with environment variable
DXVK_FILTER_DEVICE_NAME=yourdevicenamehere
- identify device name using command
- If using a flatpak launcher, you may need to resync it with your system. Run:
flatpak update
Game immediately crashes after clicking ‘Launch’
-
Start by checking the Wine output and/or “game.log” file. See initial troubleshooting steps and gathering logs.
-
See latest news for information on recent stability issues.
- Possible cause: DXVK
- Make sure DXVK is installed and enabled
- Nvidia users, check our latest news and Nvidia section for gpu driver issues, necessary workarounds, and currently recommended runner/DXVK versions.
- Possible cause: Incorrect Vulkan device
- If you have Intel integrated graphics and see
VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.jsonin your log, then change the Vulkan device to use your discrete GPU:- identify device name using command
vulkaninfo --summary | grep deviceName - set device name with environment variable
DXVK_FILTER_DEVICE_NAME=yourdevicenamehere
- identify device name using command
- If you have Intel integrated graphics and see
- Possible cause: GPU drivers not working properly
- If, in your “game.log”, you see only
llvmpipelisted as the working video adapter, your gpu drivers may not be functioning properly.
- If, in your “game.log”, you see only
- Possible cause: Out of date flatpak libraries/packages
- If you are using flatpak and have not run
flatpak updaterecently, this should be done regularly to keep everything up to date.
- If you are using flatpak and have not run
- Possible cause: Phantom joystick
- Many keyboards and mice can also have a “joystick” part in Linux, which Wine can detect. Unfortunately, Wine may be confused about it, as they are not real joysticks. In this case, the game could crash. Use the LUG Helper’s maintenance menu to run the wine control panel and disable your keyboard and/or mice.
Game launcher fails to start
- Possible cause: Outdated glibc
- Log message may include
could not load ntdll.so ... version 'GLIB-C_x.xx not found' - Update to the latest release of a non-LTS distro
- Log message may include
Game crashes after clicking ‘Verify’
- Make sure Star Citizen is installed on drive “C:" Check the “Library Folder” option in the launcher settings:
- Additionally, make sure the wine prefix is not installed on an NTFS formatted partition.oh keep in mind might be interesting to see what the model produces
Game crashes after loading into the PU
- Make sure you have set your vm.max_map_count and passed all LUG Helper preflight checks
Vulkan crash: Assertion failed! or vkCreateSwapchainKHR
- Edit the launch script and add the following environment variable:
export MESA_VK_WSI_PRESENT_MODE=mailbox - You may need to revert to DX11 by creating a USER.cfg file.
Vulkan crash: Required Vulkan Extensions are missing/error code 3
- Check if you have amdvlk installed by running
vulkaninfo --summary. The vulkaninfo utility is part of the packagevulkan-toolson most distros. You can also check your package manager. - If your system is using amdvlk, uninstall that package and replace it with
vulkan-radeon. - Make sure you’re using an up to date Wine runner. Old runners don’t have the required Vulkan extensions.
After playing for a while, crash with no errors
- If there are no errors in your game logs, check your system logs. It may be an Out Of Memory situation. Create a larger swap file.
Launcher freezes within a few seconds of opening
- Try using a different wine runner