VerifiedShow Details
Unknown
Game was crashing before the main menu until I copied the launch command I'm using from someone else.
gamemoderun gamescope -w 2560 -h 1440 -f --sharpness 0.6 -- %command%
Very low FPS when not using full screen
When opening the map or the menu, the game seems to think the mouse is in a different position and the camera moves very fast
Controller Issues
PS4 controller triggers (R2/L2/L1) spun character had to change reg file to disable Hidraw so it defaults to SDL instead
in '~/.local/share/Steam/steamapps/compatdata/1245620/pfx/system.reg'
added below [System\\CurrentControlSet\\Services\\winebus]
"DisableHidraw"=dword:00000001
I've been having some issues with Elden Ring specifically, while all over games have been running flawless (Cyberpunk, Hearts of Iron, Sea of Thieves... to name a few). After much tinkering, trying CachyOS and EOS; trying all different forms of Proton versions (Experimental, Cachy, HotFix, GE, 10 Beta, 9, 8...) and all of them having the same issues of crashing at random times while playing Elden Ring; with an error of: "amdgpu: ring gfx_0.0.0 timeout" I found that Proton 7 worked but the steam overlay wasn't working, nor ray tracing. What has worked for me with my AMD 7900XTX is overclocking with LACT. Max GPU Clock: 3050 MHz Max VRAM Clock: 2700 MHz Power usage limit: 315w Thermal target temperature: 85*C
Originally tried ProtonCachyOS (on CachyOS) which worked for many hours, until it didn't. After a lot of tinkering and small changes, couldn't get it to be stable anymore (freezing randomly anywhere from 30 seconds to 3 minutes into playing). Reformated and installed EOS, same issue with Proton Experimental on new EOS install. Went to Proton 9.0-4 and is working successfully with no issues so far.
Works right out of the box!
I needed to do nothing to get it up and running
gamemoderun mangohud gamescope -w 2560 -h 1440 -f --sharpness 0.6 -- %command%
gamemoderun → Enables GameMode (performance optimizations)
mangohud → Enables MangoHud (performance overlay)
gamescope → Runs the game in a nested Wayland session
-w 2560 → Sets width to 2560 (upscales from 1080p to 1440p)
-h 1440 → Sets height to 1440 (upscales from 1080p to 1440p)
-f → Enables fullscreen
--sharpness 0.6 → Applies 0.6 sharpness to scaling
-- %command% → Executes the game with these options
mangohud %command%
In fullscreen it takes a lot longer to fully close the game.
The only problem I encountered was, if I wanted to play with controller I had to do some Arch-Tinkering, as I am playing with a DS4-Controller and the touchpad is detected as a mouse-input:
Create a new udev rule:
edit /etc/udev/rules.d/72-ds4tm.rules
and insert
ATTRS{name}=="Sony Interactive Entertainment Wireless Controller Touchpad", ENV{LIBINPUT_IGNORE_DEVICE}="1"
to connect the controller via USB.
[!NOTE] Insert the correct name at "Sony Interactive Entertainment Wireless Controller Touchpad" you can get the name from
sudo evtest
A little bit slower than on windows
I used Proton 9.0.4 at first. But when I reached the first site of grace and interacted with it, the game instantly crashed and crashed the whole desktop with it. Then I switched to experimental and It worked flawlessly.
I had a tiny problem, I had just switched to Linux and installed Steam. I wasn't able to run the game, however, no matter how many proton versions I tried or wtvr. Then I ran steam from the terminal with the following command:
$ STEAM_DEBUG=1 steam
I didn't install Elden Ring on my OS's disk, I installed it on my HardDrive, that was a NTFS partition, so this was always showing up on the terminal: $ '/mnt/sda2/SteamLibrary/steamapps/compatdata/1245620/pfx' is not owned by you
Turns out, I had to change my disk's partition to Ext4 (cause Proton expects this type of partition and not NTFS), and after reinstalling Elden Ring on that same partition it worked flawlessly without any tinkering! I'm so glad to where Linux has gotten :)
mangohud %command%
Had to remove "gamemoderun" from the launch options, otherwise I got a white sceen and then the game would crash. But now it works pretty much out of the box.
game-performance mangohud PROTON_ENABLE_WAYLAND=1 WAYLANDDRV_PRIMARY_MONITOR=DP-1 PROTON_ENABLE_HDR=1 DXVK_HDR=1 %command%
Very washed-out and dim HDR with xwayland but works great with winewayland
HDR works only in fullscreen (sadly no 4K HDR in borderless but still looks great at native 1440p), when using winewayland I'm sometimes getting short white flashes when something happens on the desktop or my game is unfocused
Steam Overlay/Input doesn't work with winewayland, it's an Xorg application
The game on Steam doesn't fully close when using winewayland, have to kill it manually from the Steam UI
GPU overclocked to 2700 MHz, VRAM to 2500 MHz and undervolted by 125 mV using LACT
Game runs great out of the box, flawless experience.
Game runs great out of the box, flawless experience, maybe 3-4 fps lower than windows on occasion.
Game completely borked; no one knows why. White screen, then crash.
The game worked until it stopped working. First I tried running the game with default settings, but anticheat failed to start. After limiting the logical core count, the game starts, shows a white screen, and then crashes. I checked plenty of Proton versions (including GE), removed the prefix, reinstalled Proton, and reinstalled the game. Nothing resolved the problem. The game is completely borked as of now, despite working a few months ago.
It would be better if you could make the text like %50 bigger but its not that bad
No real major problems, runs around 40-45 fps with medium - high settings. I have a decent pc but i still prefer playing it on the deck.
If "volumetric quality" is set to anything other than maximum, fog that's rendered over everything is frequently on screen
When on a different application for 10-15 seconds it would be disconnected from the game servers and kick me to the main menu due to "frate rate issue"
Slight rendering and window issues, otherwise amazing experience
Works ootb no tinkering
Plays like a charm, modding is possible and not anymore weird than on Windows
mangohud %command%
Added stability on Linux systems due to how VK3D handles shader caching.
LD_Preload="" MANGOHUD=1 bash "/home/daniel/.steam/steam/steamapps/common/ELDEN RING/elden-proton/elden-proton.bash" %command%
Works very solid with elden-proton features like unlocked FPS, but only in borderless window
PS5 Controller not working. Workaround -> Steam Controller Settings Desktop set to Controller
Should be more, because of my setup. Windows was more performant
Long freezes with specific Applets. Removing QRedshift, Spices Update or CPU Temperature Indicator fixed it
Steam Overlay would get stuck on the EAC anticheat window when launching the game, so when the actual game launches the overlay is gone. I switched to Proton Experimental from 9.0.4 and that solved the issue.
WINE_CPU_TOPOLOGY=8:0,1,2,3,4,5,6,7 %command%
EAC launch issue solved by limiting WINE to less than 40 logical cores. You can increase the number of logical cores to 16 (or higher) using this format:
WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 %command%
Base game + DLC runs flawlessly once this is done.
Played 60 hours on linux - no issues
As title says, played 60 hours on linux with no issues. When i first played i had an issue with the game detecting the correct monitor but i confirmed this was a system issue with hyprland/wayland (i needed to use xrandr to set a primary screen). Since then I have played 60 hours (compared to 80 on Windows). I was able to finish NG+ and NG++ without issue and also did over 100+ co-op summons. It was smooth sailing the whole time. Well, except for the times I died but that was a skill issue ;)
RADV_DEBUG=nofastclears
Requires RADV_DEBUG=nofastclears to not crash on RDNA1. Reported 3 years ago and still unfixed
Worked perfectly without touching anything
Immediately enabled borderless fullscreen when I started the game so I could switch between desktops without issue. Runs better than it does in Windows.
On hyprland, you can only get out of the game by changing workspaces. Additionally, there was a quirk where using "Return to Desktop" to end the game resulted in the game turning black, and having to kill the window with hyprland for it to fully close.
No major issues, running beautifully.
If alt-tabbed out for an extended period of time (>30 seconds) on fullscreen mode, the game detects it as a "frame rate" issue and proceeds to log you out back to the title screen.
I was able to circumvent this issue by playing in windowed mode or pausing the game in fullscreen mode before alt-tabbing out.
BETTER THAN WINDOWS!
in hyprland the game didn't detect the appropriate monitor at first, but I was able to update my hypr.config file to move it to the right monitor via windowrulev2 and then in game settings I was able to change the game to windowed (my preference).
Comparison between Windows/Linux:
- WINDOWS: I 'played' 120 hours on windows, but this actually was only 80 hours of gameplay because my game crashed so frequently and then took ages to load. This was even though my hardware met and exceeded recommended requirements.
- LINUX: I am using the same GPU but have since upgraded RAM and CPU. The game is loading much quicker and I have had zero crashes after 2 hours of gameplay. Game runs smoothly and as expected.
LD_PRELOAD="" %command%
Installed Reshade and FSR3
If online, switching workspaces/tabbing out will cause you to get kicked in fullscreen. Alternatively, you can use gamescope or play in windowed mode instead.
