WARNING, IMPORTANT EDIT:
Try this if you have problems applying the original solution.
Some people seems to have problems applying the 2 options that disable vsync and frame rate limit. This 2 options is the better solution (in my opinion) to reduce input lag. But if you have some problems after applying it, you can try with only vsync parameter:
--disable-gpu-vsync
The input lag also is reduced with this option and the other problems probably disappear.
So you can try with 2 options explained below and go back to this warning if you experience some problems
BEST OPTION ARE THE 2 OPTIONS:
To check if you are doing well this configuration you can use this website:
If you see 4 VSYNC words in the right side you have vsync disabled (enjoy the games with less input lag)
If you see 1 gray VSYNC word, you don't have the 2 options to improve latency
------------------------
The improvement of latency is very noticeable with the mouse.
You can check adding this in the trail of desktop shorcut path, (click in shorcut with right click and select properties):
--disable-gpu-vsync --disable-frame-rate-limit
Here the example image:
EDIT:
Don't forget to put a space before--disable-frame-rate-limit, don't forget to close all windows of google chrome and launch chrome with this changes
If you are using Mac you can run this command on terminal:
open -a "Google Chrome" --args --disable-gpu-vsync --disable-frame-rate-limit
To disable mouse acceleration in Mac system execute this command in the terminal:
defaults write .GlobalPreferences com.apple.mouse.scaling -1
or use SteelSeries ExactMouse Tool
Hi @TekoRaiK
thanks for providing the related shortcut line,
Please report your idea via the Stadia app.
Definively I think that vsync improve a lot. I think that google stadia should allow to disable via Stadia App
I went from having one gray vsync with no red or cyan to 4 vsync that are flashing red and cyan constantly, is this better?
Thanks for the post, very clear and organized.
I think this Vsync problem is a bug with some Nvidia cards. I hope they solve it soon. I don't understand why Stadia is taking so long to solve that. Is a critical problem.
Alternative Solution
Another tip is to use the Stadia Web App shortcut. After installing it in the Stadia website (to install click on the + on the right side of your address bar), you can find the Stadia App shortcut in your Start Menu inside the Chrome Apps folder. Click with the mouse right lick on the Stadia shortcut ---> More ---> Open file destination. After you can do exactly what was suggested in this post.
On the shortcut proprieties click on shortcut tab copy this --disable-gpu-vsync --disable-frame-rate-limit and paste it after the chrome_proxy.exe" in the destination field and before the --app-id=.
Example: "C:\Program Files (x86)\Google\Chrome\Application\chrome_proxy.exe" --profile-directory=Default --args --disable-gpu-vsync --disable-frame-rate-limit --app-id=(your app id)
After save it and use the shortcut to start Stadia. It should start as a webapp and not as a regular website.
Alternative Solution B
You also can do this in the Nvidia Control Panel and force Vsync off inside the 3D settings for Google Chrome only. This is a great solution because does not require a shortcut. But it will disable Vsync for all websites.
Hi, when I enter the code I keep getting The folder "C:\Program Files\Google\Chrome\Application" specified in the Start In box is not valid. Make sure that the folder exists and that the path is correct.
You said if you see 4 VSYNC words I'm good... what if I see 2? What does that mean? I don't have an nVidia graphics card and am using a laptop with Intel graphics... does that have anything to do with it?
Hi @Ballz,
Thanks for commenting on this post. I did just want to give a heads up, that since it is an older topic, it may not get any responses. If you would still like some help on this subject, I'd recommend creating a new post to give it some more visibility. With that said, I am going to go ahead and lock this topic for now. Looking forward to seeing you around again!
Best,
James