Does it? What containerization does it use? I thought it was similar to wine, just a process pointed at a windows exe, and an environment to make the app think it’s running in a windows filesystem.
It’s a custom solution called pressure-vessel, which seems to be based on flatpak. You can read about it here. This is used to create a reproducible linux environment and has nothing to do with the windows translation layer. They run wine (proton) inside the container as you would expect.
There is a recent effort to port this solution outside of steam in the form of umu. As far as I know it’s in a working state but I don’t know if it’s at feature parity with steam, especially on the game-specific fixes front. The end goal is to be a universal launcher that can be used from all frontends, so that all windows games run reliably and identically regardless of which GUI you use to manage your games.
EDIT: welp, I just now noticed this info has already been posted by another user 🤷
Something internal. In order to run a third party app with access to the process (like headtracking), the only way I’ve found out to achieve that was to download a windows version of opentrack too and run it twice. One on Linux side, one inside the container and make them talk to each other via UDP
Does it? What containerization does it use? I thought it was similar to wine, just a process pointed at a windows exe, and an environment to make the app think it’s running in a windows filesystem.
It’s a custom solution called pressure-vessel, which seems to be based on flatpak. You can read about it here. This is used to create a reproducible linux environment and has nothing to do with the windows translation layer. They run wine (proton) inside the container as you would expect.
There is a recent effort to port this solution outside of steam in the form of umu. As far as I know it’s in a working state but I don’t know if it’s at feature parity with steam, especially on the game-specific fixes front. The end goal is to be a universal launcher that can be used from all frontends, so that all windows games run reliably and identically regardless of which GUI you use to manage your games.
EDIT: welp, I just now noticed this info has already been posted by another user 🤷
Something internal. In order to run a third party app with access to the process (like headtracking), the only way I’ve found out to achieve that was to download a windows version of opentrack too and run it twice. One on Linux side, one inside the container and make them talk to each other via UDP
Wow, I’m impressed you actually got that working. Sounds like quite a hack.
Yes it does.
https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/blob/main/docs/container-runtime.md
I believe there is a project to add a Steam independent version of it to Bottles, Lutris, and other proton guis.
https://github.com/Open-Wine-Components/umu-launcher
Ahh, I always wondered what “pressure-vessel” was. Thanks for the resources.