|
tater_salad posted:Google says it shouldn't be doing this, so either a whoops or bad support agent. Gotta be honest dude, I appreciate that you're shooting down bullshit complaints with evidence because it's unfair to judge them based on illegitimate statements... but this would not have been nearly as much of a problem if they had just told us all these things before it launched. Instead they just left it a mystery product until the day it launched just like the rest of their product/service releases and it would've saved them a lot of trouble to be more clear and open. CJacobs fucked around with this message at 14:26 on Nov 24, 2019 |
# ? Nov 24, 2019 14:19 |
|
|
# ? Apr 27, 2024 21:50 |
|
the threads most ardent stadia supporter believed rdr2 would be 4k 60 fps until the day it launched the biggest of google lies but i still appreciate all the hilarious other ways google is failing, keep it coming
|
# ? Nov 24, 2019 14:22 |
|
GamersNexus figures for latency testing (published about an hour ago) show that plugging the controller into a PC via USB and running Stadia that way seems to result in noticably lower response times than using the controller wirelessly while playing via an Ethernet wired Chromecast Ultra. I guess Google's claims about the direct connection from controller to server being better didn't really hold up.
|
# ? Nov 24, 2019 14:42 |
|
Bofast posted:GamersNexus figures for latency testing (published about an hour ago) show that plugging the controller into a PC via USB and running Stadia that way seems to result in noticably lower response times than using the controller wirelessly while playing via an Ethernet wired Chromecast Ultra. I guess Google's claims about the direct connection from controller to server being better didn't really hold up. Yea wired is always going to be faster. A more like for like test would be stadia controller vs. bluetooth but if I remember correctly they don't allow that at all.
|
# ? Nov 24, 2019 14:53 |
|
an actual dog posted:Yea wired is always going to be faster. A more like for like test would be stadia controller vs. bluetooth but if I remember correctly they don't allow that at all. Wait why would that be faster. The laptop / chromecast would be wirelessly connected anyway. What Google promised was that your controller was directly connected over WiFi skipping the step of connecting through a device that was also connected with WiFi. Controller (wire) PC (WiFi) Router (???) Stadia vs Controller (WiFi) Router (???) Stadia They walked back the WiFi promise for most use cases. But the chromecast WiFi connection should still hold.
|
# ? Nov 24, 2019 15:03 |
|
doingitwrong posted:Wait why would that be faster. The laptop / chromecast would be wirelessly connected anyway. What Google promised was that your controller was directly connected over WiFi skipping the step of connecting through a device that was also connected with WiFi. Atomizer posted:(Note that these two devices are both wired in the same room to the same Ethernet switch.) Wifi has a ton of overhead that can add latency. There's a constant dance of negotiation because only 1 thing can be on the air at a time. It's not much latency on average, but it's not stable because sometimes a problem with negotiation can add 20 or 100 ms of wait time. OTOH a USB connection only adds a few ms of latency over the wire, so if the computer or whatever is quick about turning the controller's command around it may not be significant. These things are going to be very context dependent though. If you have the ideal environment for wifi -- no neighbors and no other devices active -- cutting out that middleman probably shaves off a trivial about of time. But the other and more normal case is cluttered APs from neighbors and multiple devices on the wifi.
|
# ? Nov 24, 2019 15:45 |
|
Bofast posted:GamersNexus figures for latency testing (published about an hour ago) show that plugging the controller into a PC via USB and running Stadia that way seems to result in noticably lower response times than using the controller wirelessly while playing via an Ethernet wired Chromecast Ultra. I guess Google's claims about the direct connection from controller to server being better didn't really hold up. Oh, were they able to find a phone that wasn't 8 years old? As far as how the service works in less than ideal conditions (my home is about as ideal as it gets and it's perfect), I've tried it out this weekend while visiting the in-laws. They are not in a major urban area, 3 hrs to the nearest city. I'm on a poo poo DSL+wifi setup, 20mbps down and my ping is 70-100ms, with a bit of jitter. Destiny and Grid were solidly playable for me, but definitely not excellent. Input lag was very very tolerable for most of my play, minus a few short hiccups. I wouldn't say it would be great for PvP, but for most single player games it works. This is part of what makes the service great, in my opinion. I can take my controller anywhere and use it on any screen and it works. That convenience factor is pretty powerful. hostile apostle fucked around with this message at 16:08 on Nov 24, 2019 |
# ? Nov 24, 2019 15:58 |
|
doingitwrong posted:Wait why would that be faster. The laptop / chromecast would be wirelessly connected anyway. I was assuming the PC was a wired connection
|
# ? Nov 24, 2019 16:02 |
|
Yea I just watched the video it's all ethernet
|
# ? Nov 24, 2019 16:08 |
|
Atomizer posted:I believe the Google retaliation that you described, but I was asking if the original scenario (i.e. the conditions that led to the retaliation) involved the codecs & hardware acceleration situation that I mentioned. https://news.ycombinator.com/item?id=18697824 posted:"For example, they may start integrating technologies for which they have exclusive, or at least 'special' access. Can you imagine if all of a sudden Google apps start performing better than anyone else's?"
|
# ? Nov 24, 2019 16:21 |
|
Here's something that baffles me: The Project xCloud beta is free (as any beta should be). I tried it out on my phone, because like hundreds of millions of people, I have an android phone. It worked well enough, and there are a bunch of actually great games included with the service. Neat. I even reported a bug or two. I have an nVidia Shield with GeForce Now streaming. It too is a free beta. It's got a gigantic library of full priced, current titles. It pretty much works fine. Stadia is not free. I can't try it out on any of my existing hardware, because my LG V30 isn't a Pixel. If I want to play anything other than free to play games on the service, I need to pay full price for the title. I can never sell or trade that license, and if I cancel the service, there is no refund. From all accounts, if you can get it to work, it works fine, but the support is hot garbage when it exists at all. Why (the gently caress) would anyone pay for this? How is this competitive in any reasonable way? The experience is objectively less mature than two of its direct competitors which are in free public beta right now. I'm honestly asking.
|
# ? Nov 24, 2019 18:04 |
|
hostile apostle posted:Oh, were they able to find a phone that wasn't 8 years old? lol
|
# ? Nov 24, 2019 18:18 |
|
70-100ms of latency “with hiccups” does not sound “solidly playable”.
|
# ? Nov 24, 2019 18:20 |
|
hostile apostle posted:Destiny and Grid were solidly playable for me, but definitely not excellent. Input lag was very very tolerable for most of my play, minus a few short hiccups. for someone who seems to be going out of their way to defend their purchase itt, you're really not making this sound like an appealing experience for the vast majority of Americans.
|
# ? Nov 24, 2019 18:27 |
|
LORD OF BOOTY posted:this is very clearly and obviously a way to goose demand for Google Fiber and put some corporate will behind expanding it, now that it's otherwise basically stalled out This is a fine sounding conspiracy theory in a vacuum, but falls apart if you understand the US telco monopoly network. Google's "corporate will", manpower and cash on hand are less than 1% of the problem with expanding Google Fiber. It's entirely a political problem, and not a single player is working with the consumer's best interest in mind, least of all Google.
|
# ? Nov 24, 2019 18:36 |
|
Dr. Fishopolis posted:I have an nVidia Shield with GeForce Now streaming. It too is a free beta. It's got a gigantic library of full priced, current titles. It pretty much works fine. Hi fellow Geforce Now user! I've noticed that in the weeks leafing up to Stadia's release getting on a rig took a long time, but since Stadias release it's been nearly instant every time. Have you noticed this too, and I wonder if it's connected to the release...
|
# ? Nov 24, 2019 19:40 |
|
I'm baffled at how much Google lied/oversold their tech. Their sales pitch was that games would run better than any single PC with the power of the cloud but can only run RDR2 at 4K/30FPS. It seems the reviews on Football Manager are mixed as well. My hunch is that Sony will end up having a huge share of the streaming market that develops. PSNow has been around forever, they are starting to advertise it, and I imagine they will push it hard along with the PS5. I played MGS4 on PSNow and it worked fine 3 years ago. It wasn't optimal, but I didn't have a PS3 at the time. If Sony sells it being able to play your library on the go /PS5 games on your PS4 with a subscription they will eat Google's lunch. They might not, as the streaming market might be fairly small.
|
# ? Nov 24, 2019 19:48 |
|
Bofast posted:GamersNexus figures for latency testing (published about an hour ago) show that plugging the controller into a PC via USB and running Stadia that way seems to result in noticably lower response times than using the controller wirelessly while playing via an Ethernet wired Chromecast Ultra. I guess Google's claims about the direct connection from controller to server being better didn't really hold up. Ok I just watched the full GN vid and the difference is not just noticeable, it's a consistent 25 or 50ms. That's huge! I was wrong, that is not explainable just from wifi latency! options I can think of: 1. This is a beta and the controller isn't actually doing the direct connection to the servers yet. Instead it is connecting to the chromecast via wifi, and the chromecast is processing and sending the commands to the server. And that explains why you have to use it wired with anything else: without the chromecast it's still just a dumb controller. 2. The controller is connecting directly to the server, but it sucks as an independent device and takes 10s of ms to go from input to sending the packet. 3. Something else; why did Thumper only have 25ms of latency while everything else was way worse? Thumper had the best latency results across the board since the other 3 titles seemed to run at 30fps or even worse. But I can't understand why the additional wifi latency would be proportionate, unless the controls are somehow also being put in packets tied to framerate? Hypothesis #1 could be tested by examining what's happening on the network.
|
# ? Nov 24, 2019 20:09 |
|
I'm pretty sure option 1 is currently true and coming later. You need to wire the controller to anything not the Chromecast Ultra.
|
# ? Nov 24, 2019 20:12 |
|
So, wait: do you HAVE to have an android phone to use this? Like, as an iPhone user, would I be unable to use Stadia if I decided, for some reason, to buy one?
|
# ? Nov 24, 2019 20:23 |
|
As of right now the storefront where you set up the device and buy games is Android only I believe. edit; there's an iOS app.
|
# ? Nov 24, 2019 20:25 |
|
Presenting Nipples posted:I'm baffled at how much Google lied/oversold their tech. Their sales pitch was that games would run better than any single PC with the power of the cloud but can only run RDR2 at 4K/30FPS. It seems the reviews on Football Manager are mixed as well. It actually only runs RDR2 at 1440p/30FPS and it appears to be at mostly medium settings but they send you a 4k video of it. My 3 year old GTX 1070 can apparently run RDR2 better than The Power of the Cloud. Regrettable fucked around with this message at 20:34 on Nov 24, 2019 |
# ? Nov 24, 2019 20:29 |
|
Stadia RDR2 is 1440/55fps actually.
|
# ? Nov 24, 2019 20:31 |
|
American McGay posted:Stadia RDR2 is 1440/55fps actually. Okay, well, my 3 year old 1070 still matches that at a mixture of medium and high settings.
|
# ? Nov 24, 2019 20:40 |
|
Marmaduke! posted:Hi fellow Geforce Now user! I've noticed that in the weeks leafing up to Stadia's release getting on a rig took a long time, but since Stadias release it's been nearly instant every time. Have you noticed this too, and I wonder if it's connected to the release... Honestly, I mostly use my Shield for streaming MHW from my PC to my living room, I haven't actually logged into Geforce Now since I played through Spec Ops: The Line and bummed myself out real hard. edit: which, incidentally, looked and played fine at 1080p with the usual expected input lag and streaming artifacts. I never noticed any major stuttering or hitches with that game, nor with Resident Evil 7, MK11 or Prey. edit2: all of which you have been able to play for free for years now, which is crazy. Dr. Fishopolis fucked around with this message at 21:01 on Nov 24, 2019 |
# ? Nov 24, 2019 20:52 |
|
The controller is connected directly through the wifi, it doesn't connect to the Chromecast
|
# ? Nov 24, 2019 20:54 |
|
hostile apostle posted:The controller is connected directly through the wifi, it doesn't connect to the Chromecast
|
# ? Nov 24, 2019 20:56 |
|
it also overheats and shuts down due to really poor thermal design. the solution is (i am not making this up) to tape heatsinks to the case.
|
# ? Nov 24, 2019 21:04 |
|
Dr. Fishopolis posted:it also overheats and shuts down due to really poor thermal design. The solution is wait for the rubes to betatest and buy revision 2
|
# ? Nov 24, 2019 21:06 |
|
That's making the sizeable assumption that google doesn't get distracted by a passing butterfly and forget any of this exists in 6 months time
|
# ? Nov 24, 2019 21:10 |
|
limaCAT posted:The solution is wait for the rubes to betatest and buy revision 2 chromecast has had overheating issues forever, google just doesn't give a poo poo 8 months ago: https://www.reddit.com/r/Chromecast/comments/b6l9bn/i_found_the_perfect_heat_sink_for_my_overheating/ 16 months ago: https://www.reddit.com/r/googlehome/comments/92eg11/had_overheating_issues_with_the_chromecast_not/ 28 months ago: https://www.reddit.com/r/Chromecast/comments/6qiu82/chromecast_ultra_tearing_itself_apart_due_to_heat/ even the original 1080p chromecast had overheating issues but they ignored the problem so it got even worse when they stepped up to 4K
|
# ? Nov 24, 2019 21:13 |
|
man, google's a rubbish company, isn't it?
|
# ? Nov 24, 2019 21:16 |
|
Dr. Fishopolis posted:I have an nVidia Shield with GeForce Now streaming. It too is a free beta. It's got a gigantic library of full priced, current titles. It pretty much works fine. Also they're "full priced" in that you have to buy the games yourself, but you can take advantage of Steam sales, Humble Bundles, etc. Right now you can buy the Tomb Raider trilogy + DLC for $43.5 on Steam whereas they would cost $100 on Stadia. --- So while looking up prices I read Tom's Hardware review of Stadia and it talked about connection optimization: quote:Here's my issue: When I played Shadow of the Tomb Raider on a 1080p TV, the performance was extremely smooth, even though the graphics sometimes had a blurry, washed-out quality that has never been present when I've played Tomb Raider on consoles. The background textures, in particular, were not very distinct. But the framerate was excellent (60 frames per second, or thereabouts), and the game didn't slow down, even during firefights or graphically intense chase sequences. GeForce Now allows you to set your bit rate to anywhere from 5 to 50 Mbps, the quality from 720p to 1080p, the frame rate to 30, 60, or 120 fps (although 120fps is only available if you set it to Competitive which locks the resolution at 1280x720 and doesn't let you set the bit rate), and to allow it to automatically adjust the quality if your connection degrades/improves, whereas Stadia apparently...can't.
|
# ? Nov 24, 2019 21:17 |
|
google stadia!
|
# ? Nov 24, 2019 21:26 |
|
American McGay posted:Stadia RDR2 is 1440/55fps actually. As per the DigitalFoundry videos I watched, there's 2 modes this game can run in: the "lower" one is 1080p and targets 60 fps but hangs mostly somewhere in the fifties, and then the "4K" one that's actually 1440p at 30 fps. They seemed to think that the consistently 30 fps mode felt nicer.
|
# ? Nov 24, 2019 21:36 |
|
hostile apostle posted:Oh, were they able to find a phone that wasn't 8 years old? They were able to buy a new code that worked from a viewer. Their original code got caught in limbo because they use a google org email. hostile apostle posted:The controller is connected directly through the wifi, it doesn't connect to the Chromecast Ok, so why does that add 25 to 50 ms of lag versus connecting the controller to a PC and playing in a web browser? The possibility that it isn't working yet because it's an unfinished beta product is the best option. That means might get fixed!
|
# ? Nov 24, 2019 21:38 |
|
I am actually struggling to believe the “taping heat sinks to it” solution.
|
# ? Nov 24, 2019 21:40 |
|
Lots of small cheap decoder devices like that run extremely hot. I've got the option of buying a $70 HDMI USB capture device and having plenty of ice cubes handy or opting for the $250 version that contains a heatsink and fan.
|
# ? Nov 24, 2019 21:43 |
|
Pathos posted:I am actually struggling to believe the “taping heat sinks to it” solution. When you could dry berries with it, too!
|
# ? Nov 24, 2019 21:46 |
|
|
# ? Apr 27, 2024 21:50 |
|
lol i found one from *5* years ago https://www.youtube.com/watch?v=7NsWumVkTrc keep entombing your devices in non-ventilated and non-conductive plastic google, i'm sure the problem will go away by itself
|
# ? Nov 24, 2019 21:53 |