Seeji
Published
gamemoderun mangohud %command%
I initially had graphical problems with the default proton, which was fixed by changing to ProtonGE. Later I found out that the issues were caused by amdvlk lib32-amdvlk drivers. Switching to vulkan-radeon fixed the problems completely. The issue was driver related, not proton.
Overall recommendable playability on Linux. Playable without tinkering. With tinkering performance is better. Check below for more info.
gamemoderun %command% --skip-launcher
Sometimes Alt+Tab changed aspect ratio, fixable with changing any graphical setting and hitting Cancel, ie. not saving changes. This revers aspect ratio back to normal.
Game ran and was playable without any tinkering. Running game with Gamemode had noticeable, albeit still minor performance benefit (biggest difference in 1% lows).
Running with High settings, some settings on Ultra, DLSS Balanced. Solid 60fps. Without gamemode and higher settings FPS averages around 60 but 1% lows are more noticeable.
--skip-launcher does not affect gameplay, using it only to speed up launching.
Tested both Vulkan and DX11. With Vulkan there are minor graphical artifacts at times, DX11 is more stable and better performance on my hardware compared to Vulkan. No graphical artefacts or problems when running DX11.
Had minor screen tearing at first with DX11. Fixed this by Disabling Vsync and setting a 60fps cap.
No noticeable input delay with DX11 contradicting some reports.
Works out-of-the-box, no tinkering needed. Performance is great and I have so far not encountered any bugs or errors.
Did I wake you up from your depression nap?
gamemoderun %command% --modded --launcher-skip --intro-skip --skipStartScreen
FPS is solid 75+ with raytracing (local and sun shadows on, other options off). No problems even with couple of mods installed. Had a single crash in 40h+ hours of playtime.
Tested extensively with Proton GE and Proton Experimental, both with and without using launch options.
Requires reading and tinkering, instructions on how to get this running are readily available. Read more below.
gamemoderun WINE_FULLSCREEN_FSR=1 PROTON_ENABLE_NVAPI=0 %command% --skip-launcher
Followed instructions here for winetricks xact and altering of game files; https://www.reddit.com/r/DivinityOriginalSin/comments/alrg6u/divinity_original_sin_2_de_on_linux_with/
Fullscreen was prone to crashing, windowed fullscreen works fine.
After fixing initial problems with tinkering there have been 2 crashes total in span of about 7 hours, both related to loading a save.
Without tinkering game crashed on initial loading screen. Without using command line options, I got the game running on Proton GE 7.55.
With PROTON_ENABLE_NVAPI=0, the game also runs on the newest Proton GE (8.14 tested) and Forced experimental.
I did Winetricks xact and altering game files when initially trying to get the game working. Haven't tried without it after noticing that nvapi=0 fixes crashing on newer proton versions.
FPS is quite solid 60, but it's prone to screen tearing even with vsync. I got the best experience by removing vsync and capping FPS @ 57.
All features are working fine, including Cutter R.A.C.E mode. Overall very enjoyable experience on Linux.
Slight stutter in situations like reactor exploding, did not affect gameplay experience. Had similar with Windows before using different less powerfull PC.
Tested on Fedora 36, EndeavourOs with laters patches and MX Linux 21.2.1(AHS). Did not notice any remarkable differences between the distros. Always used proton experimental and latest nvidia drivers.
gamemoderun %command%
Note: If r2modman does not work try adding --no-sandbox to r2modmans launch, more info on AUR.
Performance was on par with windows. No setting changes from default were necessary. Stability was comparable to windows.
