If anyone wants to play with (almost) highest settings, I took a copy of the video settings from Windows: video.zip
Place the video.dat in compatdata/1465360/pfx/drive_c/users/steamuser/My Documents/My Games/SnowRunner/base/storage. File can be edited to adjust resolution.
Performance is okish, just slightly worse than on Windows. Steering wheel integration is horrendous but I think that's a game problem since I can't get it to work properly on Windows either.
Even though it looks like the file gets converted to a normal text file when you extract it, the game still reads it. However, you can't edit it. At least not in Linux. It breaks the file and the game will stop reading it the moment you open it or save it.
Using Proton 7.0-1 and 6.3-8 I was able to get the SnowRunner game recognize the wheel using -e flag in steam launch arguments. In the game settings the wheel is recognized when the steering wheel API is set to either DirectInput or Thrustmaster. Setting it to Logitech Legacy or Logitech Trueforce doesn't detect the wheel. When I have been playing the game with Windows 10, the Logitech Legacy has been the correct option.
I can map the buttons and use the wheel to steer but the FFB isn't working properly. I don't have any FFB when turning the wheel but sometimes it applies a huge spike of FFB, I think. This lasts maybe a half second and makes a pretty bad noise from the wheel base. This was using either the DirectInput setting or Thrustmaster setting, in the log-file DirectInput.
Same issue 3 years later.
Still no FFB with G923. Or has anyone found a solution?
Still no FFB with G923. Or has anyone found a solution?
Try switching to proton 6.3, that works for me for some reason.
Still no FFB with G923. Or has anyone found a solution?
Try switching to proton 6.3, that works for me for some reason.
Hey, thanks! Yes FFB works with 6.3-8, but Coop/Online does not work sadly. Online does work on the more recent Proton versions though.
Replying to https://github.com/ValveSoftware/Proton/issues/4834#issuecomment-3913137045
I can confirm that this is still the case, for me with a Moza R5 wheel that works flawless in other games. Proton 6.3-8 works for Force Feedback but online functionality is broken.
No FFB with my Thrustmaster T248 either. I have working FFB with Proton Experimental in every other game I've tested.
In SnowRunner, FFB works with Proton 6.3.8 and does not work in ANY newer version.
The problem is 6.3.8 provides only half the performance compared to Exp and the online features do not work with 6.3.8
Can confirm that the only Proton version providing Force Feedback for Wheels is 6.3-8... however, that Proton version won't allow you to play online co-op.
Can also confirm exactly this.
I've tried proton-cachyos, wine-cachyos-10.0, GE-Proton-10-34, GE-Proton-9-17 and various Valve Proton versions.
Some of them completely ignore the wheel, with some of them whe wheel works but there is NO FFB. The only version that recognises the wheel AND working FFB is Proton 6.3-8 but with that version the online functionalities of the game don't work.
This only applies to SnowRunner. Assetto Corsa e.g. has full FFB with GE-Proton 9-17. I'm running Assetto Corsa Evo with the most recent proton-cachyos which also has full FFB. Only SnowRunner has these problems.
CachyOS x86_64
Linux 7.0.11-1-cachyos-bore
Fanatec GT-DD Pro
No ForceFeedback in Snowrunner
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9876.
@Tuskiurhil posted on 2026-06-15T05:59:07:
Proton-Log: https://drive.proton.me/urls/MZVERYC3GW#KUN2ArQ1u8cF
Using any Proton Version other than 6.3-8 causes the Force Feedback in this game to stop working. Coincidentally, 6.3-8 also prevents you from playing online.
Launch the game on a proton version other than 6.3-8 using Force Feedback enabled peripherals.
I had the exact same issue with Snow Runner and subsequently the Road Craft demo with Gnome Bazzite. However I just installed Kubuntu 26 LTS (and had setup hiccups but besides the point), and Road Craft FFB worked. I am thinking that past proton 6-8 they implemented SDL and that is causing permission issues potentially fixable with udev rules or perhaps disabling it PROTON_PREFER_SDL=0 SDL_JOYSTICK_WHEEL_DEVICES="" SDL_GAMECONTROLLERCONFIG="" %command%. I have not tried the later two but this is what I have found. I will try it with Snow Runner soon, but I expect a similar result.
I see it could be an issue with snboxed flatpack that unsandboxed Debian applications lack. And SDL is a likely difference.
FFB also works in Expeditions (the game that was released before Roadcraft). Thanks for the startparameters, I'll also give it a try :)
I had Claude Code take a look at Proton 6.3-8 and Proton 11 and their respective logs generated playing the game. It went through a few ideas, and arrived at the following fix / workaround: https://github.com/DSBalaban/snowrunner-proton-fix.
The README includes installation instructions. It also has instructions for building the DLLs, so you don't have to trust the ones in the repository.
I'm using the DLLs on CachyOS 7.1.3-2-cachyos with a Thrustmaster T300 RS, and I have a friend on Bazzite 7.2.0-ogc6.1.fc44.x86_64 with a Logitech G29. We've been playing happily for some 40 hours and haven't noticed issues.
Hope this helps
SnowRunner (1465360) - consistent crash before main menu, all Proton versions, RX 9070 XT/RDNA4
Issue transferred from https://github.com/ValveSoftware/Proton/issues/10114.
@nmds98f9sv-coder posted on 2026-09-02T20:47:12:
SnowRunner reliably hangs and crashes before or immediately at the main menu (background renders, but no UI elements ever appear, then the process dies). Reproducible across every Proton version tested: Proton Experimental (multiple builds over several weeks, including the current one as of this report), Proton-CachyOS latest, GE-Proton 11, Proton 10, Proton Hotfix. Also reproduces after updating the game to Patch 43.0.
The game runs fine on Steam Deck (same Steam account/library), so this appears specific to desktop Linux and/or RDNA4 GPUs.
The attached PROTON_LOG shows a consistent pattern across every crash, regardless of Proton or game version:
fixme:d3dkmt:NtGdiDdDDIQueryStatistics (...): stub hundreds/thousands of times in a tight loop.RtlpWaitForCriticalSection ... wait timed out ... blocked by <spinning thread>, retrying (60 sec)..NET-side exceptions follow: System.ComponentModel.Win32Exception: Invalid window handle (repeated).dbghelp:SymCleanup this process has not had SymInitialize() called for it! suggests a crash reporter (possibly EOS SDK) attempting to generate a dump and failing.Already ruled out during troubleshooting:
MANGOHUD=0)amdgpu ring timeout/reset/fault entries in kernel log at time of crash)SteamDeck=1 %command% launch flagPROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command% (crash timing varies slightly but issue persists)Issue has been present since the system was first assembled and CachyOS installed (~3 weeks ago), not a regression from a specific update on my end.
Transparency note: I used an AI tool (Claude, Anthropic) to help investigate this issue and draft this report. All technical details (log excerpts, versions, test results) were manually verified by me against my own system and logs before submitting.
@DSBalaban how does the workaround work with SDL vs HIDRAW?
@DSBalaban how does the workaround work with SDL vs HIDRAW?
@Kurotsune77 Should be independent of that. The workaround patches DirectInput, then Wine takes that and translates it into SDL / HIDRAW down the line
proton experimentalx2 2026-09proton hotfixx1 2026-09proton 6.3-8x3 2026-08proton 11.0x1 2026-06proton 6.3x3 2026-05proton 7.0-1x1 2022-03MANGOHUD=0`)x1 2026-09PROTON_ENABLE_HDR=1x1 2026-09PROTON_ENABLE_WAYLAND=1x1 2026-09PROTON_LOGx1 2026-09PROTON_PREFER_SDL=0x1 2026-07SDL_GAMECONTROLLERCONFIG=""x1 2026-07SDL_JOYSTICK_WHEEL_DEVICES=""x1 2026-07PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command%x1 2026-09SteamDeck=1 %command%x1 2026-09PROTON_PREFER_SDL=0 SDL_JOYSTICK_WHEEL_DEVICES="" SDL_GAMECONTROLLERCONFIG="" %command%x1 2026-07
Compatibility Report
System Information
I confirm:
steam-1465360.log
Symptoms
Game freezes after the dxdiag dialog appears when changing any settings in the graphics menu:
Reproduction
Start the game, change any setting in the graphics menu and hit save.