dragontalon42
Published
No need for any tinkering or messing with wine verbs, it seems Catherine likes GEProton8-20. Works out of the box with 0 issues as far as I could tell. I started it up and then loaded a save game without issues and started playing.
gamescope -W 2560 -H 1440 -w 2560 -h 1440 -r 100 -o 60 -b -f -- %command%
Running this with Proton Experimental caused it to crash on the initial shader compilation when it boots up. It was a wine failure with error "assertion failed wine !status and vkcreategraphicspipeline". After Steam downloaded the shader cache once I switched to GE-Proton9-5, it worked, but then once I started fighting goblins on the initial road to the first camp, the game crashed necessitating a reboot. Cause was a gpu pagefault which is a known issue with this game on Linux. Once it was wrapped in a gamescope session, I was able to play for almost 6 hours before I quit. Game is playable at max settings on my hardware, though I did not check the framerate. The patches have improved the general stability of the game significantly from launch.
MANGOHUD_CONFIG=no_display,fps_limit=120 mangohud %command%
Windowed Fullscreen has a white border around the window
Crashing with my hardware was not unusual. Frequently, it would reset graphics driver, crash my GPU, and kill my DE, forcing a power cycle as the system was entirely unresponsive. This is apparently a known issue with 7000 series cards at the moment. (https://www.reddit.com/r/Helldivers/comments/1ap8kut/for_my_fellow_amd_7000_card_holders/) Fullscreen would usually cause everything to die, however windowed fullscreen could sometimes allow a recovery to desktop.
Online play frequently wouldn't work or would cause a crash. Often I wouldn't be able to join other players or would get booted or experience a crash when playing with others.
Core gameplay is fun, but issues regarding online play and stability are present. Also tried Proton Experimental and Proton Hotfix. PE was roughly as stable as GE-Proton8-32. Turning off Screen Space Global Illumination and Anti-Aliasing help a bit, but the hard crashes are still present. There is speculation that AMD hardware reaching 100% utilization causes a crash which is why some people say to lock the framerate to something below the card or CPU's max framerate. Some reports suggest that running at Native resolution and turning everything to Low and locking the framerate to 30fps helps more, but I didn't test that and it just sounds like an unpleasant experience.
DXVK_FRAME_RATE=144 %command% --use-d3d11
White border around borderless window
To make this work, first go into the location /steamapps/compatdata/553850/pfx/drive_c/users/steamuser/AppData/Roaming/Arrowhead/Helldivers2/shader_cache/ and delete the file or files present. Those are the DX12 shader cache files. Add the launch options and start. Copied from other threads on the issue in the Mesa and Steam forums. This forces the game to run in DX11 instead of DX12 which is a higher-level API with more abstraction so it shouldn't overload the GPU.
This should resolve the crashing present on AMD 7000 series GPUs until the DX12 implementation is fixed or whatever the underlying issue may be. Issues with multiplayer were mainly due to the current server overload. Frame rate cap might not be 100% necessary but no need to stress the GPU excessively. Especially the opening cinematic tends to run at 100s of frames per second which is hilariously unnecessary. In the 2 matches I played solo, I didn't have any crashes, so roughly a couple hours of play.
Used GE-Proton8-16, Proton Experimental, Proton 8.0.4
It would install and run the install scripts and then change its status to Launched and Running but would not actually launch the game.
Used Proton 8.0.4 worked OOTB
No launch options used. Previously made a report that it was borked, I think the source was that I had changed my graphics hardware from Nvidia to AMD without uninstalling the Nvidia drivers beforehand. Based on logs it seems like Proton was not able to grab the graphics adapter. Fresh install of Nobara and that seems to have resolved the issue. Was previously unable to play on Nvidia but on AMD it works as described.
The OpenGL renderer is problematic. Use the Zink driver instead. That forces OpenGL over Vulkan. Enable Zink so the game works properly.
gamemoderun mangohud MESA_LOADER_DRIVER_OVERRIDE=zink %command%
Performance problems were caused by the OpenGL renderer in Ren'Py which made the kurdle minigame impossible to win. The framerate was running in the 20s which ordinarily wouldn't be a problem for a visual novel game, but this specific minigame needed a high refresh rate to work properly.
Launch options: gamemoderun MESA_LOADER_DRIVER_OVERRIDE=zink %command%
Adding mangohud as in "gamemoderun mangohud MESA_LOADER_DRIVER_OVERRIDE=zink %command%" will allow you to check if Zink is running. MangoHud should say ZINK if it is.
VKD3D_FEATURE_LEVEL=12_2 VKD3D_CONFIG=dxr,dxr11 RADV_PERFTEST=rt %command%
Running with the given launch options and Proton Experimental, I found that I had no crashes or performance issues compared to the regular Metro Exodus. With EE on Proton, I get about 60-80 or so fps on Ultra at 1440p. Hairworks and PhysX disabled but Tessellation on and RT at Ultra. It's a fairly significant visual difference compared to Exodus. Performance is quite consistent as well. With Exodus on Heroic, I used Wine-GE-25 and then Proton Experimental, but I had to disable all RT effects to make it function but still encountered crashing and performance issues. If anything changes regarding stability, will revisit this post.
Installs and Starts but won't load
Game installs and starts up in GEProton8-21, Proton8.0.4, and Proton Experimental but as soon as the EAC loading splash screen appears, it loads for a bit and then crashes.
MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 MESA_VK_DEVICE_SELECT=xx:yy.z gamemoderun %command%
Recent updates may have caused an issue where the default GPU is the integrated GPU instead of the discrete GPU. This caused graphical corruption and artifacting as well as the game being slow in menus and running at extremely low framerates. To avoid this, instead of disabling the iGPU in BIOS, follow this guide: https://www.reddit.com/r/linux_gaming/comments/16tqql7/how_would_i_disable_my_nvidia_gpu_for_a_specific/
In summary:
- Ensure you have the mesa device selector package installed.
1a. A quick way to check is if you can run "MESA_VK_DEVICE_SELECT=list vkcube" or "MESA_VK_DEVICE_SELECT=list lspci"
1b. Cursory research indicates this is default as of Mesa 20.1 or thereabouts
- Find the appropriate device you want to use and note the PCI device ID on the left.
2a. It should say something like "VGA Compatible Controller: xxxxxx" where xxxxx is the name of the GPU in the description to the right of the device ID.
2b. Copy the PCI device ID. It will be something in the format of xx:yy.z
- Input MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 MESA_VK_DEVICE_SELECT=xx:yy.z as Launch Options in Steam for that game along with any other options you want.
3a. It should then be running on the dGPU instead of the iGPU.
3b. EXAMPLE: MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 MESA_VK_DEVICE_SELECT=xx:yy.z %command%
No launch options, just started up the game and played a match to test. Game started without any problems and ran OOTB. Max settings at 1440p I think I was hitting between 100-130fps with no RT and no FSR. Didn't crash during playtime.
gamescope -W 2560 -H 1440 -w 2560 -h 1440 -r 120 -o 45 -b -f -- %command%
Note: I purchased the Gold Edition to play early before the 9th. Despite having EAC, it basically worked out of the box. Quitting required a force-close from Steam. To prevent the AC from triggering, information I have read suggested that turning off cloud saves, Steam Overlay, and crossplay and wrapping the game in a gamescope session would work. It seemed that it worked as I had no problems starting the game and playing the campaign. I only played for about an hour and did not unlock the online PvP or co-op PvE if it is available during this pre-release time. I did not try playing online so I do not know if co-op campaign functions as of yet on Linux with the anticheat. To reiterate:
- Turn off Steam Overlay
- Turn off cloud save
- Turn off crossplay once in-game
- Wrap in gamescope
That should allow the game to run and the AC to function without kicking you out.
Occasional white flash in during character creation. Some videos had momentary white blocks in small areas of the screen. Less of a problem or an annoyance than it sounds.
Out of curiosity, I wanted to try Wo Long with Experimental since it's more or less the same engine as Nioh 2, Team Ninja's previous game. Running current Experimental with Nioh 2 finally fixed video playback as far as I could tell so I wanted to test if Wo Long was also affected. Pleasantly, it works out of the box with the current version of Experimental. Videos play normally (with only a minor, uncommon artifact) and the framerate runs at the cap 100% of the time on my setup at the highest settings (120fps). The judgement on videos playing was based on roughly 2 hours of playtime. Note: if you don't want to use upscaling, set it to Bilinear and leave the resolution scale at 100%. It's dumb, but that's how to turn it off. Runs at or better than Windows.
