gw4yn
Published
Very difficult to play the game, frequently boots to a black screen
Game only very inconsistently can be played, often has a black screen
Overall, a pretty bad native port in its current state. Needs attention from the devs. Proton version is flawless.
Open ~/.config/unity3d/Ludic/Akane/prefs in an editor, and change "Screenmanager Resolution Use Native" to 1.
Minor graphical glitches
Fails to detect display's refresh rate, always defaults to 60hz.
Connecting a gamepad crashes the game, with Steam Input enabled or not. Tested with Dualsense controller.
Since transitioning from Origin to EA App this game has become nigh unplayable, and issues are impossible to diagnose most of the time.
Slight performance downgrade, I'd say around 15% less frames
EA app often complains about cloud save discrepancies, which leads to hung processes after closing the game, even though as a Steam game it should not interfere at all.
Overall, the EA app (which replaces Origin) causes problems either opening or closing the game 2/10 times, and is a massive pain in the ass to diagnose, due to the window not being properly rendered. You're greeted with a black box which prevents you from opening the game.
Lack of ping on Proton >=7.0.4, will cause you to be kicked from most servers. Experimental fixes this issue.
EA ocassionally randomly disconnects when quitting matches.
Formerly a Gold Proton title that ran mostly without issues once you fixed the ping. The Punkbuster disclaimer is a little misleading, the real culprit is the EA App which constantly breaks for no reason, failing to launch, or forgetting your credentials, seemingly randomly.
It's completely inconsistent and impossible to predict if you're going to be able to play. This does not deserve Gold in its current state.
Good experience on the (as of yet) experimental Linux build. Much better performance in most scenarios, specially traffic. Lots of potential
Linux experimental build through "add non-steam game to library"
Missing PBR textures. Known issue with a known fix. See other reviews
WIndow would freeze when attempting borderless or fullscreen
Attempting to save custom vehicles crashes the game. Disabling preview solves this
Game will occasionally crash, more frequently than the proton version likely due to memory, but still relatively infrequent
Window must be moved in some way for the game to start loading. Game will freeze for more than a minute while loading bigger maps. Changing certain graphics settings can crash the game.
The proton version is more stable, and is recommended for people with beefier PCs, but performance is downgraded.
starting the game with a controller connected causes it to crash. definitely playable, but by no means "platinum"
starting the game with controller connected causes it to instantly crash. controller must be connected after the loading screen has already loaded
significant stuttering when first loading certain areas
crashes with controller connected
Game runs poorly on Windows. No multiplayer on Linux due to EAC. Difficult to recommend it as is.
Editing launch options didn't work for me. Instead I replaced start_protected_game.exe with a copy of eldenring.exe.
Windowed mode didn't scale properly, some elements were covered. Fullscreen if you use a permanent bar.
Controllers don't work
Game runs like shit overall (frequent stutters below 30fps) but that is mostly due to it being incredibly unoptmized in its current state, also happened to me on Windows. Slight performance decrease compared to windows.
Multiplayer disabled due to having to remove EAC
Game has improved greatly from its launch week, but still has stutters. Possible solution is to reinstall to delete the shader cache.
The game might be stuck at a low resolution if one tries to leave full-screen sometimes. Closing it and relaunching fixes it.
Controller not detected by default when EAC is active. Solution was to manually set the "gamepad" template in desktop controller options.
SDL_GAMECONTROLLERCONFIG="050000004c050000e60c000000810000,Sony DualSense ,a:b0,b:b1,back:b8,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b10,leftshoulder:b4,leftstick:b11,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b12,righttrigger:a5,rightx:a3,righty:a4,start:b9,x:b3,y:b2,platform:Linux," %command%
Unplayable with Dualsense (PS5) controller. Both triggers (dash & super dash) mapped to the same button as pause. Custom launch command solves this, but appears to also cause input lag.
Game launches but crashes a few seconds into beginning cinematic. Can't even see the start menu
Aside from connection stability issues which occasionally get you kicked from FOB missions, the game runs flawlessly.
Runs much better than Automata, probably because not as many polygons are spent rendering 2B's thighs.
Alt-tabbing sometimes causes the screen to freeze.
Some areas, specially ones where the camera is fixed, have very brief FPS dips below 40 irrespective of graphical settings, but it does not significantly affect gameplay.
Screen will occasionally freeze, game continues to run, actions can be performed, but the screen isn't refreshed.
Missing textures in practically all the signs where the button layout would be. Possibly also an issue on Windows.
There are a handful of rooms in the middle of the game where the framerate drops below 30 fps, despite average 200+ fps elsewhere.
The native version was so unstable I couldn't get past the first section, the game would crash at least once after nearly every checkpoint. The tutorial signs were also not being rendered. There may have been other issues but I didn't stick to find out. On Proton 7.0-4 I was able to finish the entire game without a single crash.
Pretty much perfect OOTB, ran surprisingly well for my hardware, absolutely no stuttering.
Very mild crackling when 3d audio is enabled. Can't confirm it if also occurs on Windows, might be my hardware.
The starting area is very unstable, and shader compilation makes performance seem much worse than it is. Besides that, runs pretty well.
env VKD3D_CONFIG=dxr PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%
Floor textures ocasionally disappear or go black, specially in the starting area (village), require a reload to fix.
Weird input with mouse. Would aim and deaim randomly, even though right click wasn't released.
Frequent crashes in the first 1/3 of the game, making it difficult to progress without autosave, much more stable afterwards.
Siginifcant stuttering for the first hour of playing, presumably shader compilation. The rest of the game was buttery smooth.
Launch options copied from another report. Not sure if necessary.
Ironically, last update (which removed WFGL) appears to have broken the game.
Worked fine originally. Now it spends a few moments downloading new files, but then won't launch.
Works perfectly. Controllers can be connected and disconnected without any issues. Fantastic game too.
Playing wtih surround headhpones, audio seems VERY messed up, I had to turn the volume all the way down. Otherwise it's playable.
COMPLETELY borked audio. Tracks fade in and out randomly, music disappears, left-right balance changes constantly with heavy crackling in between, and there's a high pitched noise when hovering over the audio menu.
Several textures seemed completely colorless, hard to say how much of it is part of the experience.
Fullscreen by default, and it works fine. However the game kept crashing when manually setting windowed mode.
Unexpected frame dips in some cinematics
An excellent port.
Game crashes somewhat often, but the frequent autosaving makes this somewhat amenable.
Runs perfectly out of the box.
Audio very ocasinally out of sync. Hard to say if it's proton specific or just a bug in the game
