Star Citizen · Linux
Linux Support - Limited
Fly Star Citizen on Linux with the same controllers and profiles as our Windows kits. This guide targets Bazzite, a gaming-focused Fedora Atomic distro that ships the drivers and tools most players need: install the game step by step, then follow the page for your controller from start to finish.
Why “limited”: Cloud Imperium supports Star Citizen on Windows only. It runs on Linux through Wine, thanks to the community’s Linux Users Group, and a game patch or Wine update can break things for a while. Our profiles are the same files as the Windows kits; Wine can name and order devices differently, so expect to check a few bindings after loading. For problems with the game itself on Linux, the LUG is the place to ask.
Step 1
Install Star Citizen on Bazzite with the LUG Helper
The LUG Helper is the Linux Users Group’s free installer. It tunes two system settings the game needs, sets up Wine (the layer that runs Windows games on Linux) with the LUG’s Star Citizen build, installs the RSI Launcher and adds it to your app menu. Menu names below are from LUG Helper v4.17.
-
Before you start
- Bazzite is up to date and you’re on the desktop (on a handheld or in Game Mode, switch to Desktop Mode first).
- About 150 GB free on a Linux-formatted drive (ext4 or btrfs, which is what Bazzite uses). Not an NTFS drive shared with Windows, and ideally an SSD, not a hard drive.
- Your RSI account login, and your Bazzite password: the Helper asks for it when it changes system settings.
-
Download the LUG Helper AppImage
Open the latest LUG Helper release and download the .appimage file (for v4.17 it’s
lug-helper-v4.17.appimage). Use the AppImage rather than the .tar.gz: it carries everything it needs, which is what you want on Bazzite, where the base system is read-only. -
Let it run, then open it
File manager: right-click the file, choose Properties, and turn on the option that lets it run as a program (in Dolphin, Bazzite’s KDE file manager, it’s Permissions › Is executable). Then double-click it.
Or in a terminal (Konsole on KDE), with the file in Downloads:
cd ~/Downloads chmod +x lug-helper-v4.17.appimage ./lug-helper-v4.17.appimage
Want it in your app menu? Bazzite comes with Gear Lever for managing AppImages: drop the file into Gear Lever and it adds a launcher.
-
Run the Preflight Check
In the main menu choose Preflight Check (System Optimization). It checks that
vm.max_map_countis at least 1048576 and the open-files limit at least 524288; Star Citizen needs both higher than most distros ship. If anything fails it asks “Would you like these configuration issues to be fixed for you?” Say yes and enter your password, then run it again until it reports your system is optimized. -
Install Star Citizen Launcher
Back in the main menu choose Install Star Citizen Launcher, then:
- It points you at the LUG Quick Start Guide and asks if you’re ready: continue.
- “Would you like to use the default install path? ~/Games/star-citizen” Say yes unless you want another Linux drive (then say no and pick the folder; it warns you if you pick NTFS).
- It downloads the LUG Wine runner, builds the Wine prefix (the folder that acts as the game’s C: drive) and installs the RSI Launcher. Leave it alone until it says “Installation has finished”.
-
Install the game in the RSI Launcher
Start RSI Launcher from your app menu (or run
~/Games/star-citizen/sc-launch.sh). Log in and click Install. The launcher offersC:\Program Files\Roberts Space Industries: don’t change it. On Linux that folder is~/Games/star-citizen/drive_c/Program Files/Roberts Space Industries. The game download is large, so this is the long wait. -
Finish with the LUG’s after-install list
Launch the game once to make sure it starts, then work through the after-install section of the LUG’s Quick-Start Guide: zram (memory compression), Wayland cursor fixes, Nvidia frame drops and non-US keyboards. Bazzite has Nvidia images with the driver built in. Stuck on an error? Maintenance and Troubleshooting › Show logs gives the LUG what it needs to help you.
-
Now set up your controller
Pick your controller below. Each page goes from plugging it in to flying: making sure Linux and Wine see it, installing our profile with one command, and checking it in the game.
Step 2
Pick your controller
Linux reaches joysticks two ways. hidraw hands Wine the raw device, exactly as Windows would; the Thrustmaster sticks need it. evdev is the normal Linux joystick driver, and the Logitech devices work through it. Each page covers its own path.
Logitech X56 HOTAS
evdevWorks with the standard Linux driver.
Set it up start to finish ›
Thrustmaster SOL-R 2 HOSAS
hidrawNeeds the LUG Helper’s hidraw rule.
Set it up start to finish ›
Logitech G PRO Flight Yoke System
evdevWorks with the standard Linux driver.
Set it up start to finish ›
Thrustmaster SOL-R 4 HOTAS
hidrawNeeds the LUG Helper’s hidraw rule.
Set it up start to finish ›
Thrustmaster T.16000M FCS
hidrawNeeds the hidraw rule and a Wine DLL override. Dual sticks or HOTAS.
Set it up start to finish ›
Xbox and PS5 controllers
gamepadBazzite ships the drivers.
Set it up start to finish ›Handy to know
Where things live
| Wine prefix (the game’s whole “C: drive”) | ~/Games/star-citizen |
|---|---|
| Game folder | ~/Games/star-citizen/drive_c/Program Files/Roberts Space Industries/StarCitizen/LIVE |
| Profiles (mappings) folder | …/StarCitizen/LIVE/user/client/0/controls/mappings |
| Launch script | ~/Games/star-citizen/sc-launch.sh |
| Find yours | LUG Helper › Maintenance and Troubleshooting › List Helper & Star Citizen directories and files |
Got a controller working on another distro, or found a better fix? Tell us on the Absolute Gaming Discord or at support@absolutegaming.store, and we’ll add it.
Star Citizen controller kits
Each kit has the control map, an editable PDF form and an XML generator. The profiles work on Windows and Linux.