
begepotam
Published
gamemoderun %command%
Patch #4 broke Vulkan.
The patch #4 broke Vulkan. DirectX still works, but it has a bit less "polished" look and makes my cooler work more then Vulkan did. The problem with Vulkan probaly only affects for existing players that have got the update - removing the cache file makes it work again, so it shoudn't be too bad. Larian was helpful with that issue as well, see https://github.com/ValveSoftware/Proton/issues/4243#issuecomment-1809486323 and https://github.com/ValveSoftware/Proton/issues/4243#issuecomment-1810662257 So existing playes can fix the Vulkan rendering by going to ~/.steam/steam/steamapps/common/Baldurs Gate 3/Data/ and removing the file PsoCache.pak, it worked for me and for a few other users as well.
Hotfixes broke the game more than once
Just finished the game, the "core" game runs great, but there were issues with launcher and a few hotfixes. As far as I can tell they are all resolved now, the game requires (or did require) Proton Experimental though.
Texture streaming is problematic unless set to lower level.
Videos played in game will block progress unless fixed
The game needs some love to make things work.
First as already mentioned many times both mf-install and mf-installcab are needed. If not applied correctly the game might start without playing videos and would work up until a point where story progress depends of watching a video (in the very beginning of the game).
Then there's an issue with texture streaming, I did not have to disable it, setting it to low in the visuals options fixes it.
In the end I also had a problem that is specific to 8+ core CPUs, probably AMD Threadripper only: I had to set the CPU list explicitly, otherwise the mf fix did not work. Setting launch option taskset -c 0-23:2 %command%
(so basically almost all the CPUs) on my system fixed it. Here's the related issue https://github.com/z0z0z/mf-install/issues/44.
Works perfectly unless you try to alt-tab from it
Smooth performance with max settings.
Leaving the workspace with the game or alt-tabbing works sometimes, but mostly leads to not being able to resume.
Works perfectly on ultra unless Steam overlay is enabled
Steam overlay makes it unplayable
Always starts windowed
Game always starts windowed, for me the only way to get back it to full screen seems to be clicking reset settings.
The game crushes now and then, but setting PROTON_NO_ESYNC=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% as laungch options fixed it completely, didn't have a crush in 20+ hours. Also enabling antialiasing which was somehow off by default seemed to re-introduce crushes.
After the mentioned tweaks the game runs perfectly, I also can't complain about any performance issues cause of disabled esync.
Works perfectly after adjustments that were mentioned before, here's the script to do that:
#!/bin/bash cd 'path/to/Steam/SteamApps/common/Divinity Original Sin 2' rm -r bin.bak mv bin bin.bak ln -s DefEd/bin bin rm bin/SupportTool.exe.bak mv bin/SupportTool.exe bin/SupportTool.exe.bak cp bin/EoCApp.exe bin/SupportTool.exe
Works
Finished the game, having an additional launcher is mildly annoying but it works just fine. Exiting the game never worked for me - had to stop it manually (Steams "Stop" works most of the time) but it did not affect anything.
gamemoderun %command%
Any complaints I can think of are about this game being a console port, nothing is Proton related. The game runs perfectly on ultra without slowing down so far (over 100 hours in), multiplayer disconnected once or twice during that whole time and I had one crush, cause I forgot to exit the game and it ran on background for more then an hour.
gamemoderun %command%
It stuttered a bit, especially in the beginning.
Works fine, but I'd expect better performance out of the box, using game mode seems to make it run smoothly.
Works out of the box, but needs the max_map_count adjustments to fix the fast travel crushes issue.
Needed to set vm.max_map_count=1048576
, I've put it into /etc/sysctl.d/99-max-map-count.conf
. Without this adjustment the game works, but crushes on fast travel. The adjustment was based on this ticket: https://github.com/ValveSoftware/Proton/issues/6510
Fixed by setting the max_map_count
After applying the max_map_count I have played for almost 100h without any issues.
A bit of tweaking was needed, sound is not great, other than that I was able to finish the game with no issues.
Needed to adjust config as mentioned in below comments.
There are two problems: running this game with Nvidia hardware requires config adjustment, it is easily fixable, but still a tweak (for me just raising the preset did the trick). The other problem is the sound, it is not perfect, not game breaking either, I just ignored that.
gamemoderun %command%
It stuttered after initial load, does that from time to time.
Major stability issues that are not easy to fix. In my case I was able to make it work reliably by forcing Proton Experimental and switching to Directx11 via UI (launch option worked, but didn't fix the issue).
The tinkering part is not fun, crushes are quite bad, a few needed a system restart, I honestly don't remember last time anything was able to mess up the system so badly. Also the "feedback loop" is annyingly long - after changing something you start the game and wait for a crush which might happen right away or after 15min of playing, then repeat.
That said, after switching to Directx11 and Proton Experimental (it might be that only Directx is actually needed) it works fine, as it should.
Finished the game, never noticed any problems. There were a couple crushes (in 80+ hours) which is better then expected on PC anyway.
Just works
Almost finished the game with no issues except when you leave it open and after some time display turns off then it hangs and has to be stopped manually. Other then that everything runs smoothly, that includes alt-tabing and switching workspaces.
Worked without problems.
Exiting the game hangs and needs a manual stop, but it's not a problem since saving is not affected.
If using PROTON_USE_WINED3D=1 it gets slow at times.
Loading screen crash mentioned here, recently fixed in Proton Experimental. Another workaround is to use PROTON_USE_WINED3D=1.
The game is quite buggy, but I doubt it has to do with Proton. They release huge patches couple times a week, if you want stability wait a month or two.
This issue is helpful https://github.com/ValveSoftware/Proton/issues/5150
Looks good OOTB
I thought I need to install media foundation to be able to see the cutscenes, but it seems to work without any action on my part - the main menu background as well as a video on starting the new game were played correctly.
I've also played for a few minutes and it seems to run smoothly on ultra, no complaints.
I'll play more later, for now just wanted to make sure I don't have to return it - so far it is a very nice out of the box experience.
As many other big games, this one needs media foundation to work properly, but works just fine afterwards.
There is slight stuttering in some areas, barely noticeable. I assume it has to do with texture streaming but there is no option to reduce it.
This game does not require GE proton, it's just one way to get media foundation fix.
Another way to get it working is to apply both https://github.com/z0z0z/mf-install and https://github.com/z0z0z/mf-installcab to the native proton (example command WINEPREFIX="/path/to/steamapps/compatdata/XXX/pfx" PROTON="/path/to/steamapps/common/Proton X.X" ./mf-install.sh -proton
), for 8+ core CPUs set this launch option "taskset -c 0-15 %command%", otherwise media foundation will not work.
Crushes on switching to another workspace, otherwise seems to run perfectly, no tweaks required.
Seems to fix random crushes every now and then. Launch option PROTON_NO_ESYNC=1 %command%
That fixes the main problem - the game depends of media foundation (https://en.wikipedia.org/wiki/Media_Foundation) to play cutscenes which doesn't work out of the box.
To do that find the games installation directory (steam store URL helps with finding id) and if you never installed wine then you'd need to tell mf-install to use proton's wine by passing the path to proton as another environment variable PROTON
, it is also localed in steamapps as well as -proton option.
So the whole command from the directory where you cloned or downloaded mf-install script (https://github.com/z0z0z/mf-install) would look like that: WINEPREFIX="/path/to/steamapps/compatdata/973760/pfx" PROTON="/path/to/steamapps/common/Proton 4.11" ./mf-install.sh -proton
where "/path/to/steamapps" is mostly under .local/share in home directory.
Applying mf-install and disabling esync works and the game runs smoothly afterwards, as far as I can tell after playing for an hour.
The problem is that to use Proton's wine one has to read mf-install script so I tried to describe how to apply it.
Runs great out of the box
It runs fast on ultra, but it seems to make my computer hotter then it should, considering it doesn't have that many fancy visuals.
Except for some extra cooler work which doesn't seem necessary, I have no complaints.
Woks perfectly
I have set the FPS limit and borderless mode as per earlier reviews, never experienced any problems, 96 hours and ticking.