Compatibility Report

Confirm this issue is still present with the latest Proton Experimental, and also on a Saitek X52.

For me Saitek x52 work normally only on official 6.3-8. Starting with 7.* version I have the same issue, on GE builds as well.

Proton 6.3-8 worked fine with the Thrustmaster T.16000M. With Proton 7 and with the experimental Proton version I observe the same behavior as described above. All attempts to mitigate the issue via the HOTAS mapping files unfortunately failed.

The main issue is that since the last game patch Proton 6.3 does not work anymore (the game crashes during initialization). It starts with Proton 7 and experimental though.

I checked with the Proton 8 Version that just came out, still the same Issue.

Just chiming in here to report the same issue exists with the ThrustMaster T.Flight Hotas X as described. Tried all Proton versions including 6.3-8 (which, as already stated, crashes on startup), 7.0-6, 8.0-1, Experimental and GE 7.55, all of which will run but still cause the issue.

Also can confirm this happening in Proton 8 GE. Game runs great, except joysticks get locked and act like they're d-pads. Bizarre.

Still facing issue with joystick on latest proton version (8.*) and experimental. What should be done to get this issue in progress?
For example: War Thunder or Elite Dangerous do not have such issue, joystick works as expected.

proton 8.0-4 issue exists
https://github.com/ValveSoftware/Proton/issues/5351#issuecomment-1412473651
Looks the same, issue with wheel device everywhere except of 6.3.8 proton version

Slackware64-Current
Linux 6.6.8
GTX 1070
NVIDIA Driver 445.29.06
Steam Version: 1702079146
Steam Client Build Date: Thu, Dec 7 7:33 PM UTC -08:00
Steam Web Build Date: Fri, Dec 8 6:30 PM UTC -08:00
Steam API Version: SteamClient021
Proton: 1703018341 experimental-8.0-20231219

PROTON_LOG=1 https://gist.github.com/EpicureanGit/03c35fa5e88075d6a29c32d986ca4c18
System Information: https://gist.github.com/EpicureanGit/e1cdbb16799067869925b7a16d1bba3b
Steam Runtime System Information: https://gist.github.com/EpicureanGit/10f01b21c38b0a4bac1198ed7c5d3db5

Game controller connected to PC:
Bus 002 Device 007: ID 044f:b10a ThrustMaster, Inc. T.16000M Joystick

Symptoms: The game doesn't respond to the Thrustmaster T.16000M moving across different axes correctly. The crosshair in the game may or may not respond. If it does, it won't move in the correct direction. It has a mind of its own. The Thrustmaster T.16000M works well with Project Cars 2, Need for Speed: Hot Pursuit Remastered, and STAR WARS Squadrons.

Reproduction: Select Single Player and then select Instant Action, and then press confirm and ready.

Symptoms: A small window appears that says "Fatal Error!" with Proton: 1655928813 proton-6.3-8f
PROTON_LOG=1 https://gist.github.com/EpicureanGit/90e658d5c15063b41308d292665daebb
Reproduction: Press "PLAY" in the Steam client.

Confirming I have the same issue.As a slight difference to other reports, it seems to me that the axis don't "stick" as such. I mapped all the other axis to non-existing outputs so that I could test each axis individually. They all seem to work the same. The positive output values (0.0,1.0] seem to work as expected, but negative values [-1.0,0.0) are seen in-game as maximum positive offset. That is: I can use the remapping to configure the positive side of each axis (pitch up, roll right) to work, but any offset into the negative direction (pitch down, roll left) will be interpreted as max up/right, making the whole axis unusable. No amount of fiddling with the mappings can fix it.

For example, this works fine when pulling on the stick (pitch up) but pushing on it goes wildly in the wrong direction:
AXIS: InAxis=HOTAS_YAxis, OutAxis=Joystick_Axis1, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.05, DeadZoneMax=0.05, MapToDeadZone=TRUE

On the other hand this allows me to control the nose up-down by only using the positive half of the axis (mid-way offset acts as 0) but again, the other half goes max-speed to the wrong direction:
AXIS: InAxis=HOTAS_YAxis, OutAxis=Joystick_Axis1, Invert=FALSE, Offset=0.0, DeadZoneMin=0.45, DeadZoneMax=0.55, MapToDeadZone=TRUE

Also, I tested the dinput via joy.cpl (~/.steam/steam/steamapps/common/Proton\ -\ Experimental/files/bin/wine control joy.cpl), and there the joystick axis seem to work just fine.

Edit: Also, just like the other reports, I get the fatal error dialog if trying to run on proton 6.3

Just tested Proton 8.0-5 and the problem persists.

My attempts to get 6.3-8 running again failed. I played around with various Steam switches via environment variables before starting steam from the shell with the switches set. Unfortunately none helped with the crash.

Does anyone still have a version without the "Rise of Rasalhague" DLC? The crash seemed to have come with that version. Not sure though if it is the DLC itself or an update of the base game that led to the crash.

Disabling all DLCs via Steams UI also does not fix the fatal error with 6.3-8.

I took a look into the changes between proton-6.3-8 and proton-7.0-1.
And for my illiterate eye, only these two commits might give hints:

• Commit 3b9480 (Feb 11, 2022) - docs: Update CONTROLLERS for Wine 7.0: updated the architecture diagram and the various input subsystem work with each other.
• Commit 05395407 (Feb 11, 2022) - Update wine: update wine from 6.3-3 to 7.0-100

Unfortunately, if I try to look into the changes between wine 6.3 and wine 7.0, I am overwhelmed by more than 5000 commits.

