manually download it through steal tools. I did and it worked.

Same problem here. Still stucked in dxvk 0.94

Ok, let's see everything together:

• DXVK is still on 0.94 (as with Proton 3.16-6), but it should be newer as you can see in changelog for 3.16-7
• Into the breach fullscreen is not fixed (https://github.com/ValveSoftware/Proton/issues/2338), but it should be fixed as in changelog for 3.16-7
• Uplay is still not working (as with 3.16-6), but it should be fixed with 3.16-7

So to me it seems like someone did a mistake and built Proton 3.16-6 again, but named it 3.16-7.

Happened to me as well.

Steam said it was using 3.16-7 but in reality it was running on an older version which I noticed when using 'DXVK_HUD=version'.

Installing Proton from the tools menu worked around the issue.

Deleting the Proton folders also probably works around the issue but Steam then re-downloaded my entire games which is a lot of data and takes a lot of time.

Note that whitelisted games are usually running whatever version Valve testers used when whitelisting it, but even when I used the game specific settings to override that with 3.16-7, it was in reality still running on the old version until I applied one of the workarounds.

Ok, let's see everything together:

* DXVK is still on 0.94 (as with Proton 3.16-6), but it should be newer as you can see in changelog for 3.16-7

* Into the breach fullscreen is not fixed ([#2338](/issue/ValveSoftware/steam-for-linux/2338)), but it should be fixed as in changelog for 3.16-7

* Uplay is still not working (as with 3.16-6), but it should be fixed with 3.16-7

So to mee it seems like someone did a mistake and built Proton 3.16-6 again, but named it 3.16-7.

No, I think the issue is that the Steam-client doesn't update your Proton even though it says it's running the latest. Apply one of the workarounds mentioned earlier to get the latest version.

@Brisse89 Thanks, you are right. (Re)downloading Proton 3.16 from the tools menu fixed it.

My guess is there has been some regression in how the Steam client handles Proton updates after the zero-byte updates fix. This is probably a bug in ValveSoftware/steam-for-linux rather than a Proton bug.

Possible duplicate, or possibly related to this issue: https://github.com/ValveSoftware/steam-for-linux/issues/6045

I can confirm I also saw this issue, as did others on GOL and in our Discord.

Proton would not update, unless we installed Proton 3.16 Beta from the tools menu.

manually download it through steal tools. I did and it worked.

Where do I get "steal tools"?

Proton would not update, unless we installed Proton 3.16 Beta from the tools menu.

"tools menu" from "steal tools"? Where is the "tools menu"?

Sorry for delayed response.
It seems like client is unable to auto-download missing Proton files. PFB gist after removing proton python script;
https://gist.github.com/0x221E/34c5d5247928e43103b7ecb4da626760

On manual integrity verification, it downloaded missing files.