It's such a shame those native Linux ports will probably never hit the Linux desktop.

But I'm one of the lucky ones, that have a decent connection, so Stadia runs really well for me. Also seeing Games getting cross-platform multiplayer (e.g. Dead by Daylight, Destiny 2) is very welcome, so it's less of a limitation to Stadia then.
I got lucky with the Premiere Edition of Cyberpunk, as the Chromecast Ultra is a great device to not only be used with Stadia. Netflix, Amazon Prime, Youtube, etc... they all can be used to play videos controlled from e.g. your smartphone to be watched on the TV.

I couldn't imagine, how convenient Stadia has become, and I'm really sad, that some games I'd like to play which have EAC aren't even available to GeForce Now. And I like that I can play (at least some) of the Games from my other Game Libraries (Steam, even Epic). Though that's a Windows machine on the backend, it's a nice way to be able to play games on/from a Linux machine, which wouldn't be playable otherwise (except installing Windows ofc).

So currently my order of preference is: Native, Proton, Lutris/Wine, Stadia, GeForce Now. You might think this should cover all needs a gamer could ever have (PC gaming related), but no... I still can't play e.g. Fall Guys (it's not available via GFN). Well, Shadow PC might be the last resort, but I didn't hear good things about their future lately.

So far I don't regret my Stadia Pro subscription.

View this comment - View article - View full comments

This is great!
Wasn't able to get MangoHud running with Proton 5.13 yet, at least not with 64bit binaries, but it started to work with 32bit binaries again. Let's see if this pre-packaged version changes this. Awesome!

View this comment - View article - View full comments

Quoting: CsokisIt's a still Proton bug!

Proton Github [External Link]

System-wide Vulkan layers like MangoHUD or vkBasalt don't work

With the Beta Update of the Steam Linux Runtime - Soldier, it should start to work again:
Steam Linux container runtime beta update: scout 0.20201124.1 and soldier 0.20201124.0 [External Link]

In particular, tools like mangohud and vkbasalt should be easier to use with Proton 5.13.

And I know people who have it working again, e.g. on Manjaro. I reported the issue [External Link] already, so hopefully it'll start working on Ubuntu soon as well.

View this comment - View article - View full comments

Quoting: whizseProbably worth mentioning in a quick bug report:
https://github.com/flightlessmango/MangoHud/issues [External Link]

When I think about it, my issue might have been, that I used vsync via MangoHud, which is capped FPS to 60, as that's e.g. needed for Dead Space 2, which otherwise is limited to 30 FPS with ingame vsync. :huh:
Need to tinker around with that, but it's probably worth opening an issue, to let other VR user know, if they have the same symptoms.

View this comment - View article - View full comments

Today I learnt, that MangoHud totally killed VR performance for me.
At first I was wondering, what that very little edge on a window was sitting in left top corner of my VR view, I couldn't properly see it, just that something was there. Until someone guessed it could be MangoHud. Oh dear, it was. And after completely disabling MangoHud, by renaming /etc/vulkan/implicit_layers/MangoHud.json, performance was great again.

View this comment - View article - View full comments

Did anyone get MangoHud working with latest soldier runtime and Proton 5.13-2 on Ubuntu yet?
I install it from github, and according to the pressure-vessel log, MangoHud.so gets mapped, but it still doesn't work for me.

edit: It did and still does work flawless with Proton 5.0-10 and before and scout runtime though.

View this comment - View article - View full comments

Quoting: EhvisI'm curious what this means:

 
Fixed an issue that caused Vulkan swapchain creation to fail for full-screen windows when a G-SYNC monitor is connected.

And how it would affect things in practice.

I hope this fixed the issue I have in VR, where there is sometimes a small but noticeable delay. Which I can get rid of by opening the SteamVR dashboard for a moment, but it's still something, that's a bit annoying.

View this comment - View article - View full comments

Maybe also worth mentioning, Proton 5.0-10 got released. Before 5.0-10 was only available as a Release Candidate under the beta branch:

5.0-10:
    Added support for the latest Steamworks SDK.
    Added support for the latest OpenVR SDKs.
    Log directory is now configurable with PROTON_LOG_DIR.

Due to the changes made for 5.13, some things are now indeed different, e.g. MangoHUD doesn't work anymore ootb.
Also the containerization changed the behaviour of the wine prefixes, I had my config folder within the Beat Saber folder symlinked to my Dropbox, which totally doesn't work anymore. So for some games, I still perfer to use pre 5.13, for others (e.g. Drone Swarm) 5.13 is totally needed.

View this comment - View article - View full comments

As Prodeus offered to actively invite users for playtesting (through the new Steam feature ), I was able to have a look at it already. Worked great with Proton [External Link], so I guess the early access version will as well. Which offers the ability for interested gamers to jump in at this phase already.

And gosh does this game feel good :D Fast paced, direct controls, lots of gore, and so nicely colorful. I'm a bit sad, that I missed the kickstarter campaign by only one (or was it two?) days.

View this comment - View article - View full comments

Quoting: ArtenGreat! With 5.0 Everspace 2 closed beta didn't even run. Now i can get into menu, but don't have time to try if i can get further :-(

ES2 closed beta did run with 5.0 (at least for me), but it needed some tinkering. E.g. you had to set the Proton prefix to Win7, otherwise audio didn't work. Which then breaks DX12 for the game, but you could add the Launch parameter '-dx11'.
Also no video playback. Still not with 5.13, but if you set the prefix to win10 again, DX12 works now with pretty good performance (again, at least for me, and 5.13 fixes that audio issue).
Haven't found a workaround to get media foundation to work with Proton 5.13 yet, so I'm using Proton 5.9-GE-8-ST (or 5.11-GE3-MF), with prefix set to win7 and '-dx11' parameter. Game is very much playable with this on my setup.

View this comment - View article - View full comments