Quoting: EikeHappy GoL cake day!
*edit* 8 years!?!
You must have been here before Liam! :-D

Yeah, I still remember when Liam used to post invitations for his site on various forums (GOL was virtually unknown at that time), and getting banned for spamming.
How times have changed.

View this comment - View article - View full comments

The original Metro 2033 was Windows-only. (Only Metro Last Light had a Linux port)

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]

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

View this comment - View article - View full comments

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.

View this comment - View article - View full comments

If as a SteamOS user you feel like experimenting with the new update to Steam Play 3.16-1 beta, don't do it yet.
The newer DXVK libraries are compiled against a newer libstdc++.so.6, and they will not work. Basically any DX11 game will not start or just revert to DX9 (if possible).

I have it working now after some tinkering, but that kinda defeats the plug and play purpose of SteamOS.
(is just that I can't help myself)

View this comment - View article - View full comments

@YoRHa-2B & Doktor_Mandrake, thanks, got it.

View this comment - View article - View full comments

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

I played the demo today, and it runs very well but characters don't open their mouth when they speak. There's just some weird distortion around it.
I take it that you didn't see that on your gameplay?

View this comment - View article - View full comments

Quoting: dannielloAbout Marc video: yes, nice Linux native gaming advertisement. I know that in adverts everything need to be pretty, working great, big "native" numbers, etc.

But reality is more brutal. Easily could be prepared quite opposite video with very sad information: Linux native support very often it is illusion. Linux native ports often are abandoned (Ticket to Ride), with start issues (War Thunder) or even cannot be finished (even in Valve game: Half-Life Opposing Force - end map is not loading after kill main boss).

Sure, but if you want to make a video concentrated on game bugs and issues, you can do it about Windows ones too. Plenty of that to go on for hours.
BTW, the Half-Life Opposing Force ending issue happens on Windows too.

View this comment - View article - View full comments

I'm not too fond of the new high contrast interface look, is a bit too harsh for my eyes and I have to squint when I look at it. The old one was more pleasant.
I've look in the settings but haven't found any way to change it.

View this comment - View article - View full comments

Quoting: Sil_el_moti see no change in VR since the new proton. Games that ran before are still running, games that didn't start before now don't start either. Would be interesting, if someone has other experiences.

Just make sure you do run 3.7-6. Sometimes is pretty finicky to get proton to actually update itself to the newest version. Supposedly is enough to only do a file verification for the game in question to get proton to update, but I've seen this failed few times.
I'd go as far as deleting the "Proton 3.7 Beta" folder to make sure the new version is downloaded (after you switch to 3.7-6 in the settings).

View this comment - View article - View full comments