dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
40
Skittles_
join:2012-03-26

Skittles_ to pheonix

Member

to pheonix

Re: [Networking] Online Gaming on HughesNet

said by pheonix :

These are my average ping times

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Dustin.Dylan-PC>ping yahoo.com -t

Pinging yahoo.com [98.139.183.24] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 98.139.183.24: bytes=32 time=1103ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1251ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1260ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1529ms TTL=47
Request timed out.
Request timed out.
Reply from 98.139.183.24: bytes=32 time=1342ms TTL=47
Request timed out.

Ping statistics for 98.139.183.24:
Packets: Sent = 10, Received = 5, Lost = 5 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1103ms, Maximum = 1529ms, Average = 1297ms
Control-C
^C
C:\Users\Dustin.Dylan-PC>ping google.com -t

Pinging google.com [74.125.227.36] with 32 bytes of data:
Reply from 74.125.227.36: bytes=32 time=1315ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1242ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1772ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1636ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1764ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1691ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1842ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1602ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1844ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1769ms TTL=49

Ping statistics for 74.125.227.36:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1242ms, Maximum = 1844ms, Average = 1647ms
Control-C
^C
C:\Users\Dustin.Dylan-PC>ping dslreports.com

Pinging dslreports.com [209.123.109.175] with 32 bytes of data:
Request timed out.
Reply from 209.123.109.175: bytes=32 time=1027ms TTL=50
Request timed out.
Reply from 209.123.109.175: bytes=32 time=1087ms TTL=50

Ping statistics for 209.123.109.175:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1027ms, Maximum = 1087ms, Average = 1057

Sucks right?

Well, for me it kind of jumps around.

You see, when I put in ping google.com, it gave me many mixed results, I tried it about 7 times. So basicly for me my ping is somewhat unstable. The lowest ping I could get was in the 800s and the highest is 1776. So yeah. :l

I also have Halo Reach here (Just matchmaking):

UNPLAYABLE. I can get into the matchmaking lobby, but the game will never be able to connect to a match.

pheonix
@direcway.com

pheonix to Doc Lithius

Anon

to Doc Lithius
These are my average ping times

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Dustin.Dylan-PC>ping yahoo.com -t

Pinging yahoo.com [98.139.183.24] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 98.139.183.24: bytes=32 time=1103ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1251ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1260ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1529ms TTL=47
Request timed out.
Request timed out.
Reply from 98.139.183.24: bytes=32 time=1342ms TTL=47
Request timed out.

Ping statistics for 98.139.183.24:
Packets: Sent = 10, Received = 5, Lost = 5 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1103ms, Maximum = 1529ms, Average = 1297ms
Control-C
^C
C:\Users\Dustin.Dylan-PC>ping google.com -t

Pinging google.com [74.125.227.36] with 32 bytes of data:
Reply from 74.125.227.36: bytes=32 time=1315ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1242ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1772ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1636ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1764ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1691ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1842ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1602ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1844ms TTL=49
Reply from 74.125.227.36: bytes=32 time=1769ms TTL=49

Ping statistics for 74.125.227.36:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1242ms, Maximum = 1844ms, Average = 1647ms
Control-C
^C
C:\Users\Dustin.Dylan-PC>ping dslreports.com

Pinging dslreports.com [209.123.109.175] with 32 bytes of data:
Request timed out.
Reply from 209.123.109.175: bytes=32 time=1027ms TTL=50
Request timed out.
Reply from 209.123.109.175: bytes=32 time=1087ms TTL=50

Ping statistics for 209.123.109.175:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1027ms, Maximum = 1087ms, Average = 1057

Sucks right?

Doc Lithius
join:2009-08-19
Rock, MI

Doc Lithius

Member

I should also mention something else about Phantasy Star Online: Blue Burst on HughesNet. Don't try and multitask. The game doesn't like sharing a connection and if your ping gets above a certain point, it automatically bumps you off regardless of where you are or what you're doing.
Doc Lithius

1 edit

Doc Lithius to Sangheili

Member

to Sangheili
said by Sangheili:

So i am wondering if anyone else can test this for me?
The server i play on (the only one really still alive) is PSOBB schtak
i would greatly apreciate this being tested.

- Phantasy Star Online: Blue Burst, SCHTHack server (Fully Playable*) -- Strangely enough, this game is completely and fully playable under HughesNet -- at the very least, in One Person mode. The only snags I've experienced are a delay when picking up items and the occasional failure to log in. (The game gets stuck on the code screen after updating.) As for in-game, the game seems to compensate for you hitting enemies and vice versa just fine, so the game works. ... provided the SCHTHack people can keep their servers up and running for more than a day at a time. They've apparently screwed something up in their latest update so it closes web browsers and blocks the "play as an NPC" program now. It's all very depressing. Nevermind, that's all been resolved. The game is working fine, aside from closing any program that has words like "cheat" or "trainer" in the window title. Regardless of what they are. Hah!