ReimTime said:
SvennoJ said:
Depends on the video quality and responsiveness you need. That simply glosses over the fact that the video you are watching is buffered ahead to compensate for the variable bitrate at which it arrives at your home. When I do a speed test I average out at 20mbps, however it's full of dips when analyzed further.
even updating hundreds of thousands of these co-ordinates per frame is a relatively small amount of data compared to things like streaming video
Again comparing to what kind of video?
A hundred thousand coordinates per frame is 549 mbps for 60fps in raw data.... Sure you can compress that a lot, yet you can't use lossy compression as used for video. I would take the hundreds of thousands coordinates with a huge grain of salt.
Anyway I guess what they mean is they'll only update collisions while the console will track everything in free fall to keep the data flow under control. Yet can they smooth out the spikes that will generate. It's nice to say you only need 3-5mbps on average, yet if a big explosion needs the equivalent of 50mbps or more for a second things might not look that great. So basically the server will have to work ahead to get the collision data to you ahead of time.
Unlimited CPU is great, depending on unreliable 5mbps for communicating with that unlimited CPU is a huge challenge. I'm curious to see how it will perform in a real world setting with wifi routers serving a bunch of other devices around the house at the same time.
|
From what I read - and again these aren't my words - apparently the maximum bandwidth required is 1.5 mbps to communicate the computations back and forth - so there is no video streaming involved, just communicating computations back and forth. Whether or not that is bs I have no idea; at this early stage I haven't seen any evidence to sway me one way or the other. I am also curious to see how it performs in a real world environment.
|
Ah, that's different from the earlier Crackdown estimates. They were talking about 3 to 5 mbps, which I already thought pretty low.
We'll see, yet 1.5 mbps is only 6.4 KB per frame at 30fps. Or just over 1600 longs (4 byte numbers) about 540 coordinates per frame. It's very little when it comes to usuable data.
Very curious to see the end result. How big the difference is going to be between cloud on and cloud off.
