Proton beta 3.16-2 is out for Valve's Steam Play system

Haha... when I'm through with Pathfinder: Kingmaker, Bards Tale 4, Battletech, Insomnia, Frozen Synapse 2.... I'll have all Windows titles out of the box.. ;-)

Quoting: NeverthelessBards Tale 4, Battletech

Aren't those coming to Linux pretty soon?

Proton 3.16-1 severely regressed on my Intel IGP 620.
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.

I noticed that Proton increased in size quite drastically with 3.7-7 (comparing the slightly modified versions I use for my wrappers it's about double the size of 3.7-6; compressed it's almost triple the size). And with 3.16-2 it seems to have gained a few hundred MBs more (the DXVK DLLs have ballooned to almost 300MB). Looks like it's possibly a repeat of this issue?

Quoting: adamhmI noticed that Proton increased in size quite drastically with 3.7-7 (comparing the slightly modified versions I use for my wrappers it's about double the size of 3.7-6; compressed it's almost triple the size). And with 3.16-2 it seems to have gained a few hundred MBs more (the DXVK DLLs have ballooned to almost 300MB). Looks like it's possibly a repeat of this issue?

That does sound like the same problem I experience at launch. Might go along with what grigi is experiencing aswell. I will test and see if this is the case.

Update: 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.


Last edited by lejimster on 17 October 2018 at 2:15 pm UTC

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+

Quoting: pb

Quoting: NeverthelessBards Tale 4, Battletech

Aren't those coming to Linux pretty soon?

Exactly! And when I finished the native games, they will have made Steam Play perfect.

Dark Souls 2 working out of box! SWWWWWWWEEEEEEEEEEEET!

Quoting: adamhmI'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+

I don't have 3.7-6 to compare. Maybe you could add a comment to this bug report as it might be related.

we need battleye! my xmas wish is r6 siege..

Quoting: adamhm

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+

IDK, 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: 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

Quoting: adamhm

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

Interesting, 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: adamhm

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

The 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.
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

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.

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.
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.

You might want to check that version out see if it fixes your performance issues.


Last edited by lejimster on 17 October 2018 at 11:17 pm UTC

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 :)

Anybody experiencing mouse issues with Fallout 4 ?

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