Quoting: Liam Dawe

Quoting: scaine

Quoting: whatever

Quoting: pleasereadthemanualcan you fix it yourself?

My guess is no.
They can test all they want, but unless they're willing (and capable) to contribute to WINE/Proton I don't see how this can work.
The game is now officially unsupported in Linux. That's why they removed the native version.

I think Valves take on this is that it's actually supported, but by Valve, not overkill.

I'd like some clarity from Valve on that though. Devs can say they "commit to get it working on Proton", but as pleasereadthemanual asks above, what does that really mean? Who's on the line if you buy that game, play it for 10 hours, then the dev screws it up and it stops working?

Realistically, by Valve's own refund rules - no one is one the line. After 2 hours / 2 weeks of buying, that's all the protection you realistically get from buying anything on Steam "Native" or not. They've only given refunds outside of that in special cases.

Hell, it wasn't until 2015 that Valve started offering those 2 hours in the first 2 weeks of buying terms. Before that, they wouldn't refund you at all except in exceedingly rare circumstances.

View this comment - View article - View full comments

It's great that OVERKILL is going to do testing for the Proton version! I have some questions about the process:

If you find an issue while testing, what will you do? Will you delay the release of the next update?

Will you fix it yourself—can you fix it yourself? Is this something you need to report to Valve on their Proton issue tracker?

How will you get the game builds to Valve's developers so they can test them and apply patches? Assuming the issue is patched in Proton, how long do players need to wait to get the version of Proton with the patches?

Will you delay the new builds until the version of Proton with the bugfixes is generally available to players?

View this comment - View article - View full comments

Quoting: Eike

Quoting: pleasereadthemanual

Quoting: Eike

Quoting: pleasereadthemanual

Quoting: EikeHere's a tip for scaling:

steam -forcedesktopscaling 2

Sorry, I have to take it "working flawlessly" back. The Steam Overlay is HUGE when in-game. More like 4x, rather than 2x. I also can't drag windows around by clicking the top part of the window and trying to move it OR with SUPER+Left-Click, so I can't see the entire window.

Sounds like two options kicking in the in-game overlay? Maybe you can remove the old one?

I tried toggling off "Scale text and icons to match monitor settings (requires restart)", but this didn't make a difference. I have no clue what might be affecting it. I've dug through all the likely settings, and all I can tell you is I have hardware acceleration/decoding/smooth scrolling on. Also, I have display scaling set to 200% on GNOME, but font scaling is 100%. There's nothing untoward in the .desktop file, and I can drag windows in normal Steam, just not the overlay. It's a mystery to me.

I'm totally speculating here, but maybe GNOME scaling works in overlay - and forcedesktopscaling too, so they get multiplied. You could give it a test by disabling GNOME scaling for a moment (if you still find your buttons then, that is ;) ).

Nope, that's not it (I thought it would be too). I even logged out of the desktop session after changing it to 100%, logged back in, opened Steam, waited forever for Vulkan Shaders to process (apparently this is something that's going to happen on every launch now), and the overlay is still huge and immovable. It being huge wouldn't be such an issue if I could move the windows.

Thank you for your tech support :) I think it's time I find the official place to complain about the new Steam Client, wherever that is. Hopefully something in our discussion helps someone else.

Some more issues I've noticed:

• Steam gets unresponsive regularly (three times so far in the past three hours) and the only way to fix it is to kill it.


• I have my games on separate drives. Sometimes they aren't noticed by Steam on startup. The way to get it to recognise them in the old client was to click Install -> Click the dropdown and select the drive. That's it. The new way is to click install, click settings, click +, click the right drive, and click Ok. There are now far more steps for no reason.

View this comment - View article - View full comments

Quoting: Eike

Quoting: pleasereadthemanual

Quoting: EikeHere's a tip for scaling:

steam -forcedesktopscaling 2

Sorry, I have to take it "working flawlessly" back. The Steam Overlay is HUGE when in-game. More like 4x, rather than 2x. I also can't drag windows around by clicking the top part of the window and trying to move it OR with SUPER+Left-Click, so I can't see the entire window.

Sounds like two options kicking in the in-game overlay? Maybe you can remove the old one?

