💥 Crashes

Error Code 210 and #1 Crash

EAC bootstrapper failed to start up
You may be missing 32bit drivers. See 32bit Drivers below for more information
Additionally, 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
If using a flatpak launcher, you may need to resync it with your system. Run: flatpak update

Start by checking the Wine output and/or “game.log” file
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.json in 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
Possible cause: GPU drivers not working properly
- If, in your “game.log”, you see only llvmpipe listed as the working video adapter, your gpu drivers may not be functioning properly.
Possible cause: Out of date flatpak libraries/packages
- If you are using flatpak and have not run flatpak update recently, this should be done regularly to keep everything up to date.
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.

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

Make sure you have set your vm.max_map_count and passed all LUG Helper preflight checks

Check the latest news for recommendations for your graphics card
Go back to DX11 by using the Delete Shaders option in the RSI Launcher > Settings > Games > {LIVE,PTU} > Delete Local Settings > Shaders folder

Some Penguins have had this error when using BTRFS. We suspect a regression of some kind.
Easiest: Just ignore the error and continue playing. It doesn’t crash until you click the button.
Or fix it: Disable CoW on the game’s StarCitizen dir
1. Navigate to the Game folder star-citizen/drive_c/Program Files/Roberts Space Industries
2. Use a terminal to run the command chattr +C ./StarCitizen, then redownload or copy in a fresh data.p4k.
Less easy Fix: Disable CoW only on the data.p4k file. This can only be done on an empty file.
Alternatively, try mounting with the compress option instead of compress-force.
If that doesn’t work, switching to ext4 is an option.

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.

Make sure DXVK is installed. Use the LUG Helper to install it
Nvidia users, check our latest news for gpu driver issues, necessary workarounds, and currently recommended runner/DXVK versions.