Seems Stadia + Google Chrome on Linux leads in input lag turning the experience unplayable.
Tested on vanilla install of chrome (stable 78.03904.108, beta 79.0.3945.45, dev 80.0.3970.5) and all those are affected.
All of those present hardware accelerated as unavailable feature, and this should be the cause of the problem.
Any idea to get rid of the issue?
@ghego :
Some items that I've picked up this week include:
1. Reset Chrome flags - go to the URL chrome://flags , select "Reset all to default", restart Chrome and try again.
2. Run Chrome and use an Incognito window and see if that helps, disable any extensions that might have been added.
3. Reduce refresh rate on mouse pointer (usually a feature on some mouse drivers).
4. Access Chrome flags and enable the feature "Enables pointer lock options".
Can't hurt to see if any of these help with your issue, although apologies if you have tried all of these already.
Running Chrome 78 on Linux Mint here (ethernet, kb+m wired), no lag, no problems.
Any lag is likely caused by your network (or the Internet), assuming that your CPU is fast enough to decode the stream in software. If you can watch 1080p videos fullscreen on YT it should be.
Forgot to mention:
- connection: Eth 1GB to router
- bandwidth: 127.88 Mbps checked with Stadia speed test
- cpu: i5-8350U
- ram: 32 GB
Well, what I can say is that I have a much lower specs than yours, running Ubuntu 18.04, and it runs just fine, also decoding everything via software.
Maybe the problem is something else, probably related to the network? I know the network speed is fine when tested, but maybe your router is not powerful enough to maintain the same latency with Stadia load?
When I bough few years ago the Steam Link I couldn't play with my router because it kept topping it's memory usage and then it started dropping packages, so I replace with a more powerful ASUS router and it everything worked perfectly ![]()
So might be some kind of hardware in the middle of your network (router/modem) that might be adding a bit more delay to it than it should.
just a guess, of course!
I played RDR2 for about 4 hours last night in chrome on my Linux PC using a DS4 controller because my Stadia controller arrives tomorrow. I had zero issues. The game ran better like this than it did on PS4.
Ryzen 7 2700x
GTX 1060 3 GB
16 GB ram
Ubuntu 19.10 with KDE and Vanilla chrome
300 Mbps down and 40 up, wired to the router
After some trial and error i got rid of the input lag.
step 1. Install patched chromium-vaapi
step 2. install vaapi driver
step 2. chromium --ignore-gpu-blacklist --disable-gpu-vsync
the vsync option is what makes the difference.
unfortunately google-chrome is not fixed with these flags
YES !!! IT WORKS !!!
I was having some issues running stadia in "Best visual quality" a lot of lag and frame drops, (running stadia with "limited data usage" work flawless btw)
Just using chromium with those flags ( --ignore-gpu-blacklist --disable-gpu-vsync) did the trick for me, thanks a lot man.
@ghego :
Some items that I've picked up this week include:
1. Reset Chrome flags - go to the URL chrome://flags , select "Reset all to default", restart Chrome and try again.
2. Run Chrome and use an Incognito window and see if that helps, disable any extensions that might have been added.
3. Reduce refresh rate on mouse pointer (usually a feature on some mouse drivers).
4. Access Chrome flags and enable the feature "Enables pointer lock options".
Can't hurt to see if any of these help with your issue, although apologies if you have tried all of these already.
Forgot to reply here for me enabling "Enables pointer lock options" worked fine on popOS!, didn't check yet on Arch
"Enables pointer lock options" doesn't change anything for me.
Well, it's not a general Linux problem - it runs fine for a lot of people, including me on Linux Mint 19.2 Cinnamon + Chrome 79 stable.
For now, until Google gets their linux support in order, set the "Data usage & performance" to "Limited data usage". It was the only thing that helped me get rid of the extreme input lag on my linux setups.
Does anybody know the codec Google is using? VP9? The nVidia driver of my GTX 770 tells me in VDPAU info, that it is only capable of MPEG1, MPEG2, H264, VC1, MPEG4, DIVX4 and DIVX5.
Chrome on Linux does not support GPU acceleration yet unfortunately. I'd advise against using that Chromium with VAAPI enabled, it's a very old version with tons of security issues.
Hi, I'd like to share my experience.
I have a FTTH Internet connection running at 600 MBPS.
I connect all my devices with a 5GHz WiFi connection to it.
The Google Chromecast Ultra wih Stadia controller is working as a charm: optimal video quality, no input lag.
I tested Stadia un some DELL Laptops on the same network; they all have similar specs so hardware is not relevant.
But I tested different OSes:
- MS Windows + Google Chrome: optimal video quality, no input lag, both with keyboard and mouse and with USB connected Stadia Controller
- Ubuntu 18.04 with Google Chrome: optimal video quality; a big issue with input lag making Ghost Recon Breakpoint on Stadia; it is is present with keyboard+mouse but is more evident with Stadia Contrller
After some searches on the Internet it ended up that Google has no plans to support Hardware acceleration for video decoding for Chrome on Linux.
Every attempt to change Chrome flags related to hardware acceleration were useless.
I followed what explained here: https://www.linuxuprising.com/2018/08/how-to-enable-hardware-accelerated.htm: basically installing Chromium Browser pathced with Video hardware acceleration support (VAAPI) and everything is working fine:
Stadia set up with maximum quality, perfect video rendering and no input lag with K+M or Stadia controller.
Hope this can help.
Tried SteamOS yesterday. Installed chrome and feels like on windows. No lags, mouse movement as it should be.