Summerisle
Published
5.11-GE-1-MF
Intermittent and jarring stuttering
Set reported windows version to WIndows 7
Switching from a lower resolution to a higher resolution causes blurriness that lasts until the game is restarted.
Controller does not work if BP overlay is enabled
86 FPS at menu, and an average of 30 FPS in-game. Performance is the same regardless of resolution and presets (e.g. 720p Very Low performs just as poorly as 1440p Ultra). Occasional and bad stuttering.
Unpredictable crashing. Game freezes and hogs 100% of one core.
Changed output mode to 1920x1080@144Hz from 2560x1440@144Hz, ran game in borderless windowed at 1920x1080
TAA at low settings looks like garbage (e.g. the game camera seems farsighted), FXAA at low settings causes such bad moire effect on certain surfaces that I ended up disabling AA entirely.
Overlay does not signal to game to open menu when activated, camera movement still occurs as a result (keyboard input is ignored when not focused, however). Controller is not functional with BPM overlay enabled.
Same-hardware performance in Windows averages 70 FPS at 2560x1440 with Ultra presets on DX11 (to ensure that a fair comparison is being made). To get a playable 49 FPS average with Wine/Proton, it was necessary to play the game at 1920x1080 with Very Low settings (albeit some options were increased - texture streaming was set to ultra, etc...). The game also suffers from severe stuttering, at least some of which is known to be due to shader compilation - I intend to test with Valve's ACO Mesa fork to determine to what extent this is remedied.
Also note, frame times in Windows (DX11) were about 10ms CPU, 10ms GPU. Frame times in Linux seem to average 13ms CPU and 12ms GPU.
The fact that going from Ultra to Very Low produces an average 5 FPS improvement indicates that performance issues somewhere in the translation stack.
Serious stuttering - on some occasions the game will freeze for between one and ten seconds. Shorter freezes are more common than long freezes.
The additional configuration needed will not be worth the poor performance for most users. Anyone expecting a smooth experience should be prepared to wait for improvements as people troubleshoot and profile the game performance with Wine to improve translation layer and game performance. While some users are showing acceptable figures in the benchmark, it is not clear what precisely is causing such good figures. I only have eight threads (logical CPUs) to work with, though I doubt a vastly increased threadcount would do much to improve CPU frame time. GPU performance should not be a problem in my case, certainly not for 1080p (nor 1440p@60 for that matter, as demonstrated by game performance in Windows). Furthermore the benchmark does not demonstrate the most taxing scenes in the game and is not an entirely reliable prediction of in-game performance.
Performance disparity versus Windows is too great, and resulting performance on Linux is too poor to be enjoyable at most times.
5.5-GE-1 GloriousEggroll
Using Wine 5.5 with GE's Proton patchset r1 (5.5-GE-1)
Balloons have some kind of shader or texturing issue.
Average 50 FPS disparity at same settings versus Windows. CPU frametimes are identical, GPU frametimes are ~8ms higher.
Startup movies are still broken, even with pending mediafoundation fixes available in GE's Proton 5.5 patchset. I have not taken time to confirm whether the progression-breaking "monitor bug" is still present, but you'll certainly be missing out on a lot of story-related pre-rendered cutscenes.
5.5-GE-1 GloriousEggroll
Used AMDVLK ICD instead of Mesa ICD
Some stutter when the game loaded assets or shaders, especially during heavy particle effects. After a while, everything has "warmed up" and there are no issues.
Full-screen video (startup movies & cutscenes) does not appear to work. In-game and HUD video does work, so progression is not hindered; however, you'll miss out on parts of the story.
Using the AMDVLK ICD instead of Mesa's ICD yielded an enourmous performance improvement. I compiled the latest stable (non-dev) version of the ICD available from AMD. For whatever reason, the Mesa ICD is emitting highly inefficient or incorrect instructions compared to the AMD ICD.
Replace launcher (Launcher.exe) with game executable (BorderlandsGOTY.exe)
Game crashes while logging in (ingame, not uPlay).
Playing Far Cry is simply not something that is happening. Games were purchased from the steam store, and getting the licenses imported into uPlay was only possible by launching the games in a Windows VM. License activation was seemingly impossible on Linux.
Game occasionally crashes when entering water, reason unclear
Audio, menu, startup are OK. There is a white screen after the initial loading phase that can be cleared by pressing escape. Attempting to enter a new game produces a black screen, though the application does not freeze.
Requires media framework, otherwise works correctly albeit with excessive stuttering and some input issues.
Attempts to upload invalid compute shader, aborts
Supersampling appears to cause serious artifacting, although TSA in Native did not appear to.
Appear to be some efficiency issues related large environments, supersampling
My Steam installation lives inside of an Ubuntu chroot. Ubuntu 22.04 appears to ship with a problematic libdrm or related, and was unable to properly upload shaders to the GPU. Upgrading the chroot to 23 resolved the problem.
