Buckle up, Stadiites, it's ya boi here to cause a ruckus.
I play Stadia mainly for Destiny 2 - got hooked on three free months last year and stuck around 'cause, honestly, what else do I have to do with my COVID depression? Annnyway - been loving the service for more than a year until...TUESDAY (3/16).
Destiny reset hits, I close down my work Zoom and prepare to continue to disappoint my clan with my mediocre PvP KDA. Five minutes in, I go pixelated for a minute then crash out. Return to Stadia screen. Fine - whatevers. Not the first time it's happened, probably won't be the last.
Log back in and load into a match...BOOM! "You need a better internet connection to play this game"
Log back in...boom. Back in...boom. Spend an hour trying to play...boom boom boom. Returned to Stadia screen each time. Ugh - nothing worse than trying to fix my own tech.
Now it's four days later and after...
- following all of the troubleshoot steps laid out by Stadia troubleshooting
- location services off on macOS, AWDL off, etc
- verifying that my browsers (Edge, Chrome, Chrome Canary) are up to date and running no extensions
- verifying that my OSes (one laptop with macOS BigSur and one with Win10 20H2) are up to date and have all patches
- factory reseting my Google WiFi router and recreating my mesh network (and ensuring that it's got all of its updates)
- replacing my Google WiFi setup entirely with a new Google Nest WiFi I had purchased to setup a family member's new home
- enabling port forwarding on all devices as directed by Google Support
- factory resetting my Cable Modem
- upping my Internet speeds from 100Mbps to 400Mbps
- replacing my Cable Modem entirely to be compatible with the new service
- calling my ISP to ensure that there was no throttling and to 'reset my network connection' as guided by Google Stadia support (I assume the meant to reload my isp config file on my modem and issue a new IP address, they weren't very clear)
- connecting directly to both my old and my new cable modems directly with Ethernet
- successfully running Stadia on my mobile device via Mobile Data without issue
...I still get poor network performance notifications from Stadia (regardless of which app, but usually Destiny 2) and get booted from my session between 2 and 5 minutes.
My internet connection is reporting my 400 Mbps on all speedtests, including the one at: https://projectstream.google.com/speedtest
My ping times to Google's DNS average around 15 ms
My ping times to Stadia.google.com avg around 30 ms
My ping times to other sites averaging around 20 ms
Would be super cool if someone at Google could look around under the hood and see what is causing my issues streaming Stadia titles specifically (when literally nothing else is affected).
Or, if someone 'round here has some advice on which Eldritch ritual it is that can roll time back to Monday evening when I could bury myself into games to ignore all of my life problems, that would be great. : )
Google doesn't take this **bleep** seriously.Its doing that same **bleep** here in August
Hello @NotAGyrados,
I have no direct solution for you but here is my analysis :
- If Stadia wouldn't work, this would be true for everyone I think. I see no reason to have a restriction for some users.
- Always dissociate bandwich capacity with stability. Actually, you have a good bandwich capacity (not the best, but a way suffisent one). I'm not sure with your stability.
- Atm 30ms for a ping of 64 bytes is huge. Really huge. Just look below (in french, sorry !) :
Envoi d’une requête 'ping' sur stadia.com [2001:4860:4802:32::1b] avec 64 octets de données :
Réponse de 2001:4860:4802:32::1b : temps=4 ms
Réponse de 2001:4860:4802:32::1b : temps=5 ms
Réponse de 2001:4860:4802:32::1b : temps=4 ms
Réponse de 2001:4860:4802:32::1b : temps=5 ms
You probably guess it, but your network takes 6 to 7x the time it should. This can probably be the problem as Stadia output near 5 555 555 bytes/s in 1080p (Am I right ? 20 Go/h without considering Gio => 20.000.000.000 bytes / 3600 = 5.555.555 bytes/s).
Also consider using the tracert stadia.com command-line. It determine all the relay your network use to reach Stadia. If one of them have a problem, this can cause troubles using Stadia. Sometimes, using a VPN (or if possible a tunnel to Stadia) improves performances (this changes thoses relay).
Also consider opening your ports (list here).
Thoses values & tests were realized with Netflix 4K used on my TV, Stadia actually running (playing Ys 9), my gf looking at Twitch in 1080p (Source), my 3 cameras on, iPad Pro also running, without QoS Support / use of a router.
Hope this can help you in any way. It's not a "process" to solve your incident, sorry for that.