Fubarberry

KDE defaults to Wayland on most distros now, so it might be worth confirming.

You can run

echo $XDG_SESSION_TYPE

to find out.

Are you using X11 or Wayland on your PC? Steam streaming from X11 works fine, but streaming from Wayland is really finicky or doesn't work in my experience.

I was fortunate enough to get a Huaying fan thankfully. Buying those early LCD decks felt like gambling with the fans tbh.

I put everything on Proton Experimental all the time, and only change to an older proton or GE if I'm having a specific compatibility issue.

I know people have managed to do this manually for awhile now, but honestly it sounded like more trouble than it was worth, especially when many people can just toggle on a wifi hotspot on their phone.

This is great though, finally a nice user friendly option.

Some games don't get any performance increase, so you'll have to try it game by game. So far most games I've tried have worked, but maybe I've just been lucky.

Nightreign only supports 1 or 3 player modes, the mod lets you play with just two players.

As a somewhat busy adult with work and kids, finding time to play together with friends is kinda hard. We have some set times a week where we try to play together (but we have more than 3 players) and we often squeeze in 2 player game sessions when possible. Nightreign only supporting exactly 3 players for multiplayer didn't really work for us.

Nightreign (to be clear, "ELDEN RING NIGHTREIGN" is the actual official name)

This same workaround is possibly needed for the seamless coop mod in the original Elden Ring as well, but the app ID would need to be changed to match that game.

So for original elden Ring the launch option would probably be:

SteamAppId=1245620 SteamGameId=1245620 SteamOverlayGameId=1245620 %command%

I 100% had this issue, I could watch the combined memory climb towards 17GB over a play session, and when it got close the system would lock up. This was on an LCD deck, and I was targeting a 30fps with some of the graphical texture settings on high iirc. Some people reported being able to play the game fine, and my best guess is that they were targeting a higher frame rate and had graphical textures turned down. Since the memory leak would eventually stop growing, it's possible that with low enough settings you might be able to stay under the crash threshhold.

The other possibility is that since it only would crash after playing for awhile, that short play sessions might let you get through without issue. The length of the sessions before a crash would probably be longer the lower your texture settings.

I'm assuming you're talking about Cryobyte increasing swap size, which was actually necessary for some games. God of War for example has a memory leak on devices with an integrated cpu/gpu (so handhelds and most laptops), and it would cause a full system lockup and crash after 30min-1hr of playtime. The memory leak would eventually stop around 17.5-18.5 GB of total RAM + VRAM used. Increasing swap file size would let the game run without issues or crashes.

That specific use case shouldn't be needed anymore since Valve switched SteamOS to use ZRAM instead of traditional swap.

That sounds like an abusive relationship.

Thanks for sharing, that's a great additional bit of info on this whole thing.