We do often include affiliate links to earn us some pennies. See more here.

Good news Cloud Gaming fans, as it appears the version of Chrome available on the Steam Deck is now the correct version needed to detect the gamepad. With two small quick fixes, you can play GeForce NOW on Steam Deck easily.

I was waiting on the Chrome update to ship to properly show off Cloud Gaming, which was available in the Dev and Beta versions of Chrome for a little while. You can see on the official Chromium tracker that it has now shipped, and checking the Chrome version on Deck today, it's the same.

Using the version of Chrome available on the Steam Deck, which you can install via the Non-Steam menu in the Steam Library of Gaming Mode, it's possible to tweak it to get it working fully.

  1. To get the Chrome package to work with the Deck controller, you need to do what Microsoft said in their guide for Edge and Xbox Cloud Gaming with this quick terminal command in Konsole in Desktop Mode (with Edge changed to Chrome of course): flatpak --user override --filesystem=/run/udev:ro com.google.Chrome
  2. While in Gaming Mode, you will also want to set Steam Input on Chrome to be in "Gamepad with Mouse Trackpad" mode, along with one edit to set the Right Trackpad click behaviour to be a Left Mouse button. This just enables you to interact with Chrome and click things properly. Any other Steam Input mode, and the Deck Controller will not be picked up by Chrome.
  3. If you want to get rid of the tab bar and have it feel more like an "app", you can also append these to the Launch Options for Chrome: --window-size=1024,640 --force-device-scale-factor=1.25 --device-scale-factor=1.25 --kiosk "https://www.whateverserviceyouuse.com"

Here's a little demo of Fortnite on the Steam Deck, thanks to GeForce NOW:

YouTube Thumbnail
YouTube videos require cookies, you must accept their cookies to view. View cookie preferences.
Accept Cookies & Show   Direct Link

#100, woo-hoo! That's obviously great right. Performance of Fortnite on GFN however isn't amazing (quite stuttery), although I was testing out the Free plan over WiFi.

I should note, I am on the Steam Deck Beta branch, but that shouldn't change anything since the Flatpak package of Chrome will be the same since it's an external package.

Article taken from GamingOnLinux.com.
12 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
12 comments
Page: «2/2
  Go to:

Liam Dawe Oct 11, 2022
Quoting: BrumpoTungusHey, I followed the links here from this video https://www.youtube.com/watch?v=RCVy2BzxzN8&t=127s

I was wondering if you could help me. The creator of the video responded and said he has not had this problem.

The shortcuts work well in desktop mode, no problems. Initially I had a single "instance" or "listing of a non-steam game" of chrome and it worked well in game mode. Then, following the youtube tutorial above, I added listings directed at youtube, disney+, prime video, etc. I changed the names from google chrome to youtube, disney+, etc. and added artwork and added the konsole command shown in the video. I added the suffix in the properties directing each "non steam game" to the specific sites. But now each time I open one of these links in game mode, I get a prompt to sign into google chrome with my email address and password. Does anyone know how to get the browser to remember my login credentials and stay signed in in game mode? Or what might be the cause of the browser constantly needing a sign in?
You're better off posting in Discord or the Forum, rather than commenting on an older article. Support stuff should always be it's own thing.
BrumpoTungus Oct 11, 2022
Quoting: krelltunezEDIT 2: Got it working after pulling out some hair! Turned off the setting allowing Chrome to run in the background. That was causing all my issues because it was trying to keep my PWAs running.

This could solve my issue. Do you know where that setting is located? I cannot find it.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.