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.

View this comment - View article - View full comments

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.

View this comment - View article - View full comments

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.

View this comment - View article - View full comments

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

View this comment - View article - View full comments

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

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

Quoting: GuestSuprised 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.

View this comment - View article - View full comments

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.

View this comment - View article - View full comments

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.

View this comment - View article - View full comments

Quoting: whizse

Quoting: lejimster

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

View this comment - View article - View full comments

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

View this comment - View article - View full comments

Can't wait for this extension to become available. So many titles will be whitelistable. Including Grow Up which I've been waiting to play ever since the devs decided not to bring this sequel to Linux. (Love the original).

View this comment - View article - View full comments