Been waiting for this one, being a backer. Seems like a lot of long hard days was put into the game. Hopefully that hard work pays off for them.

View this comment - View article - View full comments

Quoting: ShoNuff!!!waiting for when I can play Dying Light again on Archlinux (currently broken it seems)... will be a happy day!

Rather than compiling mesa yourself to do the fix, you can just grab these dll's [External Link] I compiled myself for Arch. Just follow the instructions in the readme.

I've been playing the game with mesa-git and llvm-svn from the mesa-git repo [External Link] on my system for the last couple of weeks no problem and the fix has survived a month of updates without breaking so far.

View this comment - View article - View full comments

For Direct3D games (both DXVK and wined3d), Nvidia cards are now reported as if they are actually AMD cards. This prevents games from trying to load the Windows-only nvapi library and crashing or giving very bad performance.

As an AMD user I had an issue with The Vanishing of Ethan Carter Redux where it would only load if you spoof the vendor id and make it believe it's running an Nvidia card. I hope this update doesn't break those types of fixes.

View this comment - View article - View full comments

Quoting: GuestWell that's cool, if EA ever recovers from their current state of being a pure and utter garbage company that can't produce any decent games anymore......

EA have always been garbage. I had the "pleasure" of experiencing it first hand when I was in game development.

Its a shame really because they've ruined great studios over the years.

View this comment - View article - View full comments

I disagree with what he did, but it shows character to admit your mistake, apologise and rectify the mistake. Hopefully it doesn't put them off developing games and maybe they can take on criticism better in the future and make their work even better =).

View this comment - View article - View full comments

Some people dont believe in constructive criticism. They believe its just an excuse to insult their hard work. If your a game developer you need to be open to feedback, even if you disagree.

I don't know how much time and effort the developer has put into the game, but they're probably miffed at seeing a negative review that's going to affect the sales. Especially *if* its from a backer who had a chance to give feedback earlier.

View this comment - View article - View full comments

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:

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

View this comment - View article - View full comments

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 [External Link]

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 [External Link] 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 [External Link] 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 [External Link]?

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