Quoting: bisbyxAnother Valve update that improves the EGS experience on linux

Last time in recent memory that Valve fixed a competing "alternative" launcher, it was Battle.net, a few months before Overwatch 2 came to Steam. Maybe some games are planning to bundle the Epic Games Store on Steam as their launcher? :cry: Certainly none from Epic (unless they're really suffering, which I hope they are, but keep them off Steam) but maybe this is a new strategy like with integrating EAC and EOS malware: Bundle the launcher with games on Steam to raise those player numbers.

I certainly hope this is not the case, and it just so happens a patch that fixed the Epic Games Store made its way into the 9.0 rebasing, but still.

EDIT: Scored out the "competing" word, no one competes with Steam and gets away with it. :grin:

View this comment - View article - View full comments

Very glad to see the Framerate Limiter fixed. All games were defaulting to 10fps and the max rate was set to 60fps with no 90 option available, and the limit wasn't doing anything anyway. I thought this was a bug with Preview so I switched back to Beta and it persisted. Now that it's fixed I can go back to Preview. :smile:

View this comment - View article - View full comments

Hadn't heard of this one until this article, picked it up and loving it!

The devs even left a tiny easter egg in the game files :wink:

View this comment - View article - View full comments

Quoting: Purple Library GuyWasn't tearing supposed to be a bad thing?

I'm in agreement, but some people want it for gaming/drawing tablet purposes for the lower latency. Personally I've been gaming on Wayland for almost 2 years and never really noticed any latency, and always played games on X11 with compositing on. I'm just curious to see it on Wayland.

Also, on Wayland, tearing only applies to fullscreen windows, and the protocol I believe supports setting/unsetting it per-window (some Wayland compositors support this as of very recently, Plasma has implemented this for Adaptive Sync in 6.1). On Plasma 6 though, right now it's all-or-nothing and it's controlled by a checkbox on the Display settings page. Or at least, my understand is that it was, but I haven't seen this workking yet! :wink:

View this comment - View article - View full comments

Has anyone been able to get tearing to work for fullscreen games/general applications? Not having much success, even with Adaptive Sync turned off too, but even on my two other displays without Freesync I'm not seeing any tearing with the option enabled in System Settings.

As far as I understand Xwayland and KWin now fully implement the tearing protocol, and Mesa 24 should have support for the protocol as well. Tried out `MESA_VK_WSI_PRESENT_MODE=immediate` as well for some DXVK games, but not having any luck. Same story with Gamescope using `--immediate-flips`.

Videos in the Steam Overlay when fullscreen have tearing but that's regardless of this setting and always in the same spot.

I'm not really interested in having in on practically, I'm just morbidly curious to see tearing on Wayland, either in games, fullscreen YouTube videos from a browser, or anywhere. :smile: Maybe there's a step I'm missing or something isn't quite ready to be enabled at the flick of a switch yet.

Although for what it's worth, I did try the "Enable Tearing" option on my Steam Deck with the same games to see if I could introduce some tearing, and still couldn't see it. Maybe my eyes just aren't too sharp :unsure:

View this comment - View article - View full comments

I gave up on Humble Choice a while ago. I was grandfathered in with the Classic Plan and eventually I had two months in a row where I already owned every game, so I gave up. Even since, all of the headliner games are games I already own or have already gifted.

I have a Steam Collection for games specifically gotten from Humble Monthly as it was known back then, and it has 363 games. I think I certainly got my money's worth at the time, but never regretted cancelling.

Not a great lineup again, maybe it's because I have 1,923 games in my library according to the Steam filtering dropdown but I feel like a lot of the games have not been as good as they used to be. Though back in the day at least, it was a good way to beef up your library if it was small!

View this comment - View article - View full comments

Quoting: Forgewe should really look into a competitor program to Epic's Free Money

I get where this comes from, but I disagree. Fighting exclusivity with exclusivity would make the PC gaming landscape worse. I don't just want games on Steam, I want zero paid third-party exclusivity (and that includes on consoles, hence why I don't buy from Sony).

