Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Somehow it's still an issue. Was a while ago now but somehow an update to dbus(?) broke Worms WMD and the publisher just never fixed it. The solution was to just run the Windows version in Proton which works fine.


I'm not certain, but WORMs WMD is a pretty old 2016 title that might predate a lot of these container runtimes being available to games other than Valve's own first party titles like Dota 2 and CSGO/CS2.

Also, Valve has recently insituted changes about how native titles work forcing existing native titles onto the scout 1.0 runtime and giving developers the ability to pick newer stable targets.

https://store.steampowered.com/news/collection/steam/?emclan...

> Native titles will execute in 'Steam for Linux runtime 1.0 (scout)' by default, instead of the legacy runtime environment. This behavior is consistent with Steam Deck and promotes better compatibility across all Linux desktop distributions. Note that this new feature can be turned off globally with "-compat-force-slr off" on the Steam client command line.

Its also the case that the original version of this that was bouncing around in the 2010s was more of a gaint shell script hack and it was possible for games to depend upon the host system in way which could break over time. Today it is utilising stuff in the flatpak ecosystem:

https://ftp.belnet.be/mirror/FOSDEM/video/2020/UD2.208/conta...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: