I would like to see Valve pick up on Stadia (Stadia white label?) and build it's own SteamOS based cloud service...

View this comment - View article - View full comments

Quoting: scaine

Quoting: GuestI actually think what held it back from attracting game publishers is linux and vulkan. It probably would have had a better time attracting big publishers with a Windows based solution since the effort of putting games on the service would have been lower

Effort may have been lower, but I doubt it would scale in terms of cost. Or, frankly, performance, although that's just me extrapolating from how poorly Citrix and Horizon solutions run Windows desktops at scale on shared hardware (they generally don't).

Indeed, Linux (and the Stadia framework built upon it) might be a contributing factor to how Google get such low latency generally.

Pure guesswork of course, but there must be reasons they went Linux despite most games being focussed on Windows.

The first reason that comes to my mind is Windows... When you want to use Windows, you have to deal with the Windows UI and all the bumps that comes with it. GeForce Now shows these quite clearly. It feels patched no matter what they do, because of Windows, there are no workarounds. Stadia feels completely integrated with a custom UI that answers the needs of their service. It's a console experience, in the cloud.

View this comment - View article - View full comments

Quoting: dubigrasu

Quoting: Mohandevir"Google has added 93 games to Stadia since the start of this year, with just six weeks left to meet its promise of at least 100 titles added during the calendar year 2021."

Source:
https://9to5google.com/2021/11/19/stadia-nine-to-five-game-changelog/ [External Link]

They did!?
If so, then I didn't payed much attention, although I do watch their announcements and I'm even subscribed to their YT channel.
Or maybe they released so much shovelware that my mind didn't registered it.

Sure thing, it's not all games I'm interrested in either, but I don't think they may be classified as "shovelwares". All Stadia games seem curated and lots of them are well known indie titles.

View this comment - View article - View full comments

Thinking the same. Google seems to be giving up on the best streaming service available, imo. It needs more games and aside from Ubisoft, not much AAA titles are now coming out for it.

As for GeForce Now, aside from the founders subscription (60$/year), it really is expensive, imo, for games I already own and I can't play my whole Steam catalogue, on top of that. The basic sub is 125$/year and the new RTX 3080 tier is through the roof with a 250$/year. I got absolutely no interest in that, I'll use the Steam Link app, instead and gain access to my whole Steam catalogue, at the same time. I really hoped Google would up it's game, but it seems the contrary. They pulled the plug way too fast.

As for the 100 games in 2021:
"Google has added 93 games to Stadia since the start of this year, with just six weeks left to meet its promise of at least 100 titles added during the calendar year 2021."

Source:
https://9to5google.com/2021/11/19/stadia-nine-to-five-game-changelog/ [External Link]

A little news about white label Stadia:
https://9to5google.com/2021/10/20/batman-arkham-knight-white-label-stadia-att/ [External Link]

But still, there is an overdue hardware upgrade that we may never see and Stadia as a whole is losing momentum, big time.

View this comment - View article - View full comments

I know that there are flatpaks and other "sandbox" concept, but why is the core installation sharing "ressources/files/libs/whatever" with optionnal components (post install softwares)... How come installing Steam may mess with basic components from the DE? I mean, couldn't they be 2 separate things, isolated from one another (ex: different copies of the same files)? I'm just wondering and I'm no software engineer. I'm totally aware that it's probably much easier to say than do.

View this comment - View article - View full comments

Not aimed at anybody, but... Some sayings we have in mechanical engineering, when it comes to the risks of "over engineering":

"Make it idiot proof and somebody will make a better idiot." :grin:

Still, this patch is a good thing, imo.

View this comment - View article - View full comments

Quoting: Calinou

Quoting: MohandevirThe FSR maintainers should have a look at DLSS and see what can be integrated that will boost FSR performances... Isn't it open source, afterall?

This is not possible for two reasons:

- The DLSS SDK is proprietary. In fact, even Quake 2 RTX (maintained by NVIDIA) doesn't include DLSS support [External Link] because integrating the DLSS SDK would violate the GPL.
- DLSS requires motion vectors, which makes it much more difficult to integrate in an existing engine. In contrast, FSR is a post-processing shader that can even be injected into applications that weren't designed for it (at the cost of UI elements looking worse than with a "proper" implementation).

I meant Nvidia Image Scaling... DLSS came to my mind as a reflex, but yeah, it was the wrong appellation. Are you meaning that NIS is also locked behind proprietary stuff nonetheless?

View this comment - View article - View full comments

Quoting: chelobaka

Quoting: FredrikI hope someone ports the image scaling, I have been using fsr with proton ge but its very buggy.

I never hit a FSR bug in Proton GE. Works like a charm if a game doesn't do its own upscaling like Control.

Personnal experience... I'm using FSR and ProtonGE with Witcher 3. I get game freezes that don't happen on stable Proton, or Experimental. I mean, one complete freeze per hour of play or so.

Edit: But this said, for this particular game, I never tried ProtonGE without FSR (forgot that part), there is no incentive in doing so; stock Proton (or experimental) is more than enough. It might just be a regression in ProtonGE... Adding this to my list of tests to do...:happy:

View this comment - View article - View full comments

Quoting: CatKiller

Quoting: MohandevirThe bug that quickly comes to my mind, that I personnally witnessed, since switching to Kubuntu, is always happening after an update... Suddenly I can't turn off or reboot the computer. Everytime I get an error message that... I don't remember the name... just crashed. I have to ALT+F4 + CTRL-ALT-DEL to reboot.

If it's the thing I've seen, it's specifically after Nvidia updates. The version mismatch causes the shutdown widget to crash when you try to use it. You can still do sudo shutdown -h now though.

Not really surprised to hear that it's Nvidia related... If I didn't try to do something foolish (I'm not affraid to break an install to try new stuff), GPU drivers are the usual suspect with the majority of my issues, since day one, on Linux... And Windows too, thinking about it... :wink:

View this comment - View article - View full comments

Quoting: Purple Library Guy

Quoting: MohandevirCouldn't they (Intel, AMD & Nvidia... Khronos? Valve?) figure it out together, for once, and come up with one open source standard?

No.

That's what we call a succinct answer. :grin:

View this comment - View article - View full comments