Linux Support - Limited › SOL-R 4
Star Citizen · Linux · Bazzite
Thrustmaster SOL-R 4 HOTAS on Linux
The Sol-R flightstick and Sol-R 6 throttle need Wine to read them as raw devices, one extra step on Linux. This page walks you from a fresh Bazzite install to flying with our HOTAS profile.
hidrawBazziteLUG Helper v4.17
At a glance
What this setup involves
| Linux talks to it through | Raw HID (hidraw), enabled by the LUG Helper |
|---|---|
| USB IDs to look for | 044f:0422 (flightstick, RIGHT HANDED), 044f:0447 (Sol-R 6 throttle) |
| How the game should see it | Joystick 1 = flightstick, joystick 2 = throttle |
| Our profile | layout_AbsoluteGaming_SOLR4.xml · same file as the Windows kit |
| Extra Linux setup | Hidraw rule from the LUG Helper (Step 3) |
Step 1
Install Star Citizen with the LUG Helper
Do this once for any controller. The full walkthrough on our Linux Support page goes screen by screen; here is the checklist.
-
Done these?
- LUG Helper AppImage downloaded and allowed to run (how).
- Preflight Check (System Optimization) passes.
- Install Star Citizen Launcher finished, with the default prefix
~/Games/star-citizen. - The game is installed from the RSI Launcher at its default path, and starts.
Step 2
Plug it in and make sure Linux sees it
-
Plug it straight into the PC
Use a USB port on the PC itself rather than an unpowered hub. Two devices means two cables: plug in both.
-
Check the handedness switches
Each Sol-R base has a left/right-handed switch on the back, and Linux sees it just like Windows does: the switch changes the stick’s USB ID. Our profile expects the flightstick on RIGHT HANDED (ID
044f:0422). On LEFT HANDED it reports044f:042aand the profile won’t attach to it. -
Confirm Linux sees it
Open a terminal and run:
lsusb | grep -iE '044f:0422|044f:0447'
You should get one line per device:
044f:0422= flightstick, RIGHT HANDED,044f:0447= Sol-R 6 throttle. Nothing printed? Try another USB port and cable before going further.
Step 3
Let Wine read the sticks directly (hidraw)
The LUG’s fix for Thrustmaster sticks: give Wine raw access so the game gets the same device, buttons and axes as on Windows.
-
Create the hidraw rule with the LUG Helper
Open the LUG Helper and choose Maintenance and Troubleshooting › Create joystick hidraw rules, then enter your password. It writes one rule file that lets Wine read Thrustmaster (vendor
044f), VKB and Virpil devices directly, the same way Windows does. Check it is there:cat /etc/udev/rules.d/40-starcitizen-joystick-uaccess.rules
You should see a line with
KERNEL=="hidraw*", ATTRS{idVendor}=="231d|3344|044f"…TAG+="uaccess". -
Use LUG Wine 11.4 or newer
In the LUG Helper open Manage Wine Runners. The LUG says hidraw for Thrustmaster needs LUG Wine 11.4 or newer. Check which runner you are on; if it is older, install the newest LUG Wine from that menu and switch to it.
-
Unplug and replug
Unplug the USB cable(s) and plug them back in so the new rule applies. No reboot needed.
Step 4
Check it in Wine
-
Open Wine’s controller configuration
In the LUG Helper choose Maintenance and Troubleshooting › Open Wine controller configuration. This is Wine’s version of Windows’ joy.cpl, running inside your game’s Wine prefix.
-
One entry per stick, not two
With hidraw on, a stick can appear twice: once as the raw device and once as the Linux event device. Keep the one that matches your USB ID and select the copy that doesn’t, then click Disable. You want exactly two active entries.
-
Test every axis and button
Use the window’s test view: move every axis through its full range and press each button. Thrustmaster’s T.A.R.G.E.T. software doesn’t exist on Linux, which is fine: our profile is built for the sticks without it.
Step 5
Install our profile into the game
These lines create Star Citizen’s mappings folder inside your Wine prefix if it’s missing and download our profile straight into it. Change the prefix if you didn’t use the default. Built your own profile with the generator? Copy that file into the same folder instead.
~ and run
Devices the wrong way round? Run pp_resortdevices joystick 1 2 in the console, then run the pp_rebindkeys line again.
Prefer to do it by hand? Download layout_AbsoluteGaming_SOLR4.xml and copy it into ~/Games/star-citizen/drive_c/Program Files/Roberts Space Industries/StarCitizen/LIVE/user/client/0/controls/mappings.
Step 6
Load it and check it in the game
-
Load the profile
Start the game, open the console with
~and runpp_rebindkeys layout_AbsoluteGaming_SOLR4(no.xml). Or use Options › Keybindings › Advanced Controls Customization › Control Profiles. -
Check the device order
The flightstick must be joystick 1 and the throttle joystick 2. If pushing the stick changes your speed instead of your pitch, run
pp_resortdevices joystick 1 2, then the pp_rebindkeys line again. -
Check the directions
Our profile carries the same axis inverts as on Windows, but Wine can report a device under a slightly different name, and then those settings don’t attach. If an axis comes out backwards, go to Options › Keybindings, pick the joystick, open Inversion Settings and flip it there.
-
Fly a test circuit
In the hangar or on a pad: power on, flight ready, lift off, every main axis, fire, landing gear, then quantum mode. Compare with the control map below. Anything off? Rebind it in the game or fix it in the form and regenerate.
Stick grip: flight and weapons.
Sol-R 6 throttle: thrust, strafe and systems.
Step 7
Good to know for the SOL-R 4
- Calibrating the flightstick without Windows. The LUG wiki’s Sol-R manual calibration: base unplugged; hold the upper trigger and the left grip button (35) while plugging in; let the thumbstick and twist rest at center and press the scroll-wheel; move the thumbstick to its limits on both axes and twist fully both ways; press the scroll-wheel again, then unplug and replug.
- The rudder. Twisting the throttle handle is a rudder axis, left free in our profile. Bind it to yaw or strafe if you like.
- Two throttles. The stick base has its own throttle lever too. With the Sol-R 6 doing the thrust, it’s free for something like mining power.
- NAV mode. Stick base button 18 switches between SCM and NAV.
Troubleshooting
If something’s not right
- A device is missing in the game? Thrustmaster: redo Step 3 and check the rule file and Wine version. Anything else: in Wine’s controller configuration, select it and click Override (dinput).
- An axis does nothing? Check the game hasn’t set that axis’s deadzone to 100% under Options › Keybindings.
- Everything broke after a game or Wine update? Check the LUG wiki news first; fixes usually land there.
- Still stuck? Use the LUG Helper’s Maintenance and Troubleshooting › Show logs, then ask in the LUG’s channels (game on Linux) or on our Discord (our profiles).