
Azsorlex
Published
Phenomenal performance. Even better performance than native and even Windows! My GPU usage was able to get up to 99%; can't say the same for the other two options. On almost ultra preset (ultra preset but with trees turned down to High), I experienced constant 60fps in open areas, and in urban areas, 45-60fps on average with quick drops to 30-40fps, especially when loading in things. I also tested with 4.11-2 to see if there was a performance gain, but the results were a mixed bag.
Great for those that don't like multiplayer. You're better off using native.
This may not apply to everyone, but the foliage constantly flickered whenever I moved around on my Odyssey G7 on both native and Proton versions. I resolved it by disabling Adaptive Sync in my monitor's settings as well as v-sync in-game.
Closing the game either doesn't completely stop it, or it just hangs on the main menu but with only the background visible and the music playing. In both scenarios, you have to click the "Stop" button in Steam.
EAC doesn't work, but you can still connect to unprotected servers just fine, though it isn't practical since the vast majority of servers are protected.
Game would crash frequently during gameplay. Using Proton Experimental reduced the crashes, but it would still crash a lot. Didn't encounter any freezing upon quiting as other reports have filed.
Couldn't launch the game without the c1 launcher. The frequency of crashes wasn't enjoyable, especially if the game hadn't saved for a while. Tried other tinker methods in the other reports, but they didn't help at all.
Runs well
Alt-tabbing will switch to windowed mode.
Only experienced one crash during my time playing.
PROTON_NO_ESYNC=1 gamemoderun mangohud %command%
If motion blur is set to "Enthusiast" there are black squares on some trees while moving the view. Lower to "Gamer" to get rid of those.
I did encounter one random crash, but I don't know if that exact same error would've occurred on Windows as well. I didn't play much multiplayer since there was hardly anyone else, but besides that one crash, I didn't encounter any errors in-game.
Runs perfectly, minus the audio crackling
Audio crackles whenever there's a lot going on. Trying some of the launch options given from other reports only made it worse.
I used these launch options to fix a memory issue mentioned in other reports as well as skip the unskippable intro sequence: __GLX_VENDOR_LIBRARY_NAME=bla %command% +com_skipIntroVideo 1
Screen swapping while fullscreen results in the screen being blackened and requiring a forced closure. Can be fixed by using Borderless Windowed mode instead.
Two issues here. First: whenever performing executions on the Gladiator, the FPS would drop down to 60fps. Not an issue on a 60hz monitor, but it definitely is on a higher one. Second: Raytracing performance. RT is currently a bit weird in this game in general. Whenever enabling RT in the settings while in-game, the performance was abysmal (I got anywhere between 10-40 fps depending on what was happening), and whenever enabling RT from the main menu and then entering the game, it would crash with "Failed to allocate video memory" (whereas this didn't happen on Windows). I got RT with the Ultra Nightmare quality preset working properly on both Windows and Linux by setting the overall quality setting to LOW while leaving RT on, closing the game, starting it back up and then setting the overall quality back to Ultra Nightmare. Believe it or not, RT performance is better on Linux than it is on Windows, which is extremely impressive considering I was using an out of spec driver.
The only time I experienced a crash was when having RT enabled as described before.
The port works great, however the DOS version doesn't start at all. It starts for a moment, but then crashes.
I encountered a crash at one point ~3 seconds after loading a save state.
After completing Map 6 (I think it is), there's some story dialogue. If you don't skip it and then try to continue, it will either take a long time to begin the next stage or not respond at all. The quick way of getting around this is to skip it ASAP.
gamemoderun %command% +com_skipIntroVideo 1 +com_skipkeypressonloadscreens 1
Fixed by running the following command:
pw-metadata -n settings 0 clock.force-rate 48000 && pw-metadata -n settings 0 clock.force-quantum 500
Launch options skip the various intros.
gamemoderun %command%
When playing singleplayer, there would be a small chance of crashing. I haven't been able to pinpoint the cause. As for multiplayer, it crashes a lot. More on that soon.
Sometimes when trying to join multiplayer, my game would immediately crash. It wouldn't matter how many times I retried after that point, it just kept crashing whenever I tried multiplayer. What temporarily fixed it for me was verifying the local files, which prompted EAC to be reinstalled on next launch. But I would have to keep this up whenever the issue returned.
Nothing too special has to be done to get this game running. It doesn't work out of the box, but all you have to do is select "Add a Non-Steam game to My Library..." under "Games" and select "Empyrion.exe" found in the game's files. Then you go into the properties of the newly added shortcut, SELECT EMPYRION.EXE AGAIN, and force the use of Proton.
A few things to keep in mind: 1. Don't use Exclusive Fullscreen mode; use Fullscreen Window instead. 2. 4.2-7 didn't allow alt-tabbing, but 4.2-8 does. Just make sure you press Escape before doing it, otherwise, the DPI will jump up to an insane amount (it can easily be fixed by pressing Escape). 3. There will be tearing since Empyrion doesn't have a vsync option, but it can be easily mitigated by enabling Force Full Composition Pipeline in NVIDIA X Server Settings. If you avoid/apply the points above, the actual gameplay itself runs perfectly. It's a shame that EAC doesn't work, but it isn't the root cause of the problem.
I played the game using Proton 4.2-9, but the last post intrigued me, so I tried out 4.11-2 as well. 4.11-2 does fix the black textures, but it doesn't fix the artifacts and introduces lag spikes. Just use 4.2-9 and add d9vk (https://github.com/Joshua-Ashton/d9vk/releases). Download the latest .tar.gz, extract it, and within the newly extracted directory, run these commands (without the square brackets):
Command #1: [ export WINEPREFIX=~/.steam/debian-installation/steamapps/compatdata/288470/pfx ] Command #2: [ ./setup_dxvk.sh install ]
Just make sure that you've run the game once and have Wine configured (by running [ winecfg ]) beforehand. After that, it runs perfectly.
Sounds happen roughly half a second after they're supposed to happen. This issue doesn't occur on Windows.
Game would not start out of the box. Fixed it by disabling the in-game Steam Overlay.
You'd be better off playing these two DLCs via the Unity remaster.
SteamDeck=1 LD_PRELOAD="" %COMMAND% -PSOCompileMode=1
Used the following command to fix:
pw-metadata -n settings 0 clock.force-rate 48000 && pw-metadata -n settings 0 clock.force-quantum 500
Default proton version results in the game freezing upon entering a match. Experimental helps a lot, but I still occasionally encountered a full freeze.
DXVK_ASYNC=1 gamemoderun mangohud %command%
Followed:
to modify TKGRAPHICSSETTINGS.MXML. I set the graphics to my desired settings, changed NumHighThreads to 0, NumLowThreads to 16 (to match my CPU threads), UseTerrainTextureCache and UseArbSparseTexture to true, and didn't touch the settings ever again. I noticed that setting NumLowThreads to 0 resulted in the file getting overwritten whenever the game is quit.At one point, alt-tabbing would cause my framerate to dip anywhere between 1-30, but I later noticed that was caused by lack of vram. I reduced the texture quality to high and didn't see the problem again. I wish the 3070 had more vram...
Works as expected (if you count the game's glitches/bugs and the occasional crash as "expected"). Basically, there are no Linux-unique problems.
Runs great out of the box with no tinkering required
Objects such as terrain on dry land, habitats, plants, and the Seamoth shortly after hopping out of it will appear laggy while the rest of the framerate/scene (such as held item) isn't impacted. Also tested on Windows and the same issue occurs. I'm running a high refresh-rate monitor, and it seems likely that Subnautica wasn't meant to run above 60fps. However, it is a minor issue, and the game still runs great overall.
Performance gradually degrades after long play sessions.
gamemoderun mangohud %command%
I applied the FPS limit adjustment according to the following guide, setting it to 240fps: https://steamcommunity.com/sharedfiles/filedetails/?id=804452438
At first it was buggy. NPC walk cycles were slow, dragons would freeze the game, but after some time it fixed itself and worked flawlessly.
The remaster runs almost perfectly. The DOS versions are another story.
After some time, the mouse movement would occasionally stop being smooth and instead jump by small amounts. Can be fixed by restarting the game.
Only for the two DOS versions. They only occasionally worked.
gamemoderun mangohud %command%
My entire computer would freeze, usually right after reaching the main menu, every time I fire up the game. No being able to alt-tab, no being able to force-close the game, not even the num lock indicator on my keyboard would change, that's how bad it was. At first I thought it might've been my CPU undervolt causing these freezes, but disabling it did nothing.
If you experience this level of instability, your best bet is to set up a Windows VM with GPU passthrough. I run War Thunder this way, there are no freezes even with my undervolt, and performance is great.
By default, there are serious audio problems, and the game crashes after a short time of playing. The fix is to add xboxdrv as a service (https://gitlab.com/GloriousEggroll/warframe-linux/wikis/Ubuntu-Install-Instructions), and add this launch option: ( WINEDLLOVERRIDES="xaudio2_7=n,b" %command% ). Only minor problems still exist after the tweaks, such as Ordis having a weird effect to his voice that isn't present on Windows, some sounds sounding quieter than they do on Windows, loading screens being a bit glitchy, and the low chance to freeze upon completing a mission. Still very playable nonetheless.
This post fixed the loading screen issue: https://github.com/ValveSoftware/Proton/issues/333#issuecomment-543211289 . Replace "eu" with "asia" for the Asia servers.