kasimir
Published
Some freezes, more so early on, mostly while crafting
The game has some odd optimization issues, but that's not specific for Linux, there are also various reports for Windows. There's a spot where I could pan across a coast line with no distinctive differences, yet halfway the coastline fps would drop from 80 to 40fps (average fps for me was 80fps, so very playable) and CPU utilization would shoot up, with GPU utilization dropping from 100% to 60%. Also, the default setting for motion blur and chromatic abberation will give you a headache and tax the CPU in busy places. It's more playable and performant to set those to 'low' or 'off'.
gamemoderun %command%
Occasionally, 'full screen' fills only 1/4 of the screen, setting the resolution in-game to something else and then back, fixes this
Microstutters due to shader processing
As noted by others, if you install & launch, you'll likely get a message saying UPlay isn't installed. You need to install it manually, via the terminal (command for your distro/computer may vary):
STEAM_COMPAT_CLIENT_INSTALL_PATH=~/.steam/steam STEAM_COMPAT_DATA_PATH=~/.local/share/Steam/steamapps/compatdata/812140/ ~/.steam/steam/steamapps/common/Proton\ -\ Experimental/proton run ~/.local/share/Steam/steamapps/common/Assassins\ Creed\ Odyssey/Installer_Resources/UPlayInstaller.exe
After that, it runs great. Perhaps because of my CPU (12th gen hybrid Intel), I had to run it through gamemode (gamemoderun) to have it run smoothly, otherwise the CPU would be taking it easy and cripple frametimes.
New remake runs great with Proton Experimental
The remake that was just released didn't initially work, same thing as with GLQuake previously: it quits even before the launch screen. But after specifically setting 'Proton Experimental' as compatibility tool it launches and runs fine. Everything works and it's buttery smooth. Now with the original music by Nine Inch Nails included, it's a fantastic way to re-experience Quake - on Linux!
gamemoderun WINEDLLOVERRIDES="winmm=n,b" MANGOHUD=1 %command%
Edited Prefs.json to sync the framerate with my monitor's refresh rate (see https://www.pcgamingwiki.com/wiki/Return_to_Monkey_Island#Enable_higher_framerates) and added a mod to remove the black bars on my ultrawide (see https://gameplay.tips/guides/return-to-monkey-island-ultrawide-fix-guide.html).
Runs great! I only noticed some choppiness and vertical tearing on the scrolls. When syncing the framerate with my monitor's refresh rate (changing the game config), it was a lot better.
Still there was some minor tearing on the sidescrolls. The game does not have a vsync setting, so I tried enforcing it from MangoHud or with launch options. Made no difference.
Then, I toggled the compositor and the problem was gone! Default behavior is to turn off compositing, but in my case (with KDE, so KWin) the compositor had to remain enabled. Now it's buttery smooth at 120 fps! (Also not a tough game at all to run on a decent GPU, typicaly 30-40% utilization.)
Proton 3.16-5 Beta: still crashes when entering a battle. Map runs OK, but has some serious graphics issues (shadows, effects, erratic FPS) when looking closely.
It is playable, but would you enjoy it if you'd had a top-tier GPU and it feels like 20-30 fps?
I've played this game before on NVIDIA hardware, and that GPU performed about 10% worse with Proton compared to native, while native introduced some choppiness, especially on the map. Now, with the AMD card, the native version is very choppy and performs significantly worse. On Ultra settings, I get 70 fps native and 100 fps on Proton. That's 30% less! And because of the choppiness, 70 fps feels more like 20-30 fps... On the other hand, the Proton version seems to suffer from random crashes so that's also far from ideal. To summarize: either is bad! I wish they'd update the native version to perform optimally with the newest AMD hardware.
