Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal. You can also buy games using our partner links for GOG and Humble Store.
We do often include affiliate links to earn us some pennies. See more here.

Two pieces of Valve news to cover this Tuesday morning including new updates to Steam Play Proton and an upcoming Vulkan extension to help deal with other APIs and porting.

Firstly, the Proton update. 5.13-2 RC has been announced which needs more testing, since the Proton 5.13 release was quite a big one and it's not quite ready yet as they deal with some known issues. If you wish to try the Proton 5.13-2 RC, you need to opt into the "next" Beta branch for Proton 5.13 on Steam like so:

Here's their tentative changelog for this Proton update:

  • Update vkd3d-proton to version 2.0.
  • Fix Assetto Corsa Competizione in VR mode.
  • Proton log directory can be configured with PROTON_LOG_DIR.
  • Fix Killer Instinct crash on exit.
  • Fix Risk of Rain multiplayer.
  • Fix games not launching in Uplay Connect, and Origin crashing when updating.
  • Fix mouse cursor in Mount & Blade II: Bannerlord.
  • Fix SpellForce crash on launch on some systems.
  • Fix very long load times in Warhammer 40k: Inquisitor.
  • Restore behavior of horizontal scrolling input from previous Proton versions.

The list may change over time once it goes through their usual QA, and there may be future builds pushed to it before Proton 5.13 is considered ready.

Additionally, it seems a couple of Valve contractors have been working on a new Vulkan extension. It seemed to have been accidentally pushed out to the Vulkan repository on GitHub a little early, and promptly closed mentioning a "Misclick". The extension is called VK_VALVE_mutable_descriptor, with the gist of it being to allow "much more efficient emulation of the binding model present in other graphics APIs for layering or porting purposes".

Article taken from GamingOnLinux.com.
39 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 came back to check 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.
6 comments

Spyker Nov 10, 2020
This 5.13 update has been really rocky for me. I still have to deal with a lot of regressions, like my optimus laptop not working anymore with proton titles, even when I come back to 5.0.10 now it seems broken (probably a mix-up with runtime libs as weel). I really hope they get it squared out soon.
Nanobang Nov 10, 2020
View PC info
  • Supporter
Somewhere among the recent Xubuntu, SteamPlay, Steam Linux Runtime, and Nvidia driver updates, Dying Light became unstable, crashing unexpectedly, sometimes after minutes, other times after hours. I used to play with Vulkan because it just ran better than native. I switched back to native a few weeks ago, hoping DL would become reliably playable again, but no luck.

I've resorted to firing up my Win7 machine for the first time in over a year to continue a playthrough with a friend. I don't have any real expectations this update will fix it, but deep down inside there is a sliver of hope that this will magically fix everything.


Last edited by Nanobang on 10 November 2020 at 1:01 pm UTC
DrDickGind Nov 10, 2020
Quoting: SpykerThis 5.13 update has been really rocky for me. I still have to deal with a lot of regressions, like my optimus laptop not working anymore with proton titles, even when I come back to 5.0.10 now it seems broken (probably a mix-up with runtime libs as weel). I really hope they get it squared out soon.

Yes Proton 5.13 handles somethings in the wineprefixes different: It creates symlinks instead of copying the files. So if you go back to on older version, the symlinks cannot be overwritten and nothing works anymore.

As a workaround you can delete the wineprefix for your game in $SteamLibraryDir$/steamapps/compatdata/
Start the game again, with an older proton version and all will be fine


Last edited by DrDickGind on 10 November 2020 at 6:24 pm UTC
ShinyaOsen Nov 11, 2020
More changes made

Quote-Risk of Rain 2 multiplayer lobbies should actually be working now.

-PROTON_LOG_DIR set in user_settings.py should be respected now.

-Atelier Ryza should be playable again.

-Incorrect colors in some videos should be fixed.
Corben Nov 11, 2020
Maybe also worth mentioning, Proton 5.0-10 got released. Before 5.0-10 was only available as a Release Candidate under the beta branch:

5.0-10:
    Added support for the latest Steamworks SDK.
    Added support for the latest OpenVR SDKs.
    Log directory is now configurable with PROTON_LOG_DIR.


Due to the changes made for 5.13, some things are now indeed different, e.g. MangoHUD doesn't work anymore ootb.
Also the containerization changed the behaviour of the wine prefixes, I had my config folder within the Beat Saber folder symlinked to my Dropbox, which totally doesn't work anymore. So for some games, I still perfer to use pre 5.13, for others (e.g. Drone Swarm) 5.13 is totally needed.
kokoko3k Nov 12, 2020
Quoting: DrDickGind
Quoting: SpykerThis 5.13 update has been really rocky for me. I still have to deal with a lot of regressions, like my optimus laptop not working anymore with proton titles, even when I come back to 5.0.10 now it seems broken (probably a mix-up with runtime libs as weel). I really hope they get it squared out soon.

Yes Proton 5.13 handles somethings in the wineprefixes different: It creates symlinks instead of copying the files. So if you go back to on older version, the symlinks cannot be overwritten and nothing works anymore.

As a workaround you can delete the wineprefix for your game in $SteamLibraryDir$/steamapps/compatdata/
Start the game again, with an older proton version and all will be fine

They should handle that cases differently, hardlinks if the filesystem is the same at least, symlinks in other cases and triggering the rebuild of the profile in the corner cases automatically.
Let's hope for the better.
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.