Yep, it's trying to run something on host Please don't ask for progress reports, that will only make it take longer. The solution for this will not be in this app, it will be in Flatpak and in pressure-vessel. So what's the recommended solution for this? Should we just sit still and wait for a fix The container setup used for Proton 5.13 has other limitations that we hope will be solved in future, even without Flatpak being in the picture: controller hotplug doesn't work, primusrun almost certainly doesn't work (I haven't actually tried but I'm fairly sure it won't), it currently requires a valid XDG_RUNTIME_DIR (any systemd system has one but sysvinit systems maybe don't), and I'm sure there are others. This is exactly the same problem as not being able to run native Linux games under the "Steam Linux Runtime" compatibility tool from inside the Flatpak app (it's the same container launcher being used), except that the arrangements for Proton add an extra layer of complication, because native Linux games don't run arbitrary setup commands before running the actual game but Proton games do.
#Rune 2 open beta not working code
Solving this needs new code in both Flatpak and pressure-vessel ( flatpak/flatpak#3797 is the Flatpak side). The code required to make this work is fairly elaborate, and is not currently compatible with Flatpak: the pressure-vessel runtime tool should eventually work with the Steam Flatpak app, but at the moment it can't. Proton 5.13 is the first version to run Proton in a container with a different runtime environment, instead of as a child process of Steam. Proton 5.0 is still available and still works the way it always did. At the moment there are no good answers: making complex things work together takes time.
0 kommentar(er)
