Thrustmaster SOL-R 2 HOSAS on Linux

1. 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.

1. 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.

2. 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. Set the left stick’s base to LEFT HANDED and the right one to RIGHT HANDED; if both are on the same setting, the game sees two identical sticks and can’t tell them apart.

3. Confirm Linux sees it

   Open a terminal and run:

   lsusb | grep -iE '044f:0422|044f:042a'

   You should get one line per device: 044f:042a = left stick, LEFT HANDED, 044f:0422 = right stick, RIGHT HANDED. Nothing printed? Try another USB port and cable before going further.

1. 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".

2. 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.

3. Unplug and replug

   Unplug the USB cable(s) and plug them back in so the new rule applies. No reboot needed.

1. 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.

2. 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.

3. 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.

Prefer to do it by hand? Download layout_AbsoluteGaming_SOLR2.xml and copy it into ~/Games/star-citizen/drive_c/Program Files/Roberts Space Industries/StarCitizen/LIVE/user/client/0/controls/mappings.

1. Load the profile

   Start the game, open the console with ~ and run pp_rebindkeys layout_AbsoluteGaming_SOLR2 (no .xml). Or use Options › Keybindings › Advanced Controls Customization › Control Profiles.

2. Check the device order

   The left stick must be joystick 1. Take off and push the left stick forward: you should fly forward. If the nose pitches down instead, the sticks are swapped: run pp_resortdevices joystick 1 2, then the pp_rebindkeys line again.

3. 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.

4. 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.

Left stick: thrust and strafe.

Right stick: pitch, yaw, roll and weapons.