Your system might not be able to decode the video stream fast enough. This can add a very high latency on your system itself (not related to network latency). Ideally, hardware (GPU) acceleration wi...
See more...
Your system might not be able to decode the video stream fast enough. This can add a very high latency on your system itself (not related to network latency). Ideally, hardware (GPU) acceleration will give the best results, but if your GPU is not able (or not enabled to do that) the the system will resort to software (CPU) acceleration, and that's pretty intensive, and yes, is possible that a 2014 CPU might not be able to do it properly, especially at high resolutions. Start small, go to your Stadia settings > Performance and set it to 720p, see if it works better. Additionally, add (for example) the StadiaEnhanced extension and force the stream to H264. At 720p + H264 the stream will look rather bad, but is the least intensive setting for your system, and it can give an indication as what your system is capable. If you want to check the actual video decoding latency, you can open chrome://webrtc-internals/ (while the game is running) in another tab or window, > select the latest entry, and from the Stats Tables select RTCInboundRTPVideoStream_****. You can find there useful information that can help you understand your issues, info such as: codec: H264 or VP9 decoderImplementation: ffmpeg/libvpx or ExternalDecoder (GPU) totalDecodeTime/framesDecoded_in_ms: on my system this takes for example 2.5 ms. You want this value to be as low as possible. There is a lot more there, but these should be sufficient. Alternatively, to have a better view of the decoding times you can open (from the same Stats Tables) Stats graphs for RTCInboundRTPVideoStream_*** and check again totalDecodeTime/framesDecoded_in_ms, but this time in graph form, very useful too see how fast and stable is the video decoding process.