- Wine 32 Bit on Wine 64 STILL needs a set of 32 Bit libraries. That is not a solution, but moving the libraries around.

That is absolutely wrong. Where did you get that from? Starting with Wine 9.0 there is no need for any native 32 bit libs for the new Wine 32 Bit on Wine 64 (WOW64) mode, including graphics drivers.

View this comment - View article - View full comments

Quoting: jardonthis is off-topic but it sounds like either out-dated nvidia drivers or a resource limitation.

As you can see in my PC info, I have AMD and I usually don't run any other software along with Steam. It's completely unrelated to which GPU / hardware you have.

View this comment - View article - View full comments

Quoting: Mountain ManI have not encountered a single one of those issues. Maybe it's a problem specific to your system?

No, the issues I listed are also experienced by many others. If you're interested, here [External Link] is the unclickable context menu issue on steam-for-linux Github.

View this comment - View article - View full comments

Quoting: robvvand the only issue I've had is with GPU accelerated rendering, which seems to be a bit unstable.

This is a gross understatement. In my experience, Steam is literally the only app on Linux that may cause a total desktop freeze (no matter on which DE, X.org or Wayland) after which I can do nothing but hard reboot my PC. The only workaround to it is disabling hardware acceleration in Steam.

Also, how about the fact that Steam context menu contents are 95% of the time unclickable. This is an issue since the big ui redesign update and it still hasn't been fixed after more than a year or two. You have to click sometimes dozens of times until game properties finally opens for example.

Oh, and also how Steam was already slow to launch on Linux and since the big ui update it's even slower. And many more annoyances..

I mean don't get me wrong, I have endless grattitude towards Valve for everything they've put into Linux, but you honestly have to admit that when it comes to the Steam client itself on Linux, it's a POS and the forever unfixed issues with it makes them look lazy.

View this comment - View article - View full comments

Quoting: apemaxWell that might be the issue then, Flatpak has been known to cause several issues with WT, Including crashing. I would try the native Linux client either through native non-Flatpak Steam or direct through the launcher you can download from the WT homepage and see if that works better.

Yes, I've also tried it directly via the launcher from WT homepage, but to me it actually didn't make any difference compared to running it through Steam Flatpak. I've read a lot of complains about it having issues on Wayland, and since I've been on Wayland for the last few years, I can only guess that it's probably what might have caused the vsync stutter issue.

View this comment - View article - View full comments

Quoting: apemaxIt only limits texture quality to I believe low on 2GB or less VRAM and Medium on 4GB or less VRAM, I'm not sure about 6GB of VRAM though.

I have 4GB of VRAM. Nontheless, that's not an issue with the Windows client and WT isn't even a VRAM heavy game. Unless you enable some ultra high res textures, it shouldn't use more than around 2-2.5GB of VRAM with other settings set to maximum. And AFAIK, they limit texture quality on Linux client not because it uses more VRAM, but because otherwise it causes crashes that they can't (or unwilling to) fix.

Quoting: apemaxOn the VSync issue you mentioned, I don't have that issue myself on Arch, RADV+6500XT. I don't know what version of Debian your on but maybe something to do with a older version of Mesa?

Last time I tried WT native client through Steam Flatpak, so I had the latest Mesa at that time. I don't think that issue is related to the Mesa version. I also feel like WT's Vulkan renderer (regardless if it's used with Linux or Windows WT client) is also a bit of an afterthought. From the numerous times I tried it, I was getting inconsistent performance and occasiinally some weird slowdowns, which isn't the case with WT's Dx11 and Dx12 renderers.

View this comment - View article - View full comments

Did they finally fix texture quality being limited to medium and pulsating stutters with vsync enabled in their Linux client?

If no, then the Linux client is still crap and I'll continue playing WT on Proton which runs beautifully.

View this comment - View article - View full comments

If they think that I need to get comfortable with the fact that one day I may completely lose access to the game I bought with my hard earned money, then I'd rather just quit gaming altogether. Seriously, I don't advocate piracy, but this is a case that makes piracy more justifiable. As they say: "If buying isn't owning, piracy isn't stealing".

This is also why I wish the open source gaming scene would've been more developed. I personally like games like Xonotic and Red Eclipse, but of course they're incomparable even to some indie games and of course they're not something an average gamer would really want to play.

View this comment - View article - View full comments

Too bad that WT has recently stopped working on Proton after working beautifully on it for some time (it now crashes after login). And I'm not touching the dumpster fire that is their so called "native port" with a ten-foot pole. Every time I was trying the native port it was a bad experience after bad experience after bad experience after bad experience after bad experience after bad experience... And again, bad experience.
When the native port still used opengl, the game was essentially unplayable most of the time. Especially in 2017, when it was a total glitchlag fest. And when it received the Vulkan renderer, the performance also wasn't that great in the beginning. The Vulkan renderer has of course matured over time, but the Linux client still suffers from occasional crashes and other issues. At some point you couldn't even set texture quality to high (WTF?!) And last time I tried the native port, it caused a gpu hang on my RX 580.

Sorry if it was a bit of a rant. Overally I love this game, but getting it to run on Linux is like drowning in a sea of grief most of the time and occasionally finding a few islands of happiness.

View this comment - View article - View full comments

Btw, I'd argue that Flatpak is much much closer to the Unix principle of "do one thing and do it well" than traditional package management because in Flatpak you have your regular apps and the different runtimes underneath (there are also separate runtimes for GPU drivers and separate runtimes for other system packages) and there is a clear separation between every single app and between every single runtime. With package management on the other hand, you only have this one monolithic chunk of packages with which there is no clear separation between system packages and regular apps. Everything is on the same level.

The same argument can be made about kernels - that Microkernels (that are barely used in the Unix or Unix like OS family) are actually closer to Unix philosophy than monolithic kernels...

So anyone whining about "but but muh Unix philosophy" doesn't even know what he's talking about.

View this comment - View article - View full comments