You're a smart guy. Let me explain why satellite is the WORST POSSIBLE WAY of gaming.
First and foremost, whats most important when gaming? Latency. Ping.
The higher your ping, the higher your latency.
Now. Whats a ping?. the time it takes for a packet to leave your computer, go to the destination, and return. ping = 'Round Trip Time'
Now. Satellites. They have the bandwidth (pipe diameter) to download, and to game. But the problem with a satellite, lies in ping. Why?
Satellites in geosynchronus orbit are roughly 30,000kms from 'ground level' on earth (Give or take).
Those satellites communicate with a ground station - Usually somewhere like california or texas.
Im going to assume this is one way satellite - Thats BETTER than 2-way. I'll explain why in a second.
With a cable modem, a ping works like this.
The packet leaves your computer, goes up your cable line, is routed around your isp, and sent over terrestrial circuits to the destination host. The packet stops there, and comes back to you via the same (usually) route. Lets take my computer to ninjaserve.com for example:
Quote:
traceroute to www.ninjaserve.com (198.77.7.254), 30 hops max, 40 byte packets
1 192.168.51.1 (192.168.51.1) 1.166 ms 0.285 ms 0.287 ms
2 10.72.0.1 (10.72.0.1) 6.76 ms 5.954 ms 6.644 ms
3 r1-fe2-0-100bt.pego1.on.home.net (24.226.3.1) 7.947 ms 7.057 ms 6.417 ms
4 d226-3-241.home.cgocable.net (24.226.3.241) 11.984 ms 13.771 ms 13.896 ms
5 cgowave-hala-core2.cgocable.net (24.226.0.166) 13.106 ms 13.055 ms 13.897 ms
6 h66-38-197-241.gtconnect.net (66.38.197.241) 16.924 ms 13.628 ms 14.229 ms
7 ge3-1.wana-toroon.ip.grouptelecom.net (216.18.63.1) 13.875 ms 14.831 ms 14.975 ms
8 pos6-0.wana-mtrlpq.ip.grouptelecom.net (216.18.63.194) 35.902 ms 35.492 ms 36.179 ms
9 ge1-0.peera-nycmny.ip.grouptelecom.net (66.59.191.206) 37.009 ms 36.716 ms 35.877 ms
10 nyiix.starlan.com (198.32.160.98) 36.466 ms 35.777 ms 36.202 ms
11 fa4-0-0.core1.nyc1.starlan.com (69.60.129.2) 38.364 ms 37.946 ms 38.067 ms
12 fa0-0-0.edge1.nyc1.starlan.com (69.60.130.2) 39.558 ms 41.506 ms 48.888 ms
13 198.77.7.254 (198.77.7.254) 41.471 ms 41.297 ms 38.737 ms
|
The packet left my computer, took 13ms to get to my isp, (at hop 7) and then a total of 38ms to get to the webserver (hop 13) - These we all land-based optical and/or copper circuits.
With satellite, one way service requires a modem or dsl line for you to do all your packet sending (usually this is low traffic, in the case of an http request (web)) etc.
The path the packet would follow to say
www.ninjaserve.com, would be something like this:
your computer
your dialup isp
your satellite isp
(all the stuff between your satellite ISP and ninjaserve - probably 5+ hops)
ninjaserve
This is where the similarities end. The reason the packet is translated by your satellite isp before its sent to ninjaserve, is so they can tell ninjaserve to send the responses via your satellite link. The server sends the return packet back through those hops to the sat isp's network, at which point they uplink it to a satellite at 38000km+ altitude, its then routed back down to your computer.
Simple in theory, and works great when you are requesting large bandwidth porn streams to your antartic research base. However, your bf1942 packets have to transit a round trip from ground to space ALONE thats almost 80000km's. (Who cares?!?! its moving at the speed of light, right?!?!)
Lets do the math:
Lowball at 70 000 000 meter round trip through space. Speed of light at just under 300000000m/s
(0.23 seconds) - So - Your minimum overhead on a packet is 24ms just for 'space time' - Knowing sat gear, its closer to half a second. Then you add in all the overland overhead to and from the pacfic coast. You're very quickly looking at a full second latency. Make that 2 way, and you have to transit 'space' twice. Also knowing satellite isps, Their actual connectivity SUCKS. On top of that, add in some clouds, weather, and your latency wouldnt suprise me at over 1500ms - If you have any connectivity at all.
make sense?