I told you this addon always show up the problem " Unfortunately, if you're still on Windows 7 or 8.1 and use Chrome, it doesn't matter if you bought your GPU yesterday — VP9 won't be hardwar...
See more...
I told you this addon always show up the problem " Unfortunately, if you're still on Windows 7 or 8.1 and use Chrome, it doesn't matter if you bought your GPU yesterday — VP9 won't be hardware-accelerated in Chrome. [...] VPx decoding isn’t supported well before Windows 10 creators update.: 616318, 667532 [...]". @spwrozek answer is probably the good one. Also, you have an high latency, for me (EDIT : "Higher latency than me" must be much correct. But I don't think this difference will bother you). Check out how much I have in game : As you can see : - Latency is 7ms VS 48 ms - Jitter Buffer is 26ms VS 39ms - You have compression (probably due to VP9 ? Dunno) - Decoding time is 3ms VS 7ms It's not a huge difference but you can probably optimize Stadia somehow here. With the addon, you can force the use of H264 that is, for me, the solution to your problem. Also, consider that Chrome works a way that impact Stadia performances. Once you have more than 1 tab opened, Stadia performances will be impacted. Also, Chrome use cache. It means that if you, for example, use Chrome, see 10 websites, then close everything and then use Stadia, your performances will be decreased VS launching Chrome then directly start Stadia. EDIT : I'm curious. Could you please provide the same screenshot but on Windows 10 to make a versus ?