I tried toggling off "Scale text and icons to match monitor settings (requires restart)", but this didn't make a difference. I have no clue what might be affecting it. I've dug through all the likely settings, and all I can tell you is I have hardware acceleration/decoding/smooth scrolling on. Also, I have display scaling set to 200% on GNOME, but font scaling is 100%. There's nothing untoward in the .desktop file, and I can drag windows in normal Steam, just not the overlay. It's a mystery to me.

View this comment - View article - View full comments

Quoting: EikeHere's a tip for scaling:

steam -forcedesktopscaling 2

Sorry, I have to take it "working flawlessly" back. The Steam Overlay is HUGE when in-game. More like 4x, rather than 2x. I also can't drag windows around by clicking the top part of the window and trying to move it OR with SUPER+Left-Click, so I can't see the entire window.

View this comment - View article - View full comments

Quoting: Eike

Quoting: pleasereadthemanualThe hardware acceleration is nice and all, but the client is now tiny on my 4K screen (GNOME), and it takes 5 minutes for the "Processing Vulkan Shaders" prompt to appear when launching Halo: MCC, and even after explicitly skipping it, it says "Processing Vulkan Shaders (0%)" next to the Cancel button 5 minutes later. I assume it launches...at some point? I didn't bother waiting around after the first 10 minutes.

Here's a tip for scaling:

steam -forcedesktopscaling 2

Thanks so much! This worked flawlessly. I couldn't figure out how to do this in the beta client I tried a month or so back. For everyone else's future reference, copy the .desktop Steam file from /usr/share/applications/steam.desktop to ~/.local/share/applications/steam.desktop, and add -forcedesktopscaling 2 to the Exec line.

About 10 minutes later, Steam started downloading a "shader pre-cache update" of 2GB for Halo: MCC, despite me explicitly skipping it. In total, it took about...25 minutes to launch? Rocket League did the same thing. What is the point of a Skip button if it doesn't work anymore?

View this comment - View article - View full comments

The hardware acceleration is nice and all, but the client is now tiny on my 4K screen (GNOME), and it takes 5 minutes for the "Processing Vulkan Shaders" prompt to appear when launching Halo: MCC, and even after explicitly skipping it, it says "Processing Vulkan Shaders (0%)" next to the Cancel button 5 minutes later. I assume it launches...at some point? I didn't bother waiting around after the first 10 minutes.

View this comment - View article - View full comments

Quoting: Mountain ManSeems a lot of developers are counting on Proton to give them zero effort access to the Linux market. The good news is that Proton works extremely well. The bad news is... hmmm... Is there bad news? I'm not sure.

Developers get to claim the benefits of supporting Linux without needing to worry if an update breaks support every few weeks because they don't officially support it, and so they don't test new updates. Players aren't entitled to complain about it because the game only supports Windows.

I don't know if "works extremely well" reflects my experience with Proton. Games take a minute or longer to startup while they compile shaders, because otherwise the game would be jittery the entire time, and sometimes it is anyway. It mostly works, I'll certainly give it that, and I'd rather it worked than didn't, but there's a long way to go until it works extremely well on most of the games I play (multiplayer games and DRM-encumbered visual novels sold outside of Steam).

View this comment - View article - View full comments

Quoting: ElectricPrismImagine selling a game and then DROPPING support for WINDOWS, and telling customers that the Linux version still works over Cygwin and VirtualBox.

Anyways -- this is more a problem with SaaS (Software as a Service) -- because it's not really clear what I'm buying when I spend money-- A Physical Copy -- Is a Physical Copy -- -- Is a Physical Copy -- Is a Physical Copy.

I'm sympathetic, but not enthusiastic or pleased.

Yes, there is a strange expectation Linux users are supposed to have, which is to be grateful they were supported at all, for any length of time. Because this platform is so hard for developers to support. And besides, you can work around it, right? You guys are always working around stuff

It seems Linux ports are treated more like charity work than anything else.

View this comment - View article - View full comments

This is sad. I wonder if the next step is to implement anticheat which doesn't work on Linux. That was the next step after Rocket League dropped official support for Linux.

View this comment - View article - View full comments