You can sign up to get a daily email of our articles, see the Mailing List page!
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 and Liberapay.!
Latest Comments by lejimster
Proton beta 3.16-2 is out for Valve's Steam Play system
17 October 2018 at 11:15 pm UTC

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.

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.

Proton beta 3.16-2 is out for Valve's Steam Play system
17 October 2018 at 7:42 pm UTC

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

Proton beta 3.16-2 is out for Valve's Steam Play system
17 October 2018 at 5:30 pm UTC

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.

Proton beta 3.16-2 is out for Valve's Steam Play system
17 October 2018 at 1:59 pm UTC Likes: 3

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.

Valve have updated Steam Play with the 3.16-1 beta based on Wine 3.16 and new DXVK
14 October 2018 at 6:07 pm UTC

This is exciting news, but I don't fancy building mesa and applying the patches myself. So I'm going to wait for them to land in mesa-git.

Also seems like changing DXVK to a system library (while potentially faster) is causing some headaches especially for SteamOS users who need an update.

Hope we can get all these issues ironed out for stable release. Can't wait to get testing

The Steam Play whitelist just had a large update including The Witness and Wolfenstein: The Old Blood
6 October 2018 at 1:12 pm UTC Likes: 2

toojaysAny idea why they would whitelist The Old Blood but not The New Order? Aren't they the same engine?
HoriAwesome!

I'm curious why Wolfenstein: The Old Blood is whitlisted but The New Order isn't. They are basically the same game, with different campaigns, and very small changes.
They both performed 100% under WINE with no noticeable performance loss whatsoever. Is it different in Proton? I don't want to try TNO again since I already finished it not too long ago.
Not sure about Old Blood, but TNO had a pretty major issue (crashing in the menus)with AMD/mesa that only recently got a fix. It also has a major frame rate bomb in one area of the game on those drivers too.

Doktor_MandrakeSuprised Wolfenstein 2: New Collosus hasn't been added to their whitelist

Uses vulkan by default and I played the game from start to finish on Proton with zero issues

There's some kind of facial animation bug that affects AMD/mesa users.

I think this is a common problem, you need it working on all major graphics drivers beforw a game gets white listed.

Which is why I think The Witness got white listed so fast. It works perfectly from day 1 on all GPU.

Valve have pushed out a new Steam Play beta with DXVK 0.80 and more
28 September 2018 at 10:40 pm UTC

I hope it won't be too long for stream output support to arrive. The only frustrating thing I'm finding is many games work fine on nvidia but fail to start on my Vega/radv setup, it always seems no matter how good AMD drivers improve, they're always behind in compatibility.

An update on the status of porting Ashes of the Singularity: Escalation for Linux
22 September 2018 at 11:16 pm UTC Likes: 1

I was interested in this, but by the time they bring it to Linux it will be so old the interest will have faded. Maybe they're doing work for future projects. I'm surprised it doesn't work using the Vulkan renderer through wine/proton.

Mesa 18.1.8 and Mesa 18.2.0 have been released, pushing Linux open source GPU drivers further
10 September 2018 at 5:00 am UTC

whizse
lejimster
ziabiceFinally I can put my hands on RAGE and Wolfenstein!

Been playing Rage. Although only 64bit works properly for me and I had to add xact to get the sound working.

I need to do some driver testing to see if its just a buggy version of mesa-git, but 32bit Rage and Wolfenstein N.O. tend to crash in the menus.
I think this is the problem:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=bc65dcab3bc48673ff6180afb036561a4b8b1119

Though I'm seeing hangs, not crashes, in the menu in Rage, haven't tried Wolfenstein yet.

Could you try if this fixes the problem for you?
https://pastebin.com/iwGynY9E

Ok, so I have been testing the patch for a few hours, haven't experience one hang on either Rage or Wolfenstein N.O. with it.

That leaves just one major problem left with 32-bit Rage now, the megatexture corruption.

https://youtu.be/EUwq4dbnFkA

Mesa 18.1.8 and Mesa 18.2.0 have been released, pushing Linux open source GPU drivers further
9 September 2018 at 6:04 am UTC

ziabiceFinally I can put my hands on RAGE and Wolfenstein!

Been playing Rage. Although only 64bit works properly for me and I had to add xact to get the sound working.

I need to do some driver testing to see if its just a buggy version of mesa-git, but 32bit Rage and Wolfenstein N.O. tend to crash in the menus.

  Go to:
Livestreams & Videos
Community Livestreams
See more!
Popular this week
View by Category
Contact
Latest Comments
Latest Forum Posts