Ok folks, I have been reading reviews about Stadia, none of them too good, but I am not nearly as critical about things. My attempt here is to be honest about my first interaction with the service, I will give you the facts, you all make your own judgement about it. @Leo @JasonHowell @ant_pruitt
Facts about my Stadia / home network configuration:
Router: Asus AC68U
Wireless Network: 5GHZ
Wireless Speed: 75 to 90mpbs
Strength of Signal at the Router: -35dbm
Strength of Signal at the Stadia Chromecast: -53dbm
Stadia connection: wireless
Stadia Chromecast Distance from Router: 15 ft
Setup Process: Installed with the power adapter that came in the box, loaded updates for the Chromecast, loaded updated for the Stadia controller, added device to my Home, setup my account and secured my Avatar name. Everything was great and seamless, no issues at all. Keep in mind, I am fairly tech savvy, but I think anyone could have figured this out with no issues.
Game startup and app: App launched with no issues, I claimed both games I had coming to me, Destiny 2 and Samurai Showdown (that was a freebee, for some reason). I had everything up and running and playing in under 10 minutes. Could switch from Destiny 2 to Samurai Showdown very quickly, everything happened and worked as expected.
Game Experience: Samurai Showdown - Game launched with no issues or input lag, screen selection was as expected, then I moved into an offline Battle VS a CPU. I didn’t experience anything that looked like an issue with latency, anything that was noticeable. Occasionally, I would see a little jitteriness, but it was not common or impactful. No pixilation, or degradation of the picture.
Game Experience: Destiny 2 - Game launched with no issues or input lag, everything was smooth and without issues. About 2 to 3 minutes in, while I was selecting my character and adjusting my avatar, I noticed some pixilation and blurriness, but it went away quickly. Once the game started, I adjusted my control settings to Legacy / inverted (don’t judge - thank you Goldeneye 64) and began. WIthin about 1 minute or 2, I started seeing messages pop up on the screen that said:
“Attention Contacting Destiny 2 servers”, they were popping up every 15 seconds or so. After about 2 to 3 minutes, the game crashed and said ’ ERROR - Could not connect to Destiny 2 servers. Check your network configuration and try again…Error Code: weasel"
I attempted to the reenter the game and try again, happened exactly the same each time for about 3 times, after that, I gave up. I did recheck my internet connection, everything was exactly the same, still good connection.
Then I tried the setup with my Pixel 3 XL. A little annoying that I needed a USB C to USB C from phone to controller (plus it doesnt come with one in the box), but I will forgive them. Setup for this was quick and easy. Everything looked great, but once I jumped into Destiny 2, exact same thing happened again, nothing different, same network crash.
I hope Google addresses this, and I hope everyone doesn’t just give up on Stadia so fast. Google really just needs to push this out as a BETA, invite only, just like what @karsten said. I don’t mind giving my feedback on it. I will give them time to fix. I trust they will make this work, eventually.
What do you guys think?
UPDATE 2300 hrs, Same day
Game Experience tested on the Computer, as opposed to the Chromecast.
Tried both a Dell XPS 9360 and an Acer Chromebook R11. Had to wire the Stadia controller to the laptops. SIGNIFICANTLY better performance on the computers as opposed to the Chromecast. Biggest issue was input lag, sometimes I would get stuff spinning around aimlessly. But overall on both platforms, Dell 9360 worked better, the Destiny 2 experience was playable and enjoyable. My session never timed out like on the Chromecast. So I will be using this on the Computer for now.
UPDATE 2 1100 hrs the next day:
I didn’t know you could adjust the quality down in the Settings in the Stadia app, I adjusted from best to Balanced. After this, everything worked perfectly on the Chromecast. They really should have this by default set. So far, so good! @ant_pruitt