I think Valve should stay out of the exclusivity game. Attract develoopers by having a good platform and showing that the Epic Free Money hurts in the long-term.

If Valve start buying exclusivity, they're no better than scumbags like Epic, Tomorrow Corporation (I say this with a Little Inferno profile pic, and an ex-fan of Tomorrow Corporation), and every other dev that buys into paid third-party exclusivity.

View this comment - View article - View full comments

Quoting: DerpFoxIs this version still compatible with X11

Of course, the Plasma X11 session is still receiving bugfixes too where possible. Just because the Plasma team are now able to recommend Wayland as the default, doesn't mean the X11 session is going anywhere.

Plasma runs on X11 and Wayland. They are two separate sessions; two separate packages. Existing installations using Plasma probably won't switch to Wayland, or if they do, then the distro did that and not the Plasma team, as there is still a Plasma 6 X11 session.

It's up to distros to choose what they make the default, and so far to my understanding, only Fedora and RHEL have plans to use Plasma Wayland as the default session, but I don't believe existing installations will be affected for either. If a distro makes Plasma Wayland the default, that should really mean for new installations only, when you select Plasma, the Plasma Wayland session will be selected as the default.

You are still free to install the Plasma X11 session though, and if compatibility is an issue, distros either won't default to Wayland, or will come out-of-the-box with Plasma X11 and Plasma Wayland.

So if you really have no interest in Wayland, and you find that your distribution has forced you to use Plasma Wayland, you should take that up with the distribution and not KDE, as KDE can only communicate that Plasma Wayland is now ready to be a default but they don't control what distributions actually do.

View this comment - View article - View full comments

I'm interested in this section specifically, which if I understand your article correctly, is a quote from Nintendo:

"to be clear, there is no lawful way to use Yuzu to play Nintendo Switch games, including because it must decrypt the games’ encryption".

Is referring to the firmware files you must supply to Yuzu (and Ryujinx afaik, another Switch emulator) in order to use it, or is there something else going on? My understanding was that a user should dump these from their Switch console, and that this is, at the very least, not illegal.

Someone a lot smarter than me could probably explain how much water this statement from Nintendo holds, and what Yuzu is doing wrong here.

I also wonder if Ryujinx is going to be subject to a similar lawsuit. Yuzu is more popular (and depending on who you ask, tragically so) so perhaps it caught the eye of Nintendo first, and Ryujinx right now is under some "security through obscurity". Unless there is something technical that Ryujinx is doing differently, if Nintendo's statement that there is "no lawful way" to use Yuzu does not carry over to Ryujinx.

View this comment - View article - View full comments

Quoting: whizseProbably missing the necessary Wayland libs in the steam-runtime container.

This sounds very likely. And in that case, I don't think even running wthout the Steam Linux Runtime could solve it (it's possible to do this by wrapping the launch command, but it is not a good idea) since I believe Proton is built against the same runtime. So therefore when Proton is being built it would lack the libraries, even if Valve did build with the Wayland flag.

Wine-tkg-git's Ubuntu CI builds don't have the Wayland libraries, and so they fail to build the Wayland backend ( Frogging-Family/wine-tkg-git/Wine Ubuntu CI#1920 [External Link] ). So I think what you said sounds very reasonable.

And probably if I had to guess, these libraries are missing because right now there isn't quite enough justification to build with the Wayland driver enabled. Not to dilute any of the fantastic work that has gone into making the driver as impressive as it is now (and getting it upstreamed in such a short timespan!) but it isn't complete yet, it's still a feature you have to go out of your way to enable to begin with too. Once it's more "default" I could see Valve at least allowing it behind a Proton environment variable if absolutely necessary ("PROTON_USE_WAYLAND=1" ? :grin:). Or maybe it would be something you have to disable, perhaps some games won't play nice with the Wayland driver for a while!

View this comment - View article - View full comments