I think it's not that easy.

One thing valve provides especially to indies is ... a huge base and platform. They'd stay unknown or only sell 10 % of what they do if it was not for steam and their huge user base, which makes a loss of 30 % still a win.

I do not know what models Valve has, but for small indies things like "first 100k copies are only 10 %, 200k are 20 %, 300k+ are 30 %, and after a million we scale down to 20 % again" or something like that.

Could have huge implications to the platform though, so I am sure Valve has thoughts about that. But since they're spammed with indies anyway it shouldn't have too much of an impact.

View this comment - View article - View full comments

Hope we can use NVK by then... since I have little hope that the proprietary nvidia wayland support will get better, to be true, it got worse from 535 to 545 :D. Those flickering issue in certain applications is annoying.

View this comment - View article - View full comments

Hope I'll be able to try that on Fedora 40. Would love nothing more than to get rid of the proprietary nvidia driver.

View this comment - View article - View full comments

Oh, the overview is in! That could draw me from Gnome again. I got so used to it for window switching in Gnome that I could not go back to KDE.

Good Job KDE Team!

View this comment - View article - View full comments

Good, I hoped that this would happen at some point and hope that will free up resources (generic implementations usually do). Now we only need NVK to perform well enough for gaming and we don't need the proprietary driver anymore only the GSP.

Some time down the road, but hey - there is a road!

View this comment - View article - View full comments

Quoting: const

Quoting: STiATI think a middle ground would be good.

I don't mind playing on proton/dxvk, it's a stack to build on for Linux, I don't see it as more or less than that. I even switched to that for titles which actually do have native linux support since the native linux versions are so badly optimized and the games just run better on proton/dxvk.

I think they should consider actually supporting Proton/dxvk for their desktop builds and steam deck, that would be a middle ground I'd like to see.

I think the time for native builds is certainly over. DXVK got too good for that, and we have to give kudos to Philip Rebohle, Joshua-Ashton and all the other contributors for that. And Valve for sponsoring that work.

Most of the times I have issues with games it's rather proton related than dxvk related.

And proton/dxvk/steam runtime is a lot less volatile and diverse than the current linux world, so it makes sense.

I don't think the time for native builds is over. A well done native build, linked against a stable runtime, can perform much better then a proton version. What we don't need any more are lazy 3rd party ports with proprietary middle layers and ending support contracts. These have not aged well and were replaced by Proton.

The time and effort which is required for that is a huge step. I don't see many developers or publishers going that route for not even 1 % of the playerbase, when they can do steam deck with proton/dxvk and minimal QA.

Let's agree to disagree on that one.

View this comment - View article - View full comments

I think a middle ground would be good.

I don't mind playing on proton/dxvk, it's a stack to build on for Linux, I don't see it as more or less than that. I even switched to that for titles which actually do have native linux support since the native linux versions are so badly optimized and the games just run better on proton/dxvk.

I think they should consider actually supporting Proton/dxvk for their desktop builds and steam deck, that would be a middle ground I'd like to see.

I think the time for native builds is certainly over. DXVK got too good for that, and we have to give kudos to Philip Rebohle, Joshua-Ashton and all the other contributors for that. And Valve for sponsoring that work.

Most of the times I have issues with games it's rather proton related than dxvk related.

And proton/dxvk/steam runtime is a lot less volatile and diverse than the current linux world, so it makes sense.

View this comment - View article - View full comments

Impressive. No arguments there.

View this comment - View article - View full comments

Quoting: omer666

Quoting: STiAT"Fixed Wayland flickering issues" is missing. Oh ye - they didn't. Again.

I'm on Wayland and I don't have flickering at all, could you explain the issue?

Library: You select one title, if you mouse-over other titles, it sometimes just soft-highlights other titles fully or partially (sometimes more than one) and flickers those highlights in-out with mouse move. Sometimes it even manages to show the game-page of the flickering title you did not mouse over - even without selecting the game you are currently mouse-overing. The faster you move over your library titles, the more often it occurs, and the more extreme it gets. If you move out of the selection and just mouse-over "maximize" in example it also soft-highlights the last title you did hilight over and flickers. If you resize the window to a smaller size it happens less.

Library Game-Page: The game screen is not properly loaded, respectively, instead of the title picture of the game or even sometimes the whole window it is transparent showing the window you have below.

That changes as soon as you manually trigger a full window redraw (resizing, taking a screenshot) to the correct behavior, until it occurs again. Running OBS fixes this too, so I guess it's something to do with how redraws are conducted.

May be related to Nvidia drivers though, but it really is a ugly issue happening often enough (like every 5th click). Since this only happens in Steam and with no other application, I'd guess whatever they use (their own toolkit?) is not properly handling at least on Nvidia+Wayland.

View this comment - View article - View full comments

"Fixed Wayland flickering issues" is missing. Oh ye - they didn't. Again.

View this comment - View article - View full comments