protonscr

Steam fails to detect existing shadercache when re-adding a Steam library

steamopen Steam client
ValveSoftware/steam-for-linux#7455 · opened 2020-11-06 by Saroumane · updated 2020-11-07 · 1 comments · github
SSaroumane 2020-11-06 github

Your system information

  • Steam client version : 28 Oct 2020
  • Distribution (e.g. Ubuntu): Ubuntu 20.04
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

Steam fails to detect existing shadercache when re-adding a steam library. The whole shadercache is re-downloaded (+background processing)

Steps for reproducing this issue:

  1. Pre-requisite : having 2 Steam Libraries ( in my case : the small default on the SSD where Steam is installed + 1 Library on a big HDD)
  2. For whatever reason, unmount the disk where the large Steam Library is located
  3. Quit and relaunch Steam : all games from the large library are missing. (That is expected)
  4. Mount the disk with the large library
    5 Quit and relaunch Steam. If necessary, add manually the large library. All games are detected.
    6 Steam does not detect the existing shadercache from the large library and starts to download-queue shaders for the whole library.

What is expected :

At step 5, I expect Steam to detect existing shadercache when he detects all installed games.

SSaroumane 2020-11-07 github

Possible workaround (thanks to https://github.com/ValveSoftware/steam-for-linux/issues/5717#issuecomment-722798797 ) :

  1. erase shadercache in the secondary library
  2. recreate it as a symlink ( ln -s target link ) to existing shadercache in main default mandatory library.

I'll test it and update here when the problem will arise.