delcake
Published
EAC preventing play via Proton
While the game installs fine, and even allows you to get through creating a character, you'll see at most first several seconds of the opening cutscene before an error boots you back to the title screen.
Tested on Proton 7.0-1, Proton Experimental, and Proton Experimental [Bleeding Edge].
Additionally, I noticed issues with the in-game web browser that handles account sign-in and another informational screen prior to character select. When the game is fullscreeened, these screens can appear entirely black until refocusing the window. But even then, serious flickering occurs. This can be mitigated somewhat by letting the game remember your credentials to bypass these windows on subsequent attempts, or by playing in windowed mode.
The various errors I've received are: 01-0005-0302-00 A connection error has occurred. 01-0002-0113-00 A session error has occurred. 01-0052-0062-07 Unable to send data.
None of these mention EAC outright, but given that none of these show up when accessing the game from a second machine running Windows it seems pretty clear that the anti-cheat is to blame.
After patch 1.5: If you have existing data in Steam Cloud and can't launch, try making a fresh prefix without it to get the game started.
All audio sources would crackle and stutter when taking combat actions. After a few moments the stuttering would resolve, even if holding down the fire button on an automatic weapon. This ended up being the result of pipewire-media-session's default configuration.
From the ArchWiki:
According to the official PipeWire troubleshooting guide, to solve this problem edit /etc/pipewire/media-session.d/alsa-monitor.conf, uncomment the line saying api.alsa.headroom = 0 and change its value to 1024.
Like most of the other reports after patch 1.5 came out, the game also refused to launch for me. I was able to resolve this by deleting the prefix at ~/.steam/steam/steamapps/compatdata/1091500 and then unchecking the "Keep games saves in the Steam Cloud for Cyberpunk 2077" option in the properties window.
As far as I can tell, the existence of my prior game saves and configurations that were done on a different system would cause the game to immediately error out on launch. But once you get a successful launch on a fresh prefix without prior Cloud data existing to get a working configuration file defined, you can safely re-enable and use Steam Cloud without problems.
Still some tweaks and fixing needed for this to be considered playable, but can technically be completed with cutscene skipping.
WINEDLLOVERRIDES="xaudio2_9=n" gamescope -f -H 1440 -h 1152 -F fsr -r 60 -- %command%
Per the suggestion at https://steamdeckhq.com/tips-and-guides/metal-gear-solid-2-and-3-working-on-steam-deck/ - providing a copy of xaudio2_9.dll and overriding is required to make it past the intro without crashing.
Major performance issues with playback of prerendered video in the later portion of the game. Skipping these cutscenes is required to avoid a crash. This unfortunately includes the lead up to the credits after completing the game.
As mentioned, cutscenes that cause the game to lag are capable of crashing the game entirely. Notably, the projector screens on the Tanker don't slow down the game but the image is distorted and will cause the game to crash if they are on screen for too long.
Gamespeed is tied to FPS, so I've utilized gamescope in my launch options to lock the FPS to 60. Without this, the game will be way too fast on modern hardware.
Smooth from launch through the first hour of gameplay. Easy as loading it up on the Switch, just at 2K and 165 FPS.
Play via Proton is now supported, but a bottleneck with terrain loading leads to stuttering any time the game loads more of the world.
As noted in other recent reports, significant stuttering is occuring during initial shader compilations and when loading terrain. In my experience, the severity of stuttering has been decreasing over time as my shader cache has built up.
As noted elsewhere, there is an unusually long load that happens when loading in to NGS that has a chance of erroring out with a server timeout if your settings are too high. Other reports recommend setting all graphics options to low to prevent this, but I've tested and found that the only setting that matters for this issue is Terrain Draw Distance.
Start Game -> Pick your Ship -> Support Menu -> Options -> Graphics -> Terrain Draw Distance: 1
Everything else can be set to Ultra, or the max value that your system can normally handle, and you'll still be able to load in without timing out.
No difference in online connectivity functionality from a native Windows installation now that nProtect has included Linux support.
Finally playable on Linux, even with maximum graphics settings as long as the terrain draw distance is set low. I suspect that an I/O issue needs to be addressed in Proton somwhere in the stack to keep terrain loading across an incredibly high number of files from hitching gameplay.
Some hands-on tinkering required to get it running, at least until the announced Linux native version arrives.
Launch option: PROTON_LOG=1 %command%
Only attempted with DualSense controller
In addition to specifying the PROTON_LOG=1 %command% launch option recommended here by others, the game would not launch properly until I moved it off of the NTFS drive I had installed it to originally. Make sure you run from an ext4 or other suitable partition.
