PureBasic Forums - English

OnLive 48 Mins Video Demonstration

OnLive is a gaming-on-demand game platform, announced at the Game Developers Conference in 2009.[1] The service is a gaming equivalent of cloud computing: the game is synchronized, rendered, and stored on a remote server and delivered online. The service was announced to be compatible with any Windows PC running Windows XP or Windows Vista, or any Intel-based Mac running OS X and on smartphones.

http://www.viddler.com/explore/gamertagradio/videos/160/169.707/

I don't believe that this is actualy working.

It is something completly different than streaming a movie. Just think about how bad are the control responses are. You hit a key on your keyboard. The client transfers the keycode to the server, the server processes it and renderes the next frame, compresses the frame and sends it to the client, the client receives it and displays it. Doing this and having a fluid gaming experience seems to be impossible at the moment.

On the other hand think about the enormous server clusters needed to run this service. Actualy the server would need much more calculation power than it would need if rendered on the client. There is not only the rendering to be done way faster than the actual FPS. All frames needs to be compressed extremly fast. I just can't believe that this is even near to something we can call economic.

Just saw the video and he said it does it all in 80ms. Well that would be 12,5 FPS. Not awesome at all.

Why would this be more beneficial than having the game on your computer?

It's not beneficial for the user, it only prevents piracy for the developer. Cloud computing is a stupid concept. All your data and apps controlled by someone else, and dependent on both you having an always-on internet connection and them always having their servers running? Yeah, that's smart. :roll:

Thorium wrote:I just can't believe that this is even near to something we can call economic.

Word!

Sure stuff like this is technologically possible, but not economically.
If they manage to pull this off I will be positively surprised.

Thorium wrote:Just saw the video and he said it does it all in 80ms. Well that would be 12,5 FPS. Not awesome at all.

He also said "assuming the server is within 1000 miles".

But the FPS is faster than 12 FPS I believe, the 80ms delay is the delay before you can see the response to your action, not the delay it takes for each frame to be sent. It's just like a normal video stream; and I guess it might have 30 FPS.

But great video btw, it was very interesting!

The worst part is: Here in portions of the USA at least... The empty suits with their MBA degrees have decided to charge a premium price for bandwidth speeds and are trying to start a charge for amounts transferred via bandwidth like it was in the bad old days!!!

That is gonna kill ANY hoipe that cloud computing is anything other than a raincloud on the horizon!

Nice video though.

"Just because you can doesn't mean you should.
- Acheron Parthenopaeus"

True that quote!

Thank you for the link, most interesting !

Blood wrote:C provides the infinitely-abusable goto statement, and labels to branch to. Formally, the goto is never necessary, and in practice it is almost always easy to write code without it.

I'm a proud user of GOTOs in my programs, especially for managing rare fatal errors but not only, or to skip tons of code if something bad is happened. I like this a lot more than a never-ending five arms long nesting of nice structured code. This is particular true in a language like PB where the concept of exception handling (in its modern meaning) is not present (if you exclude the on error). At the end the generated code is unstructured ASM, and the reality is everyone should code in the way he makes him more comfortable and productive. But I don't believe in laws, except maybe in physics.

luis wrote:But I don't believe in laws, except maybe in physics.

That could almost be a quote from 'Sledgehammer'

The great Sledge

I'm a proud user of GOTOs in my programs, especially for managing rare fatal errors but not only, or to skip tons of code if something bad is happened. I like this a lot more than a never-ending five arms long nesting of nice structured code. This is particular true in a language like PB where the concept of exception handling (in its modern meaning) is not present (if you exclude the on error). At the end the generated code is unstructured ASM, and the reality is everyone should code in the way he makes him more comfortable and productive. But I don't believe in laws, except maybe in physics.

We'll said
greetings
cw

Thorium wrote:Just saw the video and he said it does it all in 80ms. Well that would be 12,5 FPS. Not awesome at all.

You can see from the video it's much more than 12.5 fps.

luis wrote:I'm a proud user of GOTOs in my programs

Read my sig again, he he...

Blood wrote:

Thorium wrote:Just saw the video and he said it does it all in 80ms. Well that would be 12,5 FPS. Not awesome at all.

You can see from the video it's much more than 12.5 fps.

Actualy the video could be fake. Easyiest thing would be to just run the service over LAN. There is no prove that it runs over internet and they never said it runs over a standart connection. Could be direct line to the server. The Videos on the selection screens could be prerecorded.

Seeing is believing but it's not allways the truth. Especialy not on presentations. They worked on that for over 1 year and must have invested a lot of money. They know if they fail with that project, they are screwed. So they show the people what the people want to see. I mean thats not the first company promising technology, showing it and then vanishing.

Joakim Christiansen wrote: But the FPS is faster than 12 FPS I believe, the 80ms delay is the delay before you can see the response to your action, not the delay it takes for each frame to be sent. It's just like a normal video stream; and I guess it might have 30 FPS.

It couldn't be like a normal video stream. If it is like a normal video stream then the server have to predict the actions of the player. Just imagine you move your mouse. There must be a notable delay in the actual moving of your hand and the moving on the screen. The moving of the mouse is fluid, the 80ms delay would kill the fluidness. So the server need to interpolate the movement. Not a big problem, but interplation does not kill the huge delay, to kill it the server need to predict the movement of the mouse. Which is possible but if the prediction is wrong you see actions on the screen you havnt done on the client.

Blood wrote:Read my sig again, he he...

Why ? Well... OK.

K&R (same book) wrote: C provides the infinitely-abusable goto statement, and labels to branch to. Formally, the goto is never necessary, and in practice it is almost always easy to write code without it. We have not used goto in this book.
Nevertheless, there are a few situations where gotos may find a place. The most common is to abandon processing in some deeply nested structure, such as breaking out of two or more loops at once.

Done. You can read my original reply again too, if you wish !

I was talking about exception handling too...

http://www.8051projects.net/out.php?lin ... /goto.html

You remember me of a past user of the forum, he was a great quoter too.

But I'm not trying to force anyone here. Do as you feel it's right !

Bye !

GOTO rulez!!!


And I remember a CES where a certain computer company (not MAC) was demoing their new baby and if you peeked behind the curtain you saw there were a bunch of MACs actually running instead!!!

Ahhh presentations!!! The Coleco Adam looked good too! until you realized that when you started it if ANYTHING magnetically sensitive was within 8 feet of the CPU it would be wiped out!!!

I miss my Atari 800XL