Valve and CodeWeavers continue pushing Linux gaming along with another release of Proton for Steam Play with 4.11-3.
The biggest change here seems to be for gamepads. Proton will no longer emulate them all as if they were Xbox controllers, instead games will access them directly. So DualShock 4 (PS4) gamepads, fighting pads and more should behave more like they do on Windows.
fsync (the experimental replacement for esync) also saw some improvements to hangs and crashes, as well as gaining configurable spin count. This new config ability they say might help performance but it's disabled by default.
Additionally they added missing language fonts, in-game web browser fixes, more fixes for crashes related to text input with Mordhau and Deep Rock Galactic being noted, improved support for older VR titles and support for the latest Steamworks and OpenVR SDK versions.
It also pulls in the recent new release of D9VK, considering it only released yesterday that's quite impressive really. You still need to manually enable D9VK for D3D9 titles though, like this:
PROTON_USE_D9VK=1 %command%
Use the above for D9VK as a launch option (right click -> Properties -> Set Launch Options) for each game as needed.
You can see the full changelog here.
Didn't expect Valve to push a new release out that fast. But well - it's probably why there was a D9VK release just in time before the new Proton release.
Also seeing D9VK is coming a long nicely is really great. The only game I used it for so far was Aliens: Colonial Marines, and the FPS are way higher with D9VK than with wine's dx9 implementation. There were some shader issues on the Alien models with 0.13f though, but still nicely playable.
Quoting: CorbenAliens: Colonial MarinesOh? Now this I have to see.
Edit: Eh I guess it needs some .NET fixes? Doesn't load.
Last edited by Liam Dawe on 27 August 2019 at 12:14 pm UTC
QuoteProton will no longer emulate them all as if they were Xbox controllers, instead games will access them directly. So DualShock 4 (PS4) gamepads, fighting pads and more should behave more like they do on Windows.
Heureka!
Quoting: Liam DaweMaybe not only .NET but it's also a CEG protected executable. I used wine for this and installed D9VK manually, to get Steam running I was using -no-cef-sandbox as parameter for Steam.Quoting: CorbenAliens: Colonial MarinesOh? Now this I have to see.
Edit: Eh I guess it needs some .NET fixes? Doesn't load.
But people report it installs fine with Lutris as well.
edit: you can see the Alien shader glitches in a VOD here.
Last edited by Corben on 27 August 2019 at 1:08 pm UTC
Quoting: CorbenCEG protected executable.Like Warhammer 40.000 Space Marine... is no good playing with an "alternative" exe...
CEG and mfplat are my number one foes. :><:
Quoting: TorqachuI was only successful with Aliens vs Predator (2010), where you can use the CEG protectd executable from a wine or windows steam install from the same machine. If you then also fake the date (on some days the game crashes, on certain days it works flawless), it works in Proton. But that didn't work yet with any other CEG protected executable. Well, at least those games work flawless in wine Steam.Quoting: CorbenCEG protected executable.Like Warhammer 40.000 Space Marine... is no good playing with an "alternative" exe...
CEG and mfplat are my number one foes. :><:
QuoteProton will no longer emulate them all as if they were Xbox controllers, instead games will access them directly. So DualShock 4 (PS4) gamepads, fighting pads and more should behave more like they do on Windows.Oh, I thought it was doing that on purpose for games that weren’t designed with non-xbox controllers in mind. I sure look forward to seeing the right key prompts!
See more from me