How do I get an invitation? I'd like to see for myself. In any case, thank you for sharing your experience, yasasvy.
Latency:
Latency is the technical term for "lag", and high latency may result in you experiencing a slower than normal response from a game when you press a button or move a joystick or mouse. Because OnLive games run remotely from your home in an OnLive game data center on game servers, even though your communications to the OnLive data center is at almost the speed of light, there will more latency than if the game were running on the same game server in your home. OnLive technology was designed to keep that latency as low as possible, hopefully to the point where you don't even notice it, and at this stage in OnLive's technology evolution, most OnLive players report that they experience no latency or acceptable latency. But, some players will find the current latency unacceptable in some games. With further development, we know we can reduce the latency further, but you should decide for yourself whether OnLive's current latency is acceptable for your gameplay needs, and the best way to find out is to give the OnLive Game Service a try and play a few free demos.
Got my acceptance letter today, even though I stated on my app that I'm in Anchorage...should be laughable (understandably so). Will try it out tonight and give my impressions. Also going to monitor bandwidth (since I'm capped at 40gb/mo.)
The stills of onlive don't look terrible but they certainly are blurrier/duller, and I'm sure the frame rate won't be anything particularly pleasing.
40GB or gb?
Either way, there are much better ways to receive 40GB/gb than onlive.
Using FRAPS I can see the games are certainly capped at 60FPS. I am not sure how accurate the measurement is though.
Last I checked most monitors these days are at about 60Hz, and you also you expect 100 FPS to be stable over the internet?
start at 35:30, not 34:00
and he is wrong, it isn't about the speed of light, it is about the speed of processors... the gateways, the routers, the chips that encode/decode packets... they are the main cause of latency.
Light takes 0.0053681937522257481207215693198 seconds to travel 1000 miles.
thats 5ms to travel a distance GREATER than the length of texas at its widest. so from a center of each state it should take under 2ms to reach most location in the state.
And electricity propagates at the speed of light
from texas to syndy australia it will take light 46 ms
Tracing route to [URL="http://www.anandtech.com"]www.anandtech.com[/URL] [208.65.201.105]
over a maximum of 30 hops:
1 <1 ms * <1 ms xxx.xxx.xxx [xxx.xxx.xxx.xxx]
2 10 ms <1 ms <1 ms ve8.cosw1.hoer.dk.ip.fullrate.dk [90.185.3.25]
3 1 ms 1 ms 1 ms te2-2.boanxc7.dk.ip.tdc.net [195.215.109.229]
4 31 ms 16 ms 16 ms xe-0-3-0.cr1.lhr1.uk.nlayer.net [195.66.224.37]
5 95 ms 107 ms 94 ms xe-7-0-0.cr1.nyc3.us.nlayer.net [69.22.142.30]
6 100 ms 100 ms 99 ms xe-2-0-0.cr1.iad1.us.nlayer.net [69.22.142.92]
7 100 ms 100 ms 100 ms ae1-40g.ar1.iad1.us.nlayer.net [69.31.31.178]
8 100 ms 100 ms 100 ms r1.vadc1.eicomm.net [69.31.30.218]
9 100 ms 100 ms 100 ms 208.65.201.105
Trace complete.
well I just tried Just Cause 2 and it was a little too sluggish for me. the graphics were much worse looking than me putting the pc version on 720.
about 6800 miles away from here. No matter what ISP I get, the ping hovers around 200ms +
Yeah but still doesn't explain a very consistent result within a same 'zone' if you catch my drift, and each zone has a very consistent drop in speed (or increase in ping) regardless of the ISP, even their topology. Like I said adding whole lot more hops by going thru proxies in other countries had very negligible effects to ping and actual gameplay if any at all. Responsiveness in the game is well noticed and I can easily tell if things are going slower or faster if the ping differs more than by 10ms (played the game for 6 years, I know exactly how much time each action should take).
yeah, but then moving from east coast -> texas -> west coast produces a very linear drop in ping testing with the same methodology. Can't be just something happening on the either end.perhaps it is mostly decoding/encoding at your place and the destination server rather than, with the ISPs equipment not taking any noticeable amount of time.
@Lonbjerg: @66% of c then simply multiply each figure by 1.5x
We are now looking at 1.5*5ms = 7.5ms to go 1000 miles. Lets do the math from the beginning to avoid rounding errors... this gives 8ms @ 1000 miles. Op is 110 miles away, so (avoiding rounding errors) for him light takes 0.9 ms to travel the distance at 66% c.
OP's ping is greater than 0.9ms.
also, http://www.anandtech.com/show/2111/10
Notice how big a difference there is in ping rates with different cards? offloading processing of packets (which I explicitly stated) improved ping by 30ms. (from about 110 ms to 80ms in that test)
I have no idea what your traceroute thing is actually saying, what does each column measure, where does it show time @ each step? Where is the total time?
1 <1 ms * <1 ms xxx.xxx.xxx [xxx.xxx.xxx.xxx]
[B]My connection[/B]
2 10 ms <1 ms <1 ms ve8.cosw1.hoer.dk.ip.fullrate.dk [90.185.3.25]
[B]Our coreswitch...notice the lantency is the same, even if has been routed.[/B]
3 1 ms 1 ms 1 ms te2-2.boanxc7.dk.ip.tdc.net [195.215.109.229]
[B]Another ISP, but in the same country...notice the same lantency, we have routed but travled not far[/B]
4 31 ms 16 ms 16 ms xe-0-3-0.cr1.lhr1.uk.nlayer.net [195.66.224.37]
[B]Notice the ping goes up...moving Denmark to UK[/B]
5 95 ms 107 ms 94 ms xe-7-0-0.cr1.nyc3.us.nlayer.net [69.22.142.30]
[B]Notice the pings go up...moving from the UK to the US[/B]
6 100 ms 100 ms 99 ms xe-2-0-0.cr1.iad1.us.nlayer.net [69.22.142.92]
[B]Moving in the US[/B]
7 100 ms 100 ms 100 ms ae1-40g.ar1.iad1.us.nlayer.net [69.31.31.178]
[B]In the US...but no added lantency, simple routing[/B]
8 100 ms 100 ms 100 ms r1.vadc1.eicomm.net [69.31.30.218]
[B]In the US...but no added lantency, simple routing[/B]
9 100 ms 100 ms 100 ms 208.65.201.105
[B]In the US...but no added lantency, simple routing and at destination[/B]
Pinging [URL="http://www.anandtech.com/"]www.anandtech.com[/URL] [208.65.201.105] with 32 bytes of data:
Reply from 208.65.201.105: bytes=32 time=100ms TTL=59
Reply from 208.65.201.105: bytes=32 time=100ms TTL=59
Reply from 208.65.201.105: bytes=32 time=100ms TTL=59
Reply from 208.65.201.105: bytes=32 time=100ms TTL=59
Ping statistics for 208.65.201.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 100ms, Average = 100ms