By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Scoobes said:
Imaginedvl said:
Scoobes said:
Pemalite said:
Scoobes said:
thranx said:
If i'm not mistaken doesnt Diablo 3 for PC also use some assets from their own servers and not local based. I forget exactly what and how it works though.

Yes, it did, but it also caused a lot of stuttering issues and lag, especially early on with the heavy server loads. This is for a game that is fairly light on a graphical level.

What Microsoft are claiming here just isn't realistic for a long time.


Even after a year of release I still get stuttering, lag and rubber-banding BECAUSE Blizzard thought it was a great idea not to have a server near-by, so it was a 300ms jump to the US of A instead and a "deal with it" because it's not financially viable. (Yet ISP's here have offered high-speed servers with fantastic CDN's for free to Blizzard, yet they refuse to budge.)

Cloud gaming of any form has never been a smooth experience at all for me.

Exactly why I don't see many devs making efficient use of this. What MS claim in the OP is typical marketing crap. All companies do it but this is pushing it.

No it is not marketing crap. You are just generalizing the "cloud" computing...
For you and many it is like playing remotely to games (like Gaikai or OnLive) or to have a CDN which is TOTALY different from what Microsoft is proposing.

If it is so hard to understand, just compare what their VCPUs with small dedicated servers. Maybe you do not see any potential to that but I see a LOT of potential and idea to use this. I aready gave few exemple in this thread but haters will not even read them as they want to stick on their own "idea" of what Microsoft is proposing... More convenient I guess :)

The only thing Microsoft did wrongly (like many other companies and certainly not by pushing it like you said, I can show you some very good exemple (even recent) from another "big" console company which is way more ridiculous...) is too take as an exemple something about the rendering. While I think it may be used that way; it would be complex for a dev. team to use it in a an efficient way...

But using it to pre-compute the next room/area for instance in a game... Or to process all the background tasks in a persitent world like Skyrim etc...
And then free up the local CPU for other stuff is actually just easily doable...

I just do not get why people are bashing when a company is adding more stuff and possibilities (looking at all the sig, I think I understand why actually :))...
If you "don't" like it just ignore it but it is still a plus at the end for future Xbox owners.

I haven't once mentioned Gaikai so no, that's not what it means to me. The OP/thread title suggests the cloud will give 40x more power than the 360 based solely on the metric that each Xbone will have 3x the computing power of a single console available. Having that power is great but when it's been used in the past (see Diablo 3 and Sim City; not exactly graphically heavy games) the inherent problems of such a system become apparent. The connection drops, the stuttering, the lag... all in what should have been single player games. You can also see similar artifacts occuring in MMOs which again, are mostly poor on a graphical level. It's ludicrous to suggest this is going to make the system as a whole 40x more powerful than a 360.

It doesn't matter how much power you have available if the internet infrastructure isn't there. We may start to see more games take advantage of the tech but it won't truly take off for a long time yet. Either way, it's not going to compare to having that power available locally in a system. It currently works for non-gaming related tasks because the latency isn't as big an issue. 

So yes, this is marketing crap, in the same way all the "theoretical" values the console manufacturers give are over-inflated BS.

The point is that you discard completly the plus it would give to the console devs by just sticking to one of two details (like the title the thread) and even if 80% of the devs out there are not using it; it is still a positive addition to the console toolkit.

Whatever makes you happy, if you think adding this capabilities is just marketing crap, good for you. I do not :)