Valve are continuing to polish the next version of Steam Play's Proton with an update to the beta channel.
Proton 3.16-2 was released in the last day which includes these changes:
- DXVK is again built as a Windows DLL, due to incompatibilities with the Steam runtime. This should fix widespread crashes with Direct3D 11 titles.
- DXVK updated to 0.90.
- Fix for alt-tab crashing on Unreal Engine 1 games, including Deus Ex.
- PROTON_USE_WINED3D11 is now called PROTON_USE_WINED3D to reflect that this variable affects more than Direct3D 11. The old name still works as an alias.
They've also moved the changelog, which can now be found here. The updated version of DXVK will fix issues with Bioshock, Dark Souls 3, The Evil Within and gives a small CPU improvement for Assassin's Creed Odyssey.
To enable the beta, you need to go into Steam's main settings, locate the Steam Play section in the left panel and choose it from the dropdown box. You do not need the Steam beta client.
Some you may have missed, popular articles from the last month:
Quoting: adamhmIDK, I kept all 3.7* Proton releases, and for all of them the wineserver binary is 3.3MB. Only starting with 3.16* the wineserver binary grew to 3.4MB.Quoting: lejimsterUpdate: Yeah, just looked at DXVK's dll's and checked performance of a title I know well. Looks like they've been compiled in debug mode. I will open an issue on the proton bug tracker.
I'd guess given the huge increase in size for Proton in general with versions 3.7-7 and later this issue probably applies to the Proton as a whole & not just DXVK. e.g. Proton 3.7-6 is about 415MB (just the "dist" directory, sans the share/default_pfx and share/wine/gecko directories), whilst 3.7-7 and later come in at about 815MB. The wineserver binary for 3.7-6 is 478.8KB while for 3.7-7 and later it's 3.3MB+
0 Likes
Quoting: dubigrasuIDK, I kept all 3.7* Proton releases, and for all of them the wineserver binary is 3.3MB. Only starting with 3.16* the wineserver binary grew to 3.4MB.
I've done the same with every build since I started using it (which was at 3.7-6, when it was rolled into the stable client). The build I have is here: https://www.dropbox.com/s/wk0vm7qfqfdt51u/proton-3.7-6.tar.xz?dl=0
0 Likes
Quoting: adamhmInteresting, seems like nearly everything is bloated in 3.7-8 compared to the your 3.7-6. I wish I had backed up my own now. I've left a comment on the bug report linking to your post. So hopefully we will find out whats going on.Quoting: dubigrasuIDK, I kept all 3.7* Proton releases, and for all of them the wineserver binary is 3.3MB. Only starting with 3.16* the wineserver binary grew to 3.4MB.
I've done the same with every build since I started using it (which was at 3.7-6, when it was rolled into the stable client). The build I have is here: https://www.dropbox.com/s/wk0vm7qfqfdt51u/proton-3.7-6.tar.xz?dl=0
0 Likes
Quoting: adamhmThe date on your archive is a bit puzzling to me, is around 23 Aug, which is more in line with 3.7.3 than 3.7.6.Quoting: dubigrasuIDK, I kept all 3.7* Proton releases, and for all of them the wineserver binary is 3.3MB. Only starting with 3.16* the wineserver binary grew to 3.4MB.
I've done the same with every build since I started using it (which was at 3.7-6, when it was rolled into the stable client). The build I have is here: https://www.dropbox.com/s/wk0vm7qfqfdt51u/proton-3.7-6.tar.xz?dl=0
Edit Huh, you archive is actually even older than 3.7.3 (the very first build that I have).
Last edited by dubigrasu on 17 October 2018 at 9:03 pm UTC
0 Likes
Well, that's the version I had prior to the release of 3.7-7, and since 3.7-6 was the current version at the time according to Steam that's what it was labelled as. I used it with several games before making that copy & Steam did not try updating it or otherwise give any indication that it was outdated.
That said, prior to using it I did have the Steam beta installed with the intention of trying out Proton but I never got around to it until after it was rolled out to the stable release (at which point I moved back to the stable branch), so it's possible that Steam downloaded an older version and then lost track of it somehow.
That said, prior to using it I did have the Steam beta installed with the intention of trying out Proton but I never got around to it until after it was rolled out to the stable release (at which point I moved back to the stable branch), so it's possible that Steam downloaded an older version and then lost track of it somehow.
0 Likes
Quoting: adamhmWell, that's the version I had prior to the release of 3.7-7, and since 3.7-6 was the current version at the time according to Steam that's what it was labelled as. I used it with several games before making that copy & Steam did not try updating it or otherwise give any indication that it was outdated.
That said, prior to using it I did have the Steam beta installed with the intention of trying out Proton but I never got around to it until after it was rolled out to the stable release (at which point I moved back to the stable branch), so it's possible that Steam downloaded an older version and then lost track of it somehow.
I asked and apparently they've always built the wine part of Proton with debug stuff, Codeweaver developer Andrew Ekium posted this:
QuoteYeah, I read those comments. We do purposely ship Wine with debug symbols included, so the binaries are large. However, Wine does correctly have -O2 optimizations enabled (and more incoming), so it shouldn't be impacted in the same way that DXVK is when built in debug mode. There was a bad build uploaded a long time ago that had symbols accidentally stripped and some other problems. That was build 3.7-2. My guess is that user snagged that and mis-labeled it as 3.7-6? Otherwise I don't know where they would've gotten a stripped wineserver from.
So that could explain the file size difference, no worries. Pierre-Loup closed the bug anyway saying it was fixed and 3.16-3 beta has appeared on steam now. Just downloaded and had a quick test of that myself, so that seems to have solved that problem.
Quoting: grigiProton 3.16-1 severely regressed on my Intel IGP 620.You might want to check that version out see if it fixes your performance issues.
Skyrim (non se) ran quite horribly, no glitches, just terrible performance.
At least downgrading to 3.7-8 resolved all the issues.
When I get time I'll try and see if 3.16-2 (or newer by then) fixes the issues.
Last edited by lejimster on 17 October 2018 at 11:17 pm UTC
0 Likes
Quoting: lejimsterI asked and apparently they've always built the wine part of Proton with debug stuff, Codeweaver developer Andrew Ekium posted this:
...
So that could explain the file size difference, no worries. Pierre-Loup closed the bug anyway saying it was fixed and 3.16-3 beta has appeared on steam now. Just downloaded and had a quick test of that myself, so that seems to have solved that problem.
Yeah, I saw that. So it seems that prior to 3.7-7 Steam just wasn't updating it here for some reason. Anyway, it doesn't seem to be an issue any more at least & subsequent updates have been coming through just fine :)
0 Likes
Anybody experiencing mouse issues with Fallout 4 ?
0 Likes
Quoting: VinceNardelliAnybody experiencing mouse issues with Fallout 4 ?
The mouse is bugged in Fallout 4.. You have to apply bBackgroundMouse=1 in the Fallout4.ini file ..
It must look like this:
[Controls]
fMouseHeadingXScale=.021
fMouseHeadingYScale=.021
bBackgroundMouse=1
0 Likes
See more from me