Did you use some not official Proton version (like e.g. proton-tkg or other) or did you maybe remove some older Proton version from your Steam Library tools? I see similar issue and it's correlated to the compatibility tool rewriting its *.vdf file.
Hmmmm.
I do use custom Proton via https://github.com/Tk-Glitch/PKGBUILDS
So, deleting old Proton versions can cause Steam to think that game files are somehow corrupt?
To note, this has never been an issue previously, despite using proton-tkg for a long time, and having installed new versions, and deleted old versions, rather often.
So, deleting old Proton versions can cause Steam to think that game files are somehow corrupt?
Compatibility tool *.vdf file defines a mapping that informs Steam client which depots should be used to install/update the game. When using official Proton installed from within Steam this interaction seems to be polished and working correctly, but when an unofficial tool is used (or even Proton compiled locally), then Steam often gets confused about which depot should be used to run the game. Perhaps your earlier upgrades did not change the internal name of the compatibility tool in *.vdf file, so Steam client did not care to double check if depots changed.
Hmmmm.
Sounds like a bug I should report to the maintainer of proton-tkg, perhaps.
Mention me or link this issue, please - if proton-tkg maintainer will find better solution for this problem than me, then I would like to know ;) (I simply stopped including versions in the internal name of my tool, so Steam gets confused much less often).
Sure.
There's your link. :)
I have reported that to Plagman a while ago. If a game is bound to a proton version and you delete it, it's as if proton wasn't installed and your game will get nuked.
The "uninstaller" I'm offering shouldn't be needed in a perfect world but currently the Steam client doesn't have a fallback mechanism for proton builds.
I have never faced an issue again since I have pushed the uninstaller as long as I haven't tried to set a custom proton globally. Setting it per-game has been trouble free.
I'll add a note to a readme somewhere about that specific setting one should definitely avoid, but I'm convinced something has to be done on the Steam side. I think there was another issue open already regarding this, but I can't find it.
Another +1 to change how steam interacts with config.vdf. Would prefer if it could have a popup notification upon a games's config.vdf being 'incorrect' and stop a game from launching rather than just wiping the entire game from my library and trying to force a re-download. Real big pain when this & denvuo can make a game unplayable because it's been 'activated' too many times.
Hello, per "Fix race condition that could cause some Proton-enabled games to redownload" in the 2020-03-03 Steam client beta update, please opt into Steam's beta and keep an eye out for this issue.
Closing as fixed in the 2020-03-26 steam client update.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
For no apparent reason, Steam decided that it would do a full check on both Bayonetta, and Grandia II Anniversary Edition, and then somehow find them 100% mismatched, requiring deleting all of the files, and redownloading many gigabytes of data.
Steps for reproducing this issue:
Also, here's my content log:
content_log.txt