The Steam Client Beta has been updated with the following changes:
Steam Achievement SetsA new way to organize, track, and complete a game's achievements. Read more details in the announcement.
Games can now organize and group achievements for base game and DLC content
DLC achievements can be added via sets without breaking game completion
Completed achievement sets remain completed when new sets are added
Achievements and sets can be archived if they are seasonal or can no longer be...
The benefit to/for Steam itself is marginal. The benefit to the entire community is significant, because there’s now an entire metric shitload of obsolete 32-bit shit that can be safely deleted and forgotten for 95% of the Linux world and efforts can be focused on things that actually matter in the 64-bit world. The entire 32-bit ecosystem of libraries and system layers still had to be maintained and supported basically only for Steam’s sake, Steam was the only thing still using them for the vast majority of people. It’s not that Steam needs 64-bit, it’s that 64-bit is the standard now and has been for a long time, and Steam was the only thing that had no 64-bit version.
It’s kind of like cutting loose the anchor that the community has been dragging around everywhere for years for no purpose. It was a totally unnecessary effort that just caused suffering and added no value.
Unfortunately, SteamVR with Flatpak is busted unless you use something like WiVRn. If you try to use something like the Steam Link app on an Android-based VR headset to do direct SteamVR streaming, it won’t work on the Flatpak because of permissions.
Source: Been wishing I could use SteamVR on my gaming PC for a while without a third party solution.
Probably. It tries to run a .sh script on first launch as sudo, but fails. Even if you run it manually, it still didn’t seem to fix it. There is a bug report for it somewhere that’s been open for 2 years. Valve officially only supports the package version of Steam for SteamVR, not Flatpak, so it’s unlikely to get fixed.
The benefit to/for Steam itself is marginal. The benefit to the entire community is significant, because there’s now an entire metric shitload of obsolete 32-bit shit that can be safely deleted and forgotten for 95% of the Linux world and efforts can be focused on things that actually matter in the 64-bit world. The entire 32-bit ecosystem of libraries and system layers still had to be maintained and supported basically only for Steam’s sake, Steam was the only thing still using them for the vast majority of people. It’s not that Steam needs 64-bit, it’s that 64-bit is the standard now and has been for a long time, and Steam was the only thing that had no 64-bit version.
It’s kind of like cutting loose the anchor that the community has been dragging around everywhere for years for no purpose. It was a totally unnecessary effort that just caused suffering and added no value.
I can probably disable multilib repo soon, which is nice.
I just installed from Flatpak for years now. No multilib headache.
Unfortunately, SteamVR with Flatpak is busted unless you use something like WiVRn. If you try to use something like the Steam Link app on an Android-based VR headset to do direct SteamVR streaming, it won’t work on the Flatpak because of permissions.
Source: Been wishing I could use SteamVR on my gaming PC for a while without a third party solution.
Did you try and app like Flatseal for customising Flatpak permissions?
Yeah that fixes some things, but there is a sudo command it tries to run that has some sort of pathing issue in the Flatpak version.
Sounds like a bug to be reported :(
Is it less up to date than other versions they have?
There is already a bug report. It’s been open for two years.
Valve doesn’t support SteamVR for Linux in Flatpak or Snap
Can you not just allow those permissions?
It’s deeper than that. It tries to run a function with sudi that fails every time, but the prompt for a password never appears.
Ah, I see. So it must need some library installed via Flatpak as well, that provides that prompt, right?
Probably. It tries to run a .sh script on first launch as sudo, but fails. Even if you run it manually, it still didn’t seem to fix it. There is a bug report for it somewhere that’s been open for 2 years. Valve officially only supports the package version of Steam for SteamVR, not Flatpak, so it’s unlikely to get fixed.
What is “sudi”? I assumed you meant sudo at first. 😅