I'd be interesting in if anybody using Stadia on Linux does get a higher resolution than 720p without tweaks? Without tweaks I mean with stock Chrome/Chromium from either Google themselves (e.g. their installer and PPA if Debian/Ubuntu) or via Snap or whatever your Distribution offers. So no Chrome extension like Stadia enhanced, no special vdpau-va-driver package from Chromium Beta/Dev branch.

After complaining that I wasn't able to get 1080p anymore, Stadia replied and wanted to help to get this solved. Of course I had to go through all the possibilities their support asks for (e.g. restarting router, opening ports, using Google DNS, using "Install Stadia" standalone shortcut, using Chrome instead of Chromium, using Brave, enable the "Override software rendering list" flag, etc.). But so far nothing worked. Last statement now is, that their team is looking into this on Linux.

And this sounds to me like no one else told them it's not working on Linux ootb. Which can also mean, only I have this problem and it's working without issues for others. Even though Linux users are tinkerers, and when they get it working, maybe they think it's not worth mentioning anymore. As I do get 1080p with automatic setting on YouTube, Stadia should also be able to autodetect the resolution. Unfortunately they dodged my question about an explicit setting as e.g. Geforce Now offers for setting the resolution on the backend.

So, for those here using Stadia, do you have to use any tweak?

I have to use a tweak, e.g. the Stadia enhanced extension (none of the other extensions works for me anymore), and even here I have to click once through the settings before "native resolution" setting worked. Or I install the vdpau-va-driver (patched for nVidia, from the Chromium Beta/Dev PPA) and I get 1080p in Chrome via PPA or Chromium via PPA (but not in Chromium via Snap). I prefer the possibility to be able to force a setting, so I'm using now Stadia enhanced (thx Liam for the tip).

No matter what I do though, I cannot get hardware acceleration working, at least it never showed MojoDecoder on the chrome://media-internals page.

View this comment - View article - View full comments

Quoting: rustybroomhandleI've briefly popped in to one or two of your Death Stranding streams. It's one of my favourite games of the past few years and it's fun to see other people discover it.

Thanks for stopping by! And yes, it became already one of my favorite games I've ever played already. These little happenings that can occur?

E.g. you have to deliver a package on time, and you think 60 minutes is plenty of time. But you have to get through a MULEs territory. You drive and evade their electro shock sticks as good as you can, you're almost through their territory, only over that bridge... and the last stick hits you! :angry: Dang, car out of service, they catch up, you fight them, you lose and get knocked out... :huh:
K, you wake up again, get the car back, get the lost cargo back... driving again through their territory, as you are really close to get throught... then the battery of your car runs out :woot:

It's so much fun! (you can watch it here [External Link] :D)

Quoting: rustybroomhandleAlso notice how it has a whole screen showing what open source software was used to make it. Mainly just tiny bits, but it's nice that they actually bother to show it.

Yep, I saw that. Very cool indeed!

View this comment - View article - View full comments

Wow... also Death Stranding is specifically mentioned (as it uses the same Engine as Horizon Zero Dawn). Though I didn't have any problems with Death Stranding yet (except a missing texture issue once in 40h game play), I'm happy to see that these updates will also be beneficial to other games.

Atm I'm really enjoying Death Stranding, the graphics, the characters, the story... and I guess I will enjoy Horizon Zero Dawn when I finished Death Stranding as well. Great games, thanks Valve to let us play those AAA games on Linux!

View this comment - View article - View full comments

Quoting: Liam Dawe

Quoting: CorbenBut in Stadia Enhanced I cannot specify anything. I can only enable its overlay. Am I missing something?

It's in the hamburger menu on the main store with Stadia Enhanced.

Oi oi! Works now!

Looks like I had to open it once through the Stadia Symbol of the extension, as I didn't have the hamburger menu at first. Although the default setting for the resolution is "native" I had to to switch once through the settings to make it work, it was still giving me 720 on the first start. But after switching through it, Stadia is now sending in 1080p. Phew, no more tinkering with additional PPAs, yay!

Thank you!

View this comment - View article - View full comments

Quoting: Liam DaweI stopped using Stadia+ and went to the (far better) Stadia Enhanced. Seems to work pefectly, just tested with it today :)

I have tried "The Stadia Plus" (where I can force VP9 and 4K) and also Stadia Enhanced, when this issue arised. But in Stadia Enhanced I cannot specify anything. I can only enable its overlay. Am I missing something? But also the overlay shows only "Software VP9 720p".
As my monitor is FullHD only, enabling 4K via "The Stadia Plus" also doesn't have any effect and still gives me 720p.

View this comment - View article - View full comments

Are you playing in 1080p @Liam? If so, how do you "enable" it?

For me the Stadia+ Extension stopped working, where I was able to force the resolution to 1080p. Now I always get 720p.

All the suggestions Stadia Support gave me (from DNS, Ports, rebooting Router, to using Brave, etc.) didn't work.

My workaround atm on Ubuntu is, to enable the Chromium Beta Repo [External Link], which has a patched vdpau-va-driver. Though Chrome/Chromium Beta still don't show hardware accelerated video, I get 1080p then. Even if I force acceleration (chrome://flags), it still doesn't use it, as the chrome://media-internals page doesn't show MojoDecoder (even shows Enabling MojoDecoder failed). Nevertheless, when I install the vdpau-va-driver, it does give me 1080p again in Chrome. (Not snap Chromium though, but PPA Chromium Beta).

Looks like Stadia disabled the possibility to force the resolution, according to this github issue comment: https://github.com/Mafrans/StadiaPlus/issues/170#issuecomment-804838729 [External Link]

View this comment - View article - View full comments

Quoting: michaI can only say: I plan to buy it once released on Linux. Sorry.

Fair enough, though asking Aaron from Flippfly directly he answered me:

Quoting: AaronI think I can commit to having Linux ready from the private beta forward, which should start this July.

Also, I was able play a prototype with a native Linux binary. I'm confident it'll be released on Linux alongside the Kickstarter progress ;)

View this comment - View article - View full comments

I enjoyed Race The Sun back then, and I'm looking forward to see what this game has to offer. Flippfly have been very Linux friendly, so it's a no-brainer for me to suppor them. Backed it already.

View this comment - View article - View full comments

Quoting: NanobangHey Corben, thanks for the heads up. How would I go about finding this core dump file if I needed to?

For Bioshock 1 Remastered I had a core file below: <your steam game library path>/steamapps/common/BioShock Remastered/Build/Final/core
So directly where the Bioshock.exe file was.

I guess it's a similar path for Bioshock 2 Remastered.

View this comment - View article - View full comments

Interesting to see Bioshock 2 Remastered on the list. I just completed it with Proton 5.13-6, I've just disabled esync, and it was running pretty solid. During my ca 20 hour play through (incl. the DLC), I had like 3 crashes.

Oh, and if it crashes, and even created a core file in the binary's path, make sure to delete the core file, as the game won't start otherwise anymore. Same is true for Bioshock 1 or even the Borderlands games, so it seems to be a 2K thing. It even won't start on Windows anymore if a core file is present, but Windows normally doesn't create a core dump on a crash :D
So it might side-load something on start from a core file.

View this comment - View article - View full comments