OnLive One Step Closer
hysma writes "It looks like OnLive, the remote gaming system that streams HD video over the Internet, is one step closer to becoming reality, according to an article on DSL Reports in response to a lengthy video presentation by founder & CEO Steve Perlman at Columbia University. Perlman demonstrated the UI, spectating, using the service on an iPhone, and other features."
Until round trips between the server and client are guaranteed to be under 50ms, the lag will feel unbearable. If someone is playing a racing game and has to deal with a second between the time they begin turning and the time they actually see it turn this service will be dead before it begins.
I also strongly doubt that any kind of game on this platform can be enjoyed by people who are sensitive to input latency. For example my old high quality PVA TFT panel used an overdrive circuit to reduce ghosting. The overdrive logic in TFT panels usually buffers about 1 or 2 full frames to analyze and optimize the pixel voltages which leads to about 20-50ms input latency. I for one already notice it when I just work to the point where it annoys me when the desktop or terminal sessions somehow always feel sluggish, let alone fast 3D games.
I can't imagine that the complete round-trip time for sending my input over the internet, waiting for a frame to be rendered and encoded remotely, sent back over the internet, decoded and displayed locally would be less than 20ms and then you'd still have the latency of your display. It might be bearable with a very fast internet connection and a CRT display which has 0ms input latency.
Maybe others aren't that sensitive to latency and can enjoy at least slower games like turn-based strategy with this service. Good for them.
the richer control setup of keyboard and mouse.
It's really only the mouse---you can make a perfectly fun FPS that's playable with the buttons on, say, a wiimote plus nunchuk (one stick for moving, 8 buttons in B/C/Z/d-pad/A).
What's really missing is the fine-grained relative motion of the mouse.
It needs to be fine-grained; anyone who has tried to aim with a joystick will understand why.
It needs to be relative, as anyone having played Metroid Prime 3: Corruption on the Wii will know.
Roughly speaking, you point at an absolute point on the monitor plane; your character yaws and pitches gradually to aim at that point, the speed being monotonously increasing in the distance between your current aim point and the target aim point.
What are the implications? Either you point at where you want to shoot and it takes a while to aim there, or you point way past where you want to shoot and you get to where you want to go really fast but move away again really fast.
What you really want to do is overshoot by infinity (or $BIGNUM), then aim at the target point when your character points exactly at it: then you get to your target fast and stay there. This is virtually impossible, and trying to do it is unpleasant.
That's why you need a mouse for FPSs; you can make games that only take 8 buttons, so I don't buy the "you need a keyboard". Maybe specific FPSs require keyboards, and maybe there's really no way to design around that without making the game a different game---I'll buy that. But really it's the mouse.
I still maintain that this simply can't work, and that it's an absolutely braindead money pit of an idea if it's not a total scam.
Idea: let's take the most latency sensitive, computationally demanding, and visually intensive thing you can do with a modern computer and try to apply the thin client model to it.
A single instance of the application in question will demand the full resources of the most powerful PC you can throw at it, but we'll just wave our hands and mutter something about virtualization to convince stupid investors that we have magic at our disposal. Because they are morons and because we put on a good show, they'll believe that you can somehow run many instances of a game on the equivalent of a single PC. We'll also be encoding 720p video in realtime at a quality / bandwidth ratio that no codec today can deliver; this will presumably happen on the same computing hardware that's already running multiple instances of cutting edge 3D games.
Finally, we'll throw in some shit about the iphone, because people can't stop fellating apple lately.
Anyone who believes this is technically feasible, much less economically viable, is fucking *retarded*.
Is to rent console time over the Internet, to people with enough money to have a PC that will run this stuff, and a fast Internet connection... ...or an iPhone, a platform known for its cost-effective pricing model... ...but don't want to buy their own console, because it would clearly be too expensive?
Of course, people don't want to all play computer games at the same time, so I can see they'll be balancing load throughout the day... erm... or not (and certainly, they're not going to be running connections internationally with latency that's anything less than abominable for this).
In summary: WTF?