-
Notifications
You must be signed in to change notification settings - Fork 18
Troubleshooting
sc-lug-team edited this page Oct 5, 2024
·
99 revisions
- Check our latest news for known temporary issues, workarounds, and runner/dxvk/driver requirements (especially Nvidia users!)
- Make sure our LUG Helper's Preflight Check passes all checks
- Make sure all prerequisites from the Quick Start Guide are satisfied on your system
- Kill all wine processes and re-launch a fresh instance of the game
- In Lutris, select the game, click the arrow beside the wine button, choose
Open Bash terminal
and runwineserver -k
- If not using Lutris, run the following in your terminal, adjusting your prefix path as needed:
WINEPREFIX=$HOME/Games/star-citizen wineserver -k
- In Lutris, select the game, click the arrow beside the wine button, choose
- Look for your issue in the latest news
- Gather logs
- Check Lutris logs by clicking the arrow beside the play button:
- Run Lutris in debug mode to see more verbose logging
Native:lutris -d
Flatpak:flatpak run net.lutris.Lutris -d
- If CLI mode is turned on, there will be additional useful output in your terminal window
- Check Lutris logs by clicking the arrow beside the play button:
- Look for your issue/log output in the list of common issues below
- Ask for help on our social channels
💾 Install & Update Problems
💥 Crashes
🧊 Freezes
🤪 Unexpected Behavior (sometimes also crashes)
💚 Nvidia
❤️ AMD
🕹️ Controller Issues
🦦 Lutris Issues
👾 32bit Drivers
❔ Other Issues
- In Lutris, try setting
Prefer system libraries
toOn
globally before installation. After installation, this can be reset and configured only for Star Citizen if desired. - Make sure you are not trying to install to an NTFS-formatted drive.
- As mentioned in our Quick Start Guide, be sure you are not changing the default install path in the RSI Launcher settings. If you wish to install the game elsewhere, put the entire wine prefix there instead.
⚠️ Launch Lutris in debug mode (lutris -d
) and look for aKeyError: 'contentstatsid'
error.- If the error is present, check your Lutris version. This is fixed in v0.5.11. https://lutris.net/downloads
- If you get download failed errors during installation for components such as
arial32.exe
, try togglingPrefer system libraries
in Lutris toOn
.
- If using a rolling release or bleeding edge distro, try toggling
Prefer system libraries
in Lutris toOn
.
- Set
Prefer system libraries
toOn
in global lutris options. - Inspect install log for failed winetricks downloads or sha256 mismatch, note the URL of the files being downloaded and its destination in winetricks' cache.
- Download each file manually to its destination in winetricks' cache.
- Use winetricks to ensure that the prefix is set to Win10 mode.
- Proceed with lug-helper installer.
- We suspect this is a Lutris bug and fixes seem inconsistent.
- Try going to Lutris Preferences -> Sources, and toggle either
Lutris
orLocal
and then toggle it back again. - If you have an old install, try importing that into Lutris.
Lutris error: "Runtime Error('No path can be generated for DXVK because no version information is available.')"
- If you've just installed Lutris, be sure to launch it once, separately from the Star Citizen install process, to fully populate its runtime and caches.
-
Download the latest launcher and install it by selecting
Run EXE inside Wine prefix
in Lutris:
- Don't; it probably won't work and will likely only corrupt your game files.
- For more information, see CIG's announcement in Spectrum
- Solution 1:
- In the game's Lutris
System options
, make sure Advanced options is on then enableCLI mode
- In the game's Lutris
- Solution 2:
- If this does not fix the problem, revert the above changes and install the latest GloriousEggroll runner, available in our Helper
- You are likely 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
- identify device name using command
- If using the Flatpak Lutris, you may need to resync it with your system after installing the 32bit drivers. 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 enabled in Lutris' Runner options.
- Some people report changing their DXVK version fixes this. Try using our Helper to download an async DXVK.
- Nvidia users, check our latest news and Nvidia troubleshooting section below for gpu driver issues, necessary workarounds, and currently recommended runner/DXVK versions.
- DXVK installation instructions are available on our wiki here.
-
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 in Lutris 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
llvmpipe
listed 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 update
recently, 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. Try running the Wine joystick control panel "wine control" (in Lutris: right click -> Joystick configuration) and disable your keyboard and/or mice.
- This will not affect how your keyboard and mice work in the game.
- 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.
- Some penguins have had success changing the Windows compatibility from Win10 to Win8.1 in the Wine configuration. Select Star Citizen in Lutris, then click the Wine button at the bottom and select
Wine configuration
:
- In the Wine configuration, under the
Applications
tab, changeWindows version
toWindows 8.1
- Make sure you have set your vm.max_map_count as described in the installation section.
- Make sure you have set your vm.max_map_count as described in the installation section.
- Make sure the
SDL_VIDEODRIVER
environment variable is NOT set globally towayland
on your system.
- If you can't relaunch the game to switch it back to DX11, you can manually delete the file located at
{wine prefix}/drive_c/users/{user}/AppData/Local/Star Citizen/sc-alpha-{version}/GraphicsSettings/GraphicsSettings.json
- 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 you followed the guide to install Wine's dependencies and set your vm.max_map_count as described in the installation section.
- In game settings change display to windowed borderless
- Make sure DXVK is enabled in Lutris' Runner options.
- Try changing to a different DXVK version in the Lutris settings. Alternate DXVKs can be quickly installed using our LUG Helper.
- Nvidia users, check our latest news for gpu driver issues, necessary workarounds, and currently recommended runner/DXVK versions.
- DXVK installation instructions are available on our wiki here.
- Try using a different runner. Ask on Spectrum or in our social channels which runner is currently recommended.
- Alternatively, you can try changing "Prefer system libraries" to ON, although this may have other side effects.
- Right click the game -> Configure -> System options -> Prefer system libraries
⚠️ Launch Lutris in debug mode (lutris -d
) and look for aKeyError: 'contentstatsid'
error.- If the error is present, check your Lutris version. This is fixed in v0.5.11. https://lutris.net/downloads
- Some people report the launcher hanging in combination with the Lutris runtime. If you are on Lutris, try toggling "Disable Lutris runtime" under "System options" of the Lutris game options.
- If you do need to disable the Lutris runtime, the Lutris guys would like to have a log file to debug the issue. You can run lutris -d from the terminal after enabling Wine debugging as per this image:
- And send a log to @beniwtv on Spectrum or send it to Lutris developers in the Lutris Discord.
- The 3.18 update caused mouse and view snapping issues for most Penguins using Wayland + some desktop environments, especially KDE. The simplest workaround is to use Xorg or switch to an alternate desktop environment. For example, most Gnome users don't seem to experience this issue.
- For some users, switching their runner to Proton Wine >=9 is sufficient to resolve the issue.
- Alternatively, build xwayland with this patch applied.
- If using KDE and patching xwayland, you will also need to install Gamescope and use the
--force-grab-cursor
option.
-
Note for Nvidia users: Gamescope may not work on your hardware. See this known issue report.
- A possible fix to get Gamescope working on Nvidia:
Right click the game->Configure->System options->Game execution->Environment variables
then find or create__GL_THREADED_OPTIMIZATIONS
in the left column and change/set it to0
in the right column.
- A possible fix to get Gamescope working on Nvidia:
- After installing Gamescope, enable it in Lutris:
Right click the game->Configure->System options->Gamescope->Enable Gamescope
. Then, setOutput Resolution
to your monitor's native resolution, ie1920x1080
. - If you're using a version of gamescope newer than 3.11.51, an additional Gamescope setting is required. Set
Relative Mouse Mode
to on - Other Gamescope settings that may be required depending on your system:
Window Mode
set toFullscreen
if it doesn't launch fullscreen,-g
inCustom Settings
to grab keyboard - Depending on your system,
Prefer System Libraries
may need to be enabled or disabled in Lutris - If this doesn't work, you will need to switch to Xorg instead of Wayland.
- Create a user.cfg file in the LIVE, PTU, EPTU, TECH-PREVIEW directory
Con_Restricted = 0
#set to your display resolution
r_width = 3440
r_height = 1440
- Log out log back in, or reset the launcher by pressing Ctrl+Shift+Alt+R
- DXVK is likely disabled in Lutris's Runner options. Make sure it is enabled.
- Your game shader cache may need to be cleared. Our Helper can quickly clear your game shaders.
- Depending on your distribution, you may need to set
Prefer System Libraries
in Lutris toON
. - If you have sound in the launcher but not in the game, launch the game and go to your audio settings, then enable "Play sound while game is in background".
- Please follow our EAC migration instructions
- Check your process list for any lingering wine processes. Reboot if necessary.
- You may have to delete the EAC directory in youre prefix's
AppData/Roaming
directory. - You may also have to delete the EAC directory in the Star Citizen
LIVE
directory, followed by verifying files in the launcher.
- Check if you have amdvlk installed by running
vulkaninfo --summary
. The vulkaninfo utility is part of the packagevulkan-tools
on most distros. You can also check your package manager. - If your system is using amdvlk, uninstall that package and replace it with
vulkan-radeon
. - For additional help with this, ask in our Discord tech support channel.
- Error may read "Star Citizen requires DirectX feature level of 11.1 as a minimum which is not supported at present on this machine"
- Check that the
Vulkan device
is not set to an integrated gpu (ie, Intel)- identify device name using command
vulkaninfo --summary | grep deviceName
- set device name with environment variable
DXVK_FILTER_DEVICE_NAME=yourdevicenamehere
- verify by setting environment variable
DXVK_HUD=1
and observing the device name in the upper left of the screen
- identify device name using command
- Also make sure your GPU drivers (Mesa/nvidia) are up to date and DXVK is enabled/updated.
- Make sure the
SDL_VIDEODRIVER
environment variable is NOT set globally towayland
on your system. This causes incompatibilities with many games. If it is, simply unset it.
- Check for larger resolutions and scaling settings. See CIG's support article
- Check our latest news for gpu driver issues, necessary workarounds, and currently recommended runner/DXVK versions.
- Make sure DXVK is enabled in Lutris' Runner options.
- Try changing to a different DXVK version in the Lutris settings. Alternate DXVKs can be quickly installed using our LUG Helper.
- DXVK installation instructions are available on our wiki here.
- In Lutris, configure Star Citizen (right-click->Configure->Game options) and add
"--use-gl=osmesa"
to the Arguments field. - If launching manually:
wine "RSI Launcher.exe" "--use-gl=osmesa"
- Check the latest news recommendations for your graphics card
- Revert to DX11: Delete the AppData Local Star Citizen directory inside the wine prefix
drive_c/users/$USER/AppData/Local/Star Citizen/
- Error message may be similar to
/usr/bin/gnome-terminal.real: symbol lookup error: /lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0: undefined symbol: atk_component_scroll_to
- Disable the lutris runtime in lutris global preferences to work around this error
- See the Nvidia section of our latest news for the ways in which Nvidia is being special today.
- There is a shield rendering bug that causes the game to crash. It seems to affect 1000 series cards.
- There is currently no known workaround other than switching cards. We recommend AMD.
- Ignore or Disable DXVK NVAPI in Lutris.
- Right click the game -> Configure -> Runner options -> Enable DXVK-NVAPI/DLSS (set to off)
- Errors may include
DXVAVDA fatal error: could not LoadLibrary: msvproc.dll
orMajor opcode of failed request: 156 (NV-GLX)
- Try removing all optimus/prime env vars for render offload and set the Vulkan device to the Nvidia 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
- Some Penguins are seeing VRAM exhaustion problems on nvidia cards. It appears to be driver related and does not seem to affect AMD cards.
- A workaround that some Penguins have had some success with:
- Create a new
dxvk.conf
file and addd3d11.cachedDynamicResources = "a"
to it, then either exportDXVK_CONFIG_FILE=path/to/dxvk.conf
or, if using Lutris, addDXVK_CONFIG_FILE
as a new environment variable in the game's settings and set it to the file path. - If you still have issues or are running applications like OBS, you may also have to limit the vram the game sees to free up some vram for other applications:
dxgi.maxDeviceMemory = 6144
- Create a new
- There is an issue with LibCUDA that prevents vulkan and DLSS from working on linux.
- If using Wine-GE, add the environment variable
WINE_HIDE_NVIDIA_GPU=1
to enable vulkan - If using Wine or Wine-GE, see instructions to patch libcuda to enable both vulkan and DLSS
- There is a memory allocation issue with LibCUDA, where it attempts to allocate in a specific area already occupied by the game.
- A possible solution would be patching LibCUDA file increasing this area.
- Locate your 64-bit
libcuda.so
(usually/usr/lib
or runwhereis libcuda.so
). - To generate
libcuda.patched.so
, replace both placeholder/path/to/
lines below then run:echo -ne $(od -An -tx1 -v /path/to/libcuda.so | tr -d '\n' | sed -e 's/00 00 00 f8 ff 00 00 00/00 00 00 f8 ff ff 00 00/g' -e 's/ /\\x/g') > /desired/path/to/libcuda.patched.so
- Use the environment variable
LD_PRELOAD
to load the patched version:
LD_PRELOAD=/path/to/the/libcuda.patched.so:$LD_PRELOAD
- Remove the
WINE_HIDE_NVIDIA_GPU
env variable if it is set in Lutris or your launch script. - Don't forget to enable DXVK-NVAPI.
- Locate your 64-bit
- A possible solution would be patching LibCUDA file increasing this area.
- See this known issue report.
- A possible fix to get Gamescope working on Nvidia:
Right click the game->Configure->System options->Game execution->Environment variables
then find or create__GL_THREADED_OPTIMIZATIONS
in the left column and change/set it to0
in the right column.
- See the AMD section of our latest news
- To fix: Add environment variable
radv_zero_vram=true
- See our sticks, throttles, and pedals Troubleshooting Page
In Lutris, right clicking on Star Citizen and selecting "Configure" does not bring up the configuration
- Completely close Lutris with
kill lutris
, delete everything inside the Lutris cache directory~/.cache/lutris
, and relaunch Lutris.
- Enable the multilib repo
- Install 32bit drivers
- AMD
sudo pacman -S --needed lib32-mesa vulkan-radeon lib32-vulkan-radeon vulkan-icd-loader lib32-vulkan-icd-loader
- Nvidia
sudo pacman -S --needed nvidia-dkms nvidia-utils lib32-nvidia-utils nvidia-settings vulkan-icd-loader lib32-vulkan-icd-loader
- AMD
sudo dpkg --add-architecture i386 && sudo apt update && sudo apt upgrade && sudo apt install libgl1-mesa-dri:i386 mesa-vulkan-drivers mesa-vulkan-drivers:i386
- Nvidia
sudo dpkg --add-architecture i386 && sudo apt update && sudo apt install -y nvidia-driver-525 libvulkan1 libvulkan1:i386
- TBA
- AMD
sudo zypper in kernel-firmware-amdgpu libdrm_amdgpu1 libdrm_amdgpu1-32bit libdrm_radeon1 libdrm_radeon1-32bit libvulkan_radeon libvulkan_radeon-32bit libvulkan1 libvulkan1-32bit
- Nvidia
- Follow the instructions here: https://en.opensuse.org/SDB:NVIDIA_drivers
- Install 32bit drivers by appending the
-32bit
suffix to the driver package names - Install vulkan libraries:
sudo zypper in libvulkan1 libvulkan1-32bit
- We defer to your expertise