Compatibility Report

• Name of the game with compatibility issues: Far Cry 5
• Steam AppID of the game: 552520

System Information

• GPU: AMD Radeon RX 9070 XT
• Video driver version: Mesa 25.3.0 (git-59b552c765)
• Kernel version: 6.16.12-valve24-2.1-neptune-616-gc748040e4712
• Link to full system information report as Gist: https://gist.github.com/M-Gilly/663754ad9f4dd6a465596e90d8a07995
• Proton version: Proton 10.0-4 (broken), Proton 9.0-4 (working)

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

Symptoms

There appears to be a regression between Proton 9.0-4 and Proton 10.0-4 affecting Far Cry 5 when using a Steam Controller with Steam Input enabled.

Hardware:

• CPU: AMD Ryzen 7 7800X3D
• GPU: AMD Radeon RX 9070 XT
• OS: SteamOS 3.8.11
• Controller: Steam Controller (2026 hardware revision)
• Steam Input: Enabled

The issue is not that the B button is completely non-functional. The game detects B button presses normally in menus and for other gameplay interactions.

However, specific gameplay actions that are mapped to B no longer work correctly under Proton 10.0-4:

• Reverse in ground vehicles does not work.
• Descend in helicopters does not work.

Under Proton 9.0-4, both actions work correctly using the same Steam Controller, Steam Input configuration, save file, and game installation.

Additional observations:

• The issue only occurs when Steam Input is enabled.
• Disabling Steam Input restores proper vehicle reverse and helicopter descend behavior.
• The B button itself continues to function in menus and other gameplay contexts.
• The controller is otherwise detected and functions normally under Proton 10.0-4.
• Disabling Steam Input is not a practical workaround for Steam Controller users because Steam Input is required for normal controller functionality.
• Proton 9.0-4 displays a persistent GPU driver warning at startup but controller functionality is correct.
• Proton 10.0-4 no longer displays the GPU driver warning, but introduces the controller regression.

The behavior suggests a regression in the interaction between Steam Input and Proton's controller handling rather than a general controller detection issue.

Reproduction

1. Launch Far Cry 5 using Proton 10.0-4.
2. Connect a Steam Controller.
3. Ensure Steam Input is enabled.
4. Enter a ground vehicle.
5. Press B to reverse.
6. Observe that the vehicle does not reverse.
7. Enter a helicopter.
8. Press B to descend.
9. Observe that the helicopter does not descend.

Expected result:

• Vehicle reverse functions normally.
• Helicopter descend functions normally.
• Behavior matches Proton 9.0-4.

Actual result:

• The B button is detected by the game.
• Menus and other B button functionality continue to work.
• Vehicle reverse does not work.
• Helicopter descend does not work.

Comparison:

Proton 9.0-4

• Steam Input enabled
• Vehicle reverse works
• Helicopter descend works

Proton 10.0-4

• Steam Input enabled
• Vehicle reverse does not work
• Helicopter descend does not work

Tested workarounds that did not resolve the issue:

WINEDLLOVERRIDES="windows.gaming.input=d" %command%
PROTON_ENABLE_HIDRAW=0 %command%
WINEDLLOVERRIDES="dinput8=b" %command%
WINEDLLOVERRIDES="xinput9_1_0=b" %command%
WINEDLLOVERRIDES="xinput1_3=b" %command%
WINEDLLOVERRIDES="xinput1_3=b;xinput9_1_0=b" %command%
PROTON_DISABLE_XALIA=1 %command%

Workarounds that caused additional problems:

WINEDLLOVERRIDES="xinput1_4=d" %command%

Result: controller stopped functioning.

WINEDLLOVERRIDES="dinput8=d" %command%

Result: game crashed before launch.

Attachments

Attached:

• steam-552520-proton9.log (working)
• steam-552520-proton10.log (broken)

Additional note:

Far Cry 5 has a long-standing issue where these same actions work correctly when Steam Input is disabled. However, Steam Controller users require Steam Input for normal operation, making this regression particularly impactful.

steam-552520-proton9.log
steam-552520-proton10.log