Quoting: TheSHEEEP

Quoting: hardpenguin

Quoting: dpanterPersonally I don't care.

Personally, I don't care that you don't care!

Personally, I don't care that you don't care that they don't care!!

>

View this comment - View article - View full comments

Quoting: GuestAs far as I'm aware, the interfaces for Stadia aren't public knowledge, and are probably NDA'd by Google. So nobody can really create a Stadia runtime that way.

Even if SDL2 is used and some non-public branch provided, there's still likely a few things Stadia specific. A game wouldn't be binary compatible on a desktop.

Yeah, but that was just mentioned in the eventuality of Google stop caring about Stadia and shutting it down, then maybe they'll lift the NDA's and open the specs.
I really don't know, just throwing random thoughts in the air.

View this comment - View article - View full comments

Quoting: MohandevirI have no doubt that the Linux community would find a way, but would Google ever consider this before pulling the plug? I was thinking about the other 98% (total guess) of Stadia users that know nothing about Linux. What would be in it for them?

Ah yes, I forgot about that.
But hey, maybe it'll work under WSL too:)

View this comment - View article - View full comments

Quoting: dpanterPersonally I don't care.

Yeah Humble Bundle was great, I loved the very first years with all those Linux bundles, they were so funny with those Arnold impersonations :)
Anyway, in time they shifted more and more from the original "humble" spirit, for all I care they can put the sliders back, and take them out again, I couldn't care less.
They're just a bundle "that I used to know".

View this comment - View article - View full comments

Quoting: pbwhile we wait for SteamOS 3 4. :whistle:

You surely meant to say SteamOS 2 Episode One, or I dunno...SteamOS 2 Lost Coast.

View this comment - View article - View full comments

Quoting: MohandevirI'm just wondering what could be done with a Stadia build, whitout the api and some way to run it?

Maybe "we" could implement some kind of "Stadia-Runtime" that can be used in any distro.

View this comment - View article - View full comments

OK, thanks.
I imagined that is the "correct" behavior, but I hoped there are some tweaks or patches around to workaround it.
I did found a patch for Doom that looks to be what I want, but not sure if it still works or is applicable for this game.
https://forum.zdoom.org/viewtopic.php?f=105&t=35761 [External Link]

View this comment - View article - View full comments

Anything that can be done to eliminate the floating movement style? The game seems to work just fine, but I feel like I'm skating, every time I take just a small step for example, I'm sliding an extra meter. Feels particularly nauseating especially when I'm strafing, like I'm loosing my balance or something.
Is not lag or anything, is just like ice under my feet.

View this comment - View article - View full comments

Quoting: Corben

Quoting: RafiLinuxIt's sharp on my end. I can download some of the clips I made and send them your way. I mostly play ZA4, MK11 and Super Bomberman R Online.

I'd just be interested in some of the details of your setup. E.g. what GPU/CPU do you use, and how is it connected to what kind of screen.

Quoting: dubigrasuWell, even on Windows it doesn't works perfectly ootb. There are less issues with getting the HW acceleration working, but people on Windows are equally resorting to extensions to get it to work as intended. Really, not much of an Linux only issue.
I would say that Stadia (whatever frontend is using) needs some streaming settings similar with GFN. Sure, what they want is to promote this ease of use concept "you just click and play" but clearly isn't working, at least for the moment.
For now, I'd say that adding the Stadia Enhanced is almost mandatory if you want the best experience. It does everything that Stadia should've done from the beginning, including the search bar :) and more.
I haven't bothered lately to see how a plain Chrome would work, but last time I tried HW decoding wasn't working.
I just use a Chromium with HW acceleration and Stadia Enhanced set to the desired res and codec. I don't need any extra steps before running and I do get the HW acceleration. BTW, you don't need chrome://media-internals to check it, the type of decoding used is listed right in the Stadia Enhanced HUD, use the small HUD if the big one is too intrusive.

Thanks for the info. So far I had seen no issues on Windows machines, and yes, I strongly agree that they need the possibility for the enduser to set those things. Auto-detection can always be an issue. Why not "hide" it under an advanced settings button?
I followed the instructions on this article [External Link] to enable HW acceleration, but it didn't work for me.

I haven't had issues on Windows either, but the complaints are frequent on Stadia community.
Don't know what to say about that article, it clearly states that HW acceleration was made available for Google Chrome 88 and newer, but I was never being able to make it work, while is a breeze on Chromium.
In the end, software or hardware decoding it doesn't matter that much as long as the decoding is done fast enough, and for me it takes about 2.5ms, which is quite good (the decoding speed is also listed by the Stadia Enhanced extension). Unfortunately the latency caused by the distance is around 28ms, which is not that good, but usable.
Another cause of latency is the browser itself, you can use:
https://basro.github.io/input-lag-measuring-tool/ [External Link]
or
https://www.vsynctester.com/ [External Link]
to check it.
An effective way to reduce the browser latency is to start Chromium with the --disable-frame-rate-limit argument, though it can raise considerable your CPU usage.

View this comment - View article - View full comments

Richard Geldreich, that guy has a huge chip on his shoulder about Valve, I don't believe a word he's saying. Of course he's siding with Epic.

View this comment - View article - View full comments