Support us on Patreon to keep GamingOnLinux alive. This ensures we have no timed articles and no paywalls. Just good, fresh content! Alternatively, you can donate through PayPal, Flattr, Liberapay or Buy us a Coffee. You can also buy games using our partner links for GOG and Humble Store.

The first Steam Play update for this year is out with Proton 3.16-7 beta

By - | Views: 26,106

Valve have pushed out a Steam Play beta update with Proton 3.16-7 now available for testing. Lots of fixes!

Not quite the huge upgrade many were expecting, most people thought Valve would be pushing ahead with a major update of Wine but this release still seems like a very nice update overall

Firstly, they've updated DXVK to 0.96 and FAudio to 19.02. This should hopefully mean quite a number of games will see improvements and begin working. Additionally, there has been some controller improvements, with Unity specifically mentioned for games like Subnautica and INSIDE.

As for bug fixes and other changes, here's what they improved:

  • Fix for fullscreen behavior in Into The Breach.
  • Fix for crashes in some d3d9 games on Mesa.
  • Fix for crash when launching certain games, including Path of Exile, the Bloons series, and the Naruto Shippuden series.
  • Fix for games with special characters in paths, including LEGO Harry Potter.
  • Restore previous functionality of the Uplay client.
  • New runtime option for old games that can't handle modern GL extension strings. Set PROTON_OLD_GL_STRING to limit the extension string length.
  • New runtime option to disable d3d10 support, PROTON_NO_D3D10.
  • Better support for games that use very old steamworks SDKs, including Lost Planet.
  • Fixed various problems with the build system, and added a new top-level Makefile to make simple builds much easier.

You can see the changelog here. Looks like it's going to be a fun weekend of testing ahead!

If you're having issues updating, you can select Proton from Steam's tools menu found when you hover over "LIBRARY" -> "TOOLS" and search for "Proton" then install "Proton 3.16 Beta". Seems many people have had issues with it not updating properly.

After some fresh testing, with a forced Proton update I can confirm Into the Breach fullscreen now works as expected—hooray!

Article taken from GamingOnLinux.com.
36 Likes, Who?
We do often include affiliate links to earn us some pennies. We are currently affiliated with GOG, Humble Store and Paradox Interactive. See more here.
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.
54 comments
Page: «6/6
  Go to:

Comandante Ñoñardo 19 Feb, 2019
The "Press space to continue" bug of Bioshock 2 Remastered continue in PROTON 3.16-7


I know there are workarounds suck using the button A of an xbox controller or use -nointro, but is not the same...
Is a WINE/PROTON issue that MUST BE SOLVED, because on my Windows 7 machine the game works out of the box.
Thormack 19 Feb, 2019
1xok
ThormackDoes it runs Elite Dangerous or we still need that unofficial Proton build?

Elite Dangerous runs under Wine/Proton? This is new to me.

Yea, you need to install an unofficial version, like I said:
https://github.com/redmcg/wine/releases/tag/ED_Proton_3.16-5_Beta

Enjoy


Last edited by Thormack on 19 February 2019 at 6:04 am UTC
torbido 1 Mar, 2019
etonbears
torbidoWhen I add non steam game, where is the prefix of these games?

Each version of Proton is a management wrapper for Steam-Installed games using a specific version of Wine ( including extension libraries/patches etc ).

As you probably know, each Steam-Installed game is identified by a unique integer number; Proton creates/uses a Wine prefix for each game as a directory named for that unique integer, in the "compatdata" directory of the Steam games library you choose to install in.

I do not think Proton is capable of doing this for non-Steam games, so a non-Steam game will use the wine prefix you chose when installing that game. If you make no wineprefix choice, the default is "~/.wine/".

Note that it is generally better to install each non-steam game to a different wine prefix, since games often have conflicting configuration needs. i.e. Configuring one game may break another if they share a wineprefix.

Hope that helps.

No, It doesn't use the main wine folder. I found it at the main steam folder with a bigger number that normal games use >>> ~/.steam/steam/steamapps/compatdata/2147483650
etonbears 4 Mar, 2019
torbido
etonbears
torbidoWhen I add non steam game, where is the prefix of these games?

Each version of Proton is a management wrapper for Steam-Installed games using a specific version of Wine ( including extension libraries/patches etc ).

As you probably know, each Steam-Installed game is identified by a unique integer number; Proton creates/uses a Wine prefix for each game as a directory named for that unique integer, in the "compatdata" directory of the Steam games library you choose to install in.

I do not think Proton is capable of doing this for non-Steam games, so a non-Steam game will use the wine prefix you chose when installing that game. If you make no wineprefix choice, the default is "~/.wine/".

Note that it is generally better to install each non-steam game to a different wine prefix, since games often have conflicting configuration needs. i.e. Configuring one game may break another if they share a wineprefix.

Hope that helps.

No, It doesn't use the main wine folder. I found it at the main steam folder with a bigger number that normal games use >>> ~/.steam/steam/steamapps/compatdata/2147483650

Interesting. Does that means you have to install each non-Steam game with its own copy of, say Origin or Uplay, I wonder. I thought you just added games you had already installed so you can launch them. I will have to look more into what the options are, though I don't really understand why one would use the feature except for running Big Picture with only a controller.
While you're here, please consider supporting GamingOnLinux on Patreon, Liberapay or Paypal. We have no adverts, no paywalls, no timed exclusive articles. Just 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!