Beanow
Published
Native version causes segfault in Wayland gnome-shell
For me the Native version would cause the Wayland gnome-shell to crash with a segfault. This would be at random moments, ~5 minutes into the game.
Since I had just updated gnome and my kernel, it may be a driver or gnome issue.
Either way, switching to Proton 9.0-2 instead of Native solved the problem. (I didn't have to test any other proton versions.)
Preformance, runs locked at my monitors 1440p@144.
Oh and the save game is preserved between versions. Nice touch.
Classic game renders in the top-left, rest of the screen is black. KaM Remake runs great.
Classic game has occasional crashes, KaM Remake runs great.
So the "native" Linux game ships the Classic game (with expansions) and a community mod, KaM Remake. Both are Windows exe's and it bundles a wine version + helper scripts.
Neither this "native" bundled Wine version, nor forcing the Windows version to be downloaded and running Proton through steam worked well for me. It had regular crashes and bugs.
But! KaM Remake fixes some of those bugs, and adds some quality of life features. The only issue is the bundled Wine didn't run (at all) on my system.
Using either system wine-7.7 from my distro's package manager, or using Bottles, both Classic (bugs included) and KaM Remake run well. I've played a few campaings on KaM Remake as the quality of life features make a huge difference.
TL;DR
Install wine through your system package manager, then:
wine <path-to>/Steam/steamapps/common/Knights\ and\ Merchants\ Historical\ Version/Game/KAMRemake/KaM_Remake.exe
Without CDLC and with increased latency. This doesn't offer a good alternative to running on Windows.
wintrick sound=alsa This is required for detecting audio devices by Rocksmith
Considerable latency after all listed optimizations
Custom DLC freezes the game and does not work.
I've tested Proton 5.0-6 and 5.1-GE-2 launched from steam. Both crashed on opening, so I needed to set it to 4.11-13.
Tested "phobos2077 no cable hack v2" with 2 audio interfaces as well. Line 6 POD HD500X, which I normally use on Windows, was detected by the game, but no audio. A simple Behringer UCG102 did work.
Otherwise same as with other comments.
Required to get the game to work
- WINEPREFIX=~/.steam/steam/steamapps/compatdata/221680/pfx winetricks sound=alsa This it to support detecting audio devices.
- WINEPREFIX=~/.steam/steam/steamapps/compatdata/221680/pfx wiinecfg and change Z: to /home/user/.steam/steam This is to launch the game at all.
- Edit ~/.steam/steam/steamapps/common/Rocksmith2014/Rocksmith.ini
ForceWDM=0
Win32UltraLowLatencyMode=0
Needed settings for working audio.
Suggested for lower latency
Rocksmith.ini
ExclusiveMode=0 (less latency than exclusive)
LatencyBuffer=1-4 (depending on CPU)
MaxOutputBufferSize=1024-1440 (depending on CPU)
DumpAudioLog=1 (to see audiodump.txt)
Edit /etc/pulse/daemon.conf
default-fragments = 5
default-fragment-size-msec = 2
Note, I derped on this initially and forgot the ; that were on front of it.
Remove those, as that marks a comment. Makes a significant latency difference. This supposedly increases power draw but haven't verified this.
FPS
Graphical performance wasn't an issue at all. As you might expect. I had max settings windowed or full screen, 1440p at 135-144 FPS. (144hz monitor, so it caps at 144).
Verdict
Could not enjoy this. Without the CDLC I got bored in less than an hour (excluding triage). And latency was still on the high side. Felt like the latency was in the 70-120ms range. Which is fast enough it's not confusing, but you will compensate for it in your playing. (e.g I can play the same riffs twice as fast on a real amp)
