PlayableShow Details
Unknown
Just mapped few key shortcuts I missed on the gamepad
WINE_CPU_TOPOLOGY=2:0,1 %command%
Needed to limit the number of cores with WINE_CPU_TOPOLOGY, as others have already mentioned. Even with that, my fans started getting loud in some areas and weirdly enough also when talking to companions. Limiting the framerate is the only thing that keeps the fans nice and quiet.
Played the EGS version with DLCs installed.
Both native and Proton version work fine, but I needed to run the Proton version because this game uses an ancient version of Unity.
WINE_CPU_TOPOLOGY=4:0,1,2,3 %command%
The game has major performance issues due to using an ancient version of Unity. Fixed with WINE_CPU_TOPOLOGY See below.
You can make the game work perfectly, but it's in a bit of a weird spot. I think Obsidian didn't upgrade their version of Unity once since they started working on Pillars of Eternity and its toolset. The end result is that the game has some weird performance issues, that you can work around.
First off, despite being released in 2016, the Windows version only supports DirectX 9.0c. This is not a huge issue for this game, but it is rather stunning nonetheless. Second, this game version of Unity has huge performance issues. If you have a PC with a large amount of available threads (I have 12 cores and 24 threads), Unity's CPU scheduler will run into some serious issues and the game will have awful performance. This is simply fixed with WINE_CPU_TOPOLOGY=4:0,1,2,3, which will cause Unity to only see 4 cores, and schedule only across these 4. This fixes the performance issues, and this trick can be used in any game that has these older versions of Unity. I've used it in a lot of games.
You can probably perform the same trick for the Native version using taskset. The fact that you can do this in Wine/Proton with an environmental variable is rather nice though, and it's why I stuck with the Proton version.
Played the Epic version of the game installed with Lutris. I was able to play without any issue.
very infrequent black artifacts in the corner of the screen
I logged with my Paradox account and cloud saves worked between desktop computer and Steam Deck.
Almost all text is very readable if you adjust the font size in the menus, but a small amount of text is too small to be comfortable. I bound R1 to Toggle Magnifier, worked out great.
The game would occassionally bring my computer to a halt while I also had Discord open, but this may be a problem with Discord and not Tyranny.
While the native version runs great, I ran the Windows version using Proton. This was because I had prior saves from the Mac version of the game that were not usable by the Linux version for some reason. Outside of this, there's really no reason not to use the native port.
MESA_LOADER_DRIVER_OVERRIDE=zink %command%
Native runs OK, but I'm not bottlenecked on GPU or CPU so it really should be running better. GPU gets stuck at around 60-80% usage, depending on area. Fixed by changing driver to zink(!)
On a whim, I decided to try the OpenGL-on-Vulkan zink driver. And what do you know, the performance problems completely disappeared. Rock solid 165 FPS.
Native version runs decently, Proton version is unplayable
Native runs OK, but I'm not bottlenecked on GPU or CPU so it really should be running better. GPU gets stuck at around 60-80% usage, depending on area.
The native version runs OK (see above), but the Proton version is completely unplayable. Framerate constantly below 60, insane stutter, frequent dips to the 20s and even 10s... So just use native and accept the slightly lower than expected framerate. Doesn't matter that much in an isometric RPG anyways.
Нативная версия игры идет идеально.
Native runs on X11 smoothly just by clicking play, when not counting in the multi-monitor setup issues, like running on wrong display and wrong refresh rate. On Wayland the native starts with black screen, couldn't find any launch parameters to make this work but forcing the game to run via Proton seems to make it work on Wayland on correct monitor with correct refresh rate.
Saves were not found after switching from native to Proton, as one could expect, so switching in middle of a campaign might not be wise.
Works great out of the box
No issues spotted, installed, selected latest proton, played, beat the game without any problems.
WINE_CPU_TOPOLOGY=5:0,1,2,3,4 %command%
All the Obsidian Unity engine games have the same problem; They spawn a worker thread for each CPU core, but doesn't assign priority to them. This results in lower performance the more cores/threads you have.
Using the launch argument limits the CPU core count to 5, this results in very high performance. It could probably be lowered more.
Game works perfectly. No controller support, but track pad and back buttons make playing feel smooth.
(GOG version) Works good
Played GOG version with Proton 7.0-1.
