From ArchWiki
Jump to navigation Jump to search

Runtime issues fixed?

From the January 19 Steam update notes:

Improved interactions between the Steam runtime and host distribution libraries, which should let Steam work out of the box with open-source graphics drivers on modern distributions. If using an older distribution or running into problems, use STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0 to revert to previous behavior.

I'm curious if this means that the steam runtime workarounds are no longer necessary. Can users who previously required runtime workarounds try running Steam via /usr/lib/steam/steam to see if you no longer have issues?

Silverhammermba (talk) 05:59, 21 January 2017 (UTC)

For me, games that require the native runtime (ie don't work even with the workarounds) are still the same. I don't currently have any that specifically needed the workarounds to check. Argymeg (talk) 17:37, 28 January 2017 (UTC)
That's interesting. Which games require the native runtime? I think that is a separate issue though, I think the purpose of the Steam update was to make the LD_PRELOAD hack unnecessary. Silverhammermba (talk) 21:58, 28 January 2017 (UTC)

Steam needs Python 3 to function properly

If you want to run games through Proton, you need Python 3. Tonij (talk) 00:59, 21 January 2019 (UTC)

Yes, see bug report: FS#61362. Lonaowna (talk) 11:51, 21 January 2019 (UTC)

No Hardware decoding with intel-media-driver

Just found out that with intels media driver for newer CPUs (Broadwell+), steam does no hardware decoding for Remote Play (despite mpv working well and vainfo shows no problems). When using the older libva-intel-driver (or rather lib32-libva-intel-driver), hardware decoding works again. One can switch between the two with:

export LIBVA_DRIVER_NAME=iHD # not working
export LIBVA_DRIVER_NAME=i965 # working

Anyone knows why? (Perhaps missing 32bit for intel-media-driver?) Stebs (talk) 10:30, 24 April 2020 (UTC)