I bought the Logitech Huperion Fury G402 mid-price gamer mouse. Up until now I have been using a generic whatever-office-mouse and it has worked flawlessly. Now I get twitching and jumping with the "real" mouse and I started to wonder, can there be compatibility issues with mouses and Stadia? I know some people have reported mouse jumping etc. issues with Stadia but this only started for me after switching mouse.
I have reported this via the app.
I suspect that the mouse polling/refresh rate is the issue here. Check your mouse settings and reduce its polling rate or refresh rate (I guess the name depends on the mouse manufacturer). IIRC, a higher value will likely create the issue that you are encountering.
@1timer : A couple of Chrome flags you can modify to see if they improve or worsen things are the following:
chrome://flags/#enable-pointer-lock-options
chrome://flags/#enable-resampling-input-events
Regards
Glad to see this, that I'm. Not only one. Using a generic cheap mouse works flawless... Using. My razor expensive mouse it jumps and jwrks etc.... Really don't get it. Better the mouse and dpi the worse the controls
I suspect that the mouse polling/refresh rate is the issue here. Check your mouse settings and reduce its polling rate or refresh rate (I guess the name depends on the mouse manufacturer). IIRC, a higher value will likely create the issue that you are encountering.
Wow! I need to experiment with this myself. My Logitech G502 is sketchy in D2, and I know it isn't lag. It's likely the mouse hardware settings, and that really excites me. The Stadia controller experience is nearly flawless, so I was hopeful the mouse experience would catch up soon. With so many different types of mice, settings, and clients there's no way the dev's tested them all. One of the main reasons I purchased Stadia was for mouse and keyboard support in a closed / hack proof environment. So many great games on pc were trashed by hackers, so I can't wait to see where Stadia goes.
@1timer : A couple of Chrome flags you can modify to see if they improve or worsen things are the following:
chrome://flags/#enable-pointer-lock-options
chrome://flags/#enable-resampling-input-events
Regards
Thank you, this solved for me!
but I am curious, why a higher polling rate causes this issue with stadia?. I can use a higher polling rate with shadow without any issues and would like to take advantage of a high polling rate on stadia as well. Are google engineers aware of this issue? Despite being a temporal solution I think this is something that needs to be addressed and completely solved.
@GraceFromGoogle can you forward this to the engineering team? Can you give us updates on this, please?
Thank you guys again!