Steam itself runs its own sandbox, which would be non-functional with the Flatpak.

Steam itself runs its own sandbox, which would be non-functional with the Flatpak.

Please read upstream issue which i linked in OP. It completely functional already with new flatpak >= 1.11.1. F35 already contain flatpak 1.11.3.

Can your relocate the storage for Steam to somewhere else with the Flatpak yet? That was also a major problem (there are games that are >200GB!).

@ngompa you can left in place old Steam game library and it to Steam Flathub version. Without relocating and changing storage for games. Flatseal app should come in handy there. It's already whitelisted in F35 though. More accurate and detailed about this.

BTW maybe we can keep RPM Fusion version and add also Flathub version of Steam? Users might be able to decide which one they prefer.

The problem is that GNOME Software chooses Flatpak by default when there are multiple choices. That's why we don't include anything from Flathub we are delivering any other way.

I understand but sticking with something old when there is already something new and better feels really wrong and conservatism definitely not Fedora way.

It's not a question of "old" vs "new and better", it's a question of providing the user experience that gamers expect. Flatpak cannot do that right now with Steam.

Flatpak cannot do that right now with Steam.

Care to elaborate? Steam Flatpak already provide better experience then current RPM version. Many users suffer a lot because of issues which multilib introduce. Sometimes they can't update their system because of package conflict due regular repo desynchronization with rpm fusion, sometime much more deeper and nasty bugs.

Flatpak cannot do that right now with Steam.

Care to elaborate? Steam Flatpak already provide better experience then current RPM version. Many users suffer a lot because of issues which multilib introduce. Sometimes they can't update their system because of package conflict due regular repo desynchronization with rpm fusion, sometime much more deeper and nasty bugs.

This does not happen with the default setup in Fedora. I certainly don't experience this and I use Steam via the RPM and aggressively upgrade to new releases. The RPM Fusion Steam repository we offer only contains Steam. Not to mention, games being sandboxed under Steam also adds complications to folks using the NVIDIA driver because the ABI between the Flatpak runtime and the host environment differ. And Vulkan availability is simply not broad enough on Linux yet to work around this with Zink. Finally, there is no straightforward way for gamers to offload game storage to another disk, which is often necessary for enthusiasts because games are huge now. At least one game I have installed is 175GB, and I don't have many games installed that take up less than 50GB of space.

This does not happen with the default setup in Fedora. I certainly don't experience this and I use Steam via the RPM and aggressively upgrade to new releases.

Of course you certainly don't experience this because you live not in problematic region where broken and laggy mirrors usual thing. This reported soo many times in rhbz.

Not to mention, games being sandboxed under Steam also adds complications to folks using the NVIDIA driver because the ABI between the Flatpak runtime and the host environment differ.

Not true at all. Simon take care about Nvidia bugs in particular and Steam Flathub build. So basically Steam upstream supporting current Flathub build, which is not the case with RPM version. And being a long time Nvidia user i would say it worked perfectly with Flathub build for me.

And there is no any ABI complication. If .GL extension is differs from the host driver version - nothing works in Flatpak at all in such case. The fix is — flatpak update. And most important thing which need to say here — Nvidia users should blame RPM Fusion in this case since they don't wont to ship flatpak extension with their driver.

Finally, there is no straightforward way for gamers to offload game storage to another disk, which is often necessary for enthusiasts because games are huge now

I already previously posted link with step by step guide how to do this. This is trivial and basically no difference there between flatpak and non-flatpak build at all.

I think we should stick with current Steam RPM Fusion version. Yes, flatpak (Flathub) version have some benefits but it also have issues which Steam RPM Fusion doesn't have at all. Also flatpak performance issue still doesn't resolved and i don't see any active work on this.

It's really nice to have some additional security features for Steam like sandboxing since we talking about proprietary software, but Flathub is not solution. If RPM could one day add sandbox support it would be a win-win strategy.