Don't want to see articles from a certain category? When logged in, go to your User Settings and adjust your feed in the Content Preferences section where you can block tags!
We do often include affiliate links to earn us some pennies. See more here.
An interesting SteamOS update just before and now it's time for the Steam Client Beta! Valve have been putting in the effort lately for sure.

Here's the relevant bits from the changelog for us:
  • Updated STEAM_RUNTIME_PREFER_HOST_LIBRARIES logic to still prefer Steam Runtime libraries if they are more recent than the host system
  • Updated Vulkan loader in Steam Runtime to version 1.0.54, which provides all the extensions currently needed for SteamVR
  • Added support for shader cache management on supported drivers (Mesa 17.1 and NVIDIA 381.26.08 or 384.59). Shader caches for games launched by Steam are placed in separate folders next to their Steam Library folder and are deleted when each game is uninstalled, or when switching drivers or graphics cards. Individual shaders are tracked and catalogued by the Steam servers in preparation for distributing pre-compiled shaders. This tracking can incur slight additional bandwidth use. The system can be disabled by setting the environment variable STEAM_ENABLE_SHADER_CACHE_MANAGEMENT=0

They also fixed an issue with the Steam client becoming sluggish, if it couldn't connect to their error and crash-reporting servers.

The new shader cache system they have sounds rather interesting for sure. A lot of games have a slightly longer loading time on the first run (or whenever you update your drivers) as they setup a shader cache. You can also experience lots of stuttering in games when entering a new area, as it builds it up. It sounds like now, Valve will ship pre-warmed shaders for games. Useful for SteamOS, since they generally control the driver versions and it could help loading time and performance on SteamOS directly. It doesn't just affect SteamOS though, since this is in the actual Steam client itself. I'm sure if I'm wrong on this, you will happily point it out in the comments. Article taken from GamingOnLinux.com.
Tags: Beta, Steam
24 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
The comments on this article are closed.
24 comments
Page: «3/3
  Go to:

monsieursauce Jul 27, 2017
The Beta client does not work on my Arch. I switched back to the default one, no cutting edge changes for me sadly!
Phlebiac Jul 28, 2017
Quoting: Vash63This is probably: https://github.com/ValveSoftware/steam-for-linux/issues/5099
Just remove the config.vdf file and make sure not to save your password until that bug is closed.

Thanks for the link; the latest update there, about "pinning" libdbus, seems to work around it better than the other suggestions.
LinuxGamesTV Jul 29, 2017
Quoting: Phlebiac
Quoting: Vash63This is probably: https://github.com/ValveSoftware/steam-for-linux/issues/5099
Just remove the config.vdf file and make sure not to save your password until that bug is closed.

Thanks for the link; the latest update there, about "pinning" libdbus, seems to work around it better than the other suggestions.

Hey thx :) Yes this is the better way for me too.
omer666 Jul 29, 2017
Nothing happens when I opt into Beta, is it normal?

[Edit] Fixed by switching to German servers.


Last edited by omer666 on 29 July 2017 at 7:16 pm UTC
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.