The mouse sensitivity is completely bananas, and the Mouse Sensitivity menu option has ZERO effect. (it also causes the game to momentarily freeze each time it's adjusted)
I own Everspace on Steam, and that version works perfectly with almost identical settings.
The only difference being the Steam version has the "Use System Mouse Position" option (which is checked). This option doesn't appear in the Stadia version.
I'm running with Windows mouse acceleration ('Enhanced Pointer Precision') disabled, with a Logitech G403 @ 2880 DPI (1000 polls/s).
Google, you need to properly test your games with Mouse & Keyboard on Stadia.....
...and for the love of all that is holy, MANDATE THE INCLUSION OF FOV SETTINGS!!!
It's as if you're hiring two-bit software houses to cobble together half-assed console ports for your platform =/
Checking other games, I've found Hitman's mouse sensitivity makes it extremely hard to play too.
At least the sensitivity settings do something in this game, but, even with the absolute lowest sensitivity (0.5), aiming down sights is made very difficult due to the mouse sensitive.
Is this a widespread issue with Stadia's mouse support that's gone unnoticed? or a particular incompatibility with my setup?
The latter seems unlikely, as I've never encountered problems with any game outside of Stadia, and I'm not running a particularly 'special' setup.
Same in Sniper Elite 4 on Stadia; I have to set my sensitivity to the absolute minimum value for the game to be playable.
Worked out what the cause was; it's a bug in the Stadia Chrome client.
When it reports mouse values to the server, it isn't accounting for the Windows pointer speed setting.
Thus, if you have your Windows pointer speed setting very low, and your mouse software sensitivity setting high, the mouse will be uncontrollably sensitive when playing Stadia through Chrome.
Native applications do not suffer from this issue, as they either correctly factor in both these sensitivity settings, or bypass system sensitivity settings entirely by polling the raw hardware values.
Try setting chrome flag "Enables pointer lock options" to enabled.
Go to chrome://flags and search for that setting.