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...
Noob question here, but what’s the benefit of moving an application like Steam to 64bit? I understand for memory intensive applications it allows for more memory usage (it was a big deal when Stellaris made the change) but does Steam often use more than 4 GB of memory?
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.
One of the benefits is only needing to have 64 bit libraries. With this change most people can drop their 32 bit stuff.
Bits are literally “binary digits”. So more bits means bigger numbers. The reason you get more memory, is because when the code says “put this data in memory spot (number bigger than 32 bits)” … you cant with only 32 bits. How do you represent that number.
Imagine that you want to put something in memory spot 150, but you only have 2 digits. You cant. Bumping it up to 4 digits, you can say “put this data in memory address 0150” and its fine. “bigger numbers == more addresses == more places to put stuff”
So anywhere you need a number bigger than 32 bit represents, you can either just use a 64 bit number, or do a bunch of shenanigans. Those shenanigans require extra calculations inevitably. https://en.wikipedia.org/wiki/2,147,483,647 If youve ever seen this number before, it’s probably because of a 32 bit limitation. It shows up all sorts of weird ways.
Bigger numbers here aren’t about taking up more space, just representing literally bigger numbers. “9999” only takes up 2x as much “space” as “99” but it repesents a number ~100x bigger.
One of the reasons Steam held out for so long was that a lot of the games they host are 32-bit only. Games are built by a company, many of which have gone belly-up, so rebuilding the game from scratch is impossible. Making Steam 32 bit even though it could be 64 bit is a really effective way to guarantee a large chunk of their legacy products will still run. In a lot of ways, because of the nature of the gaming industry, Steam has it worse than most package managers/app stores.
Remember that the portion of Steam users that use Proton regularly is less than 10%, if you include Deck users. That number is rising and is probably a major factor in the decision to switch, but it’s still a minority.
It still doesn’t matter for the Steam client. All it does is point to games and tell them to boot. The client itself doesn’t act as a compatibility layer so the 32-bit vs 64-bit game argument isn’t relevant
Noob question here, but what’s the benefit of moving an application like Steam to 64bit? I understand for memory intensive applications it allows for more memory usage (it was a big deal when Stellaris made the change) but does Steam often use more than 4 GB of memory?
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.
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?
Started writing a lengthy response, then came across this Wikipedia link which slamdunks it: https://en.wikipedia.org/wiki/64-bit_computing#Pros_and_cons 😅
One of the benefits is only needing to have 64 bit libraries. With this change most people can drop their 32 bit stuff.
Bits are literally “binary digits”. So more bits means bigger numbers. The reason you get more memory, is because when the code says “put this data in memory spot (number bigger than 32 bits)” … you cant with only 32 bits. How do you represent that number.
Imagine that you want to put something in memory spot 150, but you only have 2 digits. You cant. Bumping it up to 4 digits, you can say “put this data in memory address 0150” and its fine. “bigger numbers == more addresses == more places to put stuff”
So anywhere you need a number bigger than 32 bit represents, you can either just use a 64 bit number, or do a bunch of shenanigans. Those shenanigans require extra calculations inevitably. https://en.wikipedia.org/wiki/2,147,483,647 If youve ever seen this number before, it’s probably because of a 32 bit limitation. It shows up all sorts of weird ways.
Bigger numbers here aren’t about taking up more space, just representing literally bigger numbers. “9999” only takes up 2x as much “space” as “99” but it repesents a number ~100x bigger.
Sorry, I’m tired and rambling.
One of the reasons Steam held out for so long was that a lot of the games they host are 32-bit only. Games are built by a company, many of which have gone belly-up, so rebuilding the game from scratch is impossible. Making Steam 32 bit even though it could be 64 bit is a really effective way to guarantee a large chunk of their legacy products will still run. In a lot of ways, because of the nature of the gaming industry, Steam has it worse than most package managers/app stores.
I don’t think it works like that. 64 bit Steam can manage 32 bit games just like a 64 bit OS can run 32 bit games.
I’m not sure as that’s about Steam the client though not on Proton thus Wine, which I bet will keep on supporting 32bit apps.
Remember that the portion of Steam users that use Proton regularly is less than 10%, if you include Deck users. That number is rising and is probably a major factor in the decision to switch, but it’s still a minority.
It still doesn’t matter for the Steam client. All it does is point to games and tell them to boot. The client itself doesn’t act as a compatibility layer so the 32-bit vs 64-bit game argument isn’t relevant