If anybody has idea how to pinpoint the breaking changes (e.g. with a sophisticated git bisect setup?), then lets here them.

Slackware64 Current
NVIDIA GTX 1070 with NVIDIA Driver Version 555.58.02
Steam Build: Steam Beta Branch: Stable Client
Steam Version: 1721173382
Steam Client Build Date: Tue, Jul 16 7:22 PM UTC -08:00
Steam Web Build Date: Mon, Jun 24 3:16 PM UTC -08:00
Proton: 1721412568 experimental-9.0-20240719
System Information: https://gist.github.com/EpicureanGit/0695fbde6dfc7bcf5b8fabcd62f94341
System Runtime Diagnostics: https://gist.github.com/EpicureanGit/9932edeb591ba63cfbcd29b921e0629f
System Report: https://gist.github.com/EpicureanGit/9aed3fd6cc1c5dc87af5477d6ff4e194

Proton_LOG=1 https://gist.github.com/EpicureanGit/58afb3edb89469ed58631621336eccff

Proton Experimental fixes the Thrustmaster T.16000M joystick's axis movement as far as I can tell. Thank you!

Symptoms
No buttons on the Thrustmaster T.16000M joystick except for the hat is recognized by MechWarrior 5 or Need For Speed Hot Pursuit Remastered with Proton Experimental. I Switched back to 9.0-2 and the buttons work again for both games but the axis movement on the Thrustmaster T.16000M is messed up again in MechWarrior 5 like I reported in my previous post.

Reproduction: Use Proton Experimental, Select Single Player and then select Instant Action, and then press confirm and ready.

Edit: Proton: 1722351075 experimental-9.0-20240730 fixed the issue with the buttons not being recognized. The Thrustmaster T.16000M joystick's axis movement is messed up again in MechWarrior 5.

Confirming this issue in both Mechwarrior 5: Mercenaries and Mechwarrior 5: Clans

Debian Version 11.11
NVIDIA RTX3070
Steam Build: Steam Beta Branch: Stable Client
Steam Version: 1726604483
Steam Client Build Date: Tue, Sep 17 4:03 PM UTC -05:00
Steam Web Build Date: Mon, Sep 16 7:12 PM UTC -05:00
Proton: 1727104926 proton-9.0-3c

Device: Microsoft Sidewinder Precision 2 Joystick PN: X08-58015
USB ID 045e:0038

Symptoms
Using Proton's joy.cpl, everything looks normal in testing, all axis and buttons respond as expected in (js) mode. In Event mode, Throttle slider doesn't respond, but all other functions behave.
Using a known good HOTASMappings.remap file from a windows10 install, deadzone and offset settings appear to be mostly ignored for analogue axis. H & V axis also drift to one side or the other.
Removing the remap settings and using in game mapping of

• Vertical look : Joystick Axis 2
• Horizontal Look : Joystick Axis 1
• Leg Rotation : Joystick Axis 3
• Throttle : Joystick Axis 4

results in things going the right directions ( sort of ) , but appear to have no dead zones or offsets.

Building a new HOTASMappings.remap file mapping
Axis_1 -> Joystick_Axis2 -> Vertical Look
Axis_2 -> Joystick_Axis1 -> Horizontal Look
Axis_3 -> Joystick_Axis3 -> Leg Rotation
Axis_4 -> Throttle_Axis1 -> Throttle
also results in sporadic deadzone behavior and ignoring of offsets.
Can force view all the way up , and sometimes get the side to side centered, but then on any other input the vertical goes to bottom or horizontal goes hard right.
Hard buttons (1-8) appear to be recognized correctly in game. The hat buttons only get recognized intermittently.

Reproduction:
Mercs: Use Proton Experimental, Select Single Player and then select Instant Action, and then press confirm and Ready.
Clans: Use Proton Experimental, Select Continue , select barracks, select Sim Pod, select Training Missions, Select Shooting Range, Select Launch Simulation

I am also experiencing the same issues as the original poster, to the point I don't feel its necessary to include my own steps, as I have literally done everything they have.

The only acceptation is that I am using a Thrustmaster T.16000M, but otherwise I am experiencing the exact same behavior.

Operating System: Arch Linux
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.4-arch2-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7700X 8-Core Processor
Memory: 32 GiB of RAM (31.0 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3080
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B650 AORUS ELITE AX V2

Proton: 9.0-4

Also tried:
Proton Experimental

I am experiencing the same issues as the former poster, so no need to go into details again.

I use a Thrustmaster T Flight Stick X (ID 044f:b106 ThrustMaster, Inc. T.Flight Stick X)

OS: CachyOS x86_64
Kernel: Linux 6.16.6-3-cachyos
CPU: AMD Ryzen 7 3700X (16) @ 4.43 GHz
GPU: NVIDIA GeForce GTX 1070 [Discrete]
Memory: 4.27 GiB / 15.54 GiB (27%)
Desktop: KDE Plasma v: 6.4.4

inxi -F parts:
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1070] driver: nvidia v: 580.82.09
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: gpu: nvidia,nvidia-nvswitch
resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: nvidia,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.82.09
renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2
API: Vulkan v: 1.4.321 drivers: nvidia surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Machine:
Type: Desktop Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0
serial: UEFI: American Megatrends LLC. v: A.F0
date: 10/11/2023

I tried :
Proton: 9.0-4
Proton: experimental
Proton: Proton-cachyos (steam linux runtime package)

Tried this solution, and my hotas is working now correctly. Just needed some mapping adjustment.