Originally posted by 2bighorn
Better
Originally posted by FurballFurball, the 206.123.111.42 address is the new collocation address. Yours is better to it.
be interesting to see how people from the other parts of the world do - seems better for yanks so far!
Originally posted by dedalosguess I'll have to pay for my sins, eh?
Good, maybe we will get a fair fight from you now :noid 2BigLagHorn
Originally posted by Skuzzy
Furball, the 206.123.111.42 address is the new collocation address. Yours is better to it.
Originally posted by Skuzzy
Bullethead, everything after your second hop is moot. That is where your trouble starts. Have you forwarded this to anyone at Level3 yet? I would. I'll also be pointing the potential new ISP/collocation to this thread and see what they think as well.
Originally posted by hitech
Bullet Head, You have it backwords I belive, the MA is the new server i.e. the one with better ping times and less hops for you.
Originally posted by Skuzzy
Bullethead, everything after your second hop is moot. That is where your trouble starts. Have you forwarded this to anyone at Level3 yet? I would. I'll also be pointing the potential new ISP/collocation to this thread and see what they think as well.
Originally posted by MotleyCH
I'm not complaining..just giving details.
Pings here from work, were 13 to 18 about 6 months ago..then went into the twenties after the last server move.
Now they are 39+/-
Originally posted by Schutt
206.123.111.42 145AVG 144MIN 147MAX - more steady
206.16.60.38 149AVG 141MIN 158MAX - a bit jumpy
The .42 seems to be slightly better for me.
Target Name: N/A
IP: 206.16.60.38
Date/Time: 01.03.2006 23:49:27
1 0 ms 0 ms 0 ms 0 ms 0 ms localhost [192.168.1.1]
2 22 ms 19 ms 21 ms 21 ms 21 ms dslb-082-083-192-001.pools.arcor-ip.net [82.83.192.1]
3 19 ms 20 ms 21 ms 22 ms 22 ms han-145-254-11-205.arcor-ip.net [145.254.11.205]
4 22 ms 22 ms 23 ms 22 ms 21 ms hmb-145-254-18-146.arcor-ip.net [145.254.18.146]
5 23 ms 24 ms 22 ms 23 ms 23 ms so-2-0-0.ar2.ham1.gblx.net [64.215.181.93]
6 111 ms 112 ms 110 ms 112 ms 111 ms so2-1-0-2488M.ar1.DCA3.gblx.net [67.17.67.57]
7 -32764 ms -32764 ms * 350 ms * mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.194]
8 * * * * * mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.194]
9 * * * * * [-]
10 27 ms 34 ms 38 ms 30 ms 39 ms att-3.ar1.DCA3.gblx.net [208.50.13.254]
11 54 ms * * 51 ms * tbr1-p011701.wswdc.ip.att.net [12.123.9.114]
12 * 24 ms 33 ms * * tbr1-p011701.wswdc.ip.att.net [12.123.9.114]
13 26 ms 25 ms * 27 ms * tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
14 * * 17 ms * * tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
15 10 ms 18 ms 10 ms 5 ms * tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
16 12 ms 22 ms 17 ms 21 ms * gbr2-p100.dlstx.ip.att.net [12.122.12.82]
17 11 ms 8 ms 17 ms 16 ms * gar1-p370.dlstx.ip.att.net [12.123.16.237]
18 7 ms 14 ms 10 ms 5 ms * mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255.170]
19 153 ms 148 ms 156 ms 155 ms * [206.16.60.38]
Target Name: argon.gamerslobby.net
IP: 206.123.111.42
Date/Time: 01.03.2006 23:44:38
1 1 ms 0 ms 0 ms 1 ms 0 ms localhost [192.168.1.1]
2 21 ms 55 ms 22 ms 20 ms 21 ms dslb-082-083-192-001.pools.arcor-ip.net [82.83.192.1]
3 21 ms 2 ms 19 ms 21 ms 19 ms han-145-254-11-205.arcor-ip.net [145.254.11.205]
4 26 ms 55 ms 25 ms 26 ms 24 ms ffm-145-254-16-38.arcor-ip.net [145.254.16.38]
5 26 ms 24 ms 25 ms 24 ms 24 ms ge-3-2.a00.frnkge03.de.ra.verio.net [213.198.77.137]
6 24 ms 54 ms 26 ms 24 ms 25 ms ge-1-3-0-4.r01.frnkge03.de.bb.verio.net [213.198.52.222]
7 26 ms 1 ms 24 ms 26 ms 27 ms p16-3-0-0.r00.frnkge02.de.bb.verio.net [129.250.5.38]
8 -32764 ms 68 ms 25 ms 27 ms 25 ms p16-2-0-0.r01.frnkge02.de.bb.verio.net [129.250.3.195]
9 34 ms 1 ms 39 ms 31 ms 33 ms p16-7-1-2.r21.amstnl02.nl.bb.verio.net [129.250.5.6]
10 192 ms 30 ms 255 ms 225 ms 255 ms ge-0.internap.dllstx09.us.bb.verio.net [129.250.12.118]
11 83 ms 100 ms 84 ms 115 ms 84 ms p16-2-3-3.r21.asbnva01.us.bb.verio.net [129.250.5.87]
12 23 ms 320 ms * * * [206.123.64.98]
13 * * * * * [-]
14 * * * * * [-]
15 5 ms 6 ms 7 ms 5 ms 9 ms xe-1-3-0.r20.asbnva01.us.bb.verio.net [129.250.2.170]
16 * 37 ms 36 ms 37 ms 38 ms p16-0-1-1.r21.dllstx09.us.bb.verio.net [129.250.5.34]
17 * * * * * [-]
18 7 ms 58 ms 5 ms 7 ms 5 ms xe-4-1.r03.dllstx09.us.bb.verio.net [129.250.3.226]
19 42 ms 341 ms 22 ms 20 ms 21 ms border4.ge3-1-bbnnet1.ext1.dal.pnap.net [216.52.191.30]
20 20 ms 6 ms 22 ms 21 ms 19 ms colo4dallas-3.border4.ext1.dal.pnap.net [216.52.189.10]
21 23 ms 3 ms 22 ms 24 ms 22 ms [206.123.64.38]
22 -32764 ms -32764 ms 22 ms 23 ms 21 ms [206.123.64.98]
23 237 ms 170 ms 148 ms 149 ms 148 ms argon.gamerslobby.net [206.123.111.42]
Originally posted by pigface
frame rates ok
Got white screen booted after I got shot down.. when I hit the dirt got a hard crash... not just the plane.
Originally posted by Wizer
Same
Originally posted by Skuzzy
Also, when you say 'worse', 'better', or 'same', is that based on game play or other information?
Originally posted by Skuzzy
feem is quite right.
One thing I did forget to ask about, and that is who your ISP is, and what region of the world are you located in? Thank you all again for the help.
Also, when you say 'worse', 'better', or 'same', is that based on game play or other information?
Originally posted by SkuzzyWorse, based on 10 traceroutes - averaging 156ms (21 hops) to 206.16.60.38 and 194ms (18 hops) to 206.123.111.42. Also, in the arena selection screen, ping times to other arenas are lower than to MA. TeliaSonera ADSL (8/1Mbps), Tampere, Finland.
One thing I did forget to ask about, and that is who your ISP is, and what region of the world are you located in? Thank you all again for the help.
Also, when you say 'worse', 'better', or 'same', is that based on game play or other information?
Originally posted by Skuzzy
feem is quite right.
One thing I did forget to ask about, and that is who your ISP is, and what region of the world are you located in? Thank you all again for the help.
Also, when you say 'worse', 'better', or 'same', is that based on game play or other information?
Raleigh, NC Sprint 3MB DSL
--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 64.743/65.250/65.879/0.423 ms, pipe 2
--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9009ms
rtt min/avg/max/mdev = 60.384/60.819/62.077/0.548 ms, pipe 2
Durham, NC SunGuard Dual OC3
--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9080ms
rtt min/avg/max/mdev = 49.487/49.873/50.188/0.373 ms, pipe 2
--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9088ms
rtt min/avg/max/mdev = 45.462/45.774/45.992/0.194 ms, pipe 2
Portland, OR AT&T T1
--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% loss, time 9089ms
rtt min/avg/max/mdev = 60.707/61.223/62.649/0.635 ms
--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% loss, time 9084ms
rtt min/avg/max/mdev = 63.546/63.745/64.549/0.335 ms
Suak Rapids, MN 3mb Cable
10 packets transmitted, 10 received, 0% loss, time 9089ms
rtt min/avg/max/mdev = 44.001/46.044/51.885/2.223 ms
--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% loss, time 9092ms
rtt min/avg/max/mdev = 44.873/51.313/64.855/6.659 ms
Billings, MT 2mb Cable
--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9089ms
rtt min/avg/max/mdev = 54.797/57.493/66.340/3.406 ms, pipe 2
--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9090ms
rtt min/avg/max/mdev = 53.460/56.416/63.730/2.981 ms, pipe 2
Memphis, TN AT&T 128k ISDN
--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9084ms
rtt min/avg/max/mdev = 91.873/93.483/95.215/0.954 ms, pipe 2
--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9093ms
rtt min/avg/max/mdev = 90.855/92.676/94.190/1.073 ms, pipe 2
Newport, NC RoadRunner 5mb Cable
--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% loss, time 9093ms
rtt min/avg/max/mdev = 54.500/55.849/57.558/0.905 ms
--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% loss, time 9091ms
rtt min/avg/max/mdev = 52.853/54.106/55.510/0.781 ms
Originally posted by PanzzerCurrently: 206.123.111.42, 18 hops, averaging 226 ms. 206.16.60.38, 21 hops, averaging 163 ms.
Worse, based on 10 traceroutes - averaging 156ms (21 hops) to 206.16.60.38 and 194ms (18 hops) to 206.123.111.42. Also, in the arena selection screen, ping times to other arenas are lower than to MA. TeliaSonera ADSL (8/1Mbps), Tampere, Finland.
Originally posted by Skuzzy
feem is quite right.
One thing I did forget to ask about, and that is who your ISP is, and what region of the world are you located in? Thank you all again for the help.
Also, when you say 'worse', 'better', or 'same', is that based on game play or other information?
Originally posted by hitech
Screen Freezes are not related to connections.
Originally posted by hitech
Screen Freezes are not related to connections.
Originally posted by Skuzzy
In general, a pause in the screen is related to the CPU being busy or the video card stalling. The more players there are in your area, the more data your computer has to process.
If you select game settings which overload your video card, then you can experience stutters as well.
Originally posted by g00b
You might lose 1 percent of your customers, but the gameplay will increase 100% and that will attract more customers.
My 2 cents!
g00b
Originally posted by hitech
Screen Freezes are not related to connections.
Originally posted by outbreak
Well something on the server is making it happen to a jack rabbit load of peeps, On the old server the game ran like Clockwork, No Flinches in the screen or anything, Since the server update when im flying and could be 100+ miles away from any fighter or fight at that, Still get screen lockups on occasion, Its since the move to the new server i noticed these, Not on the old but on the new, And they are very annoying, And if more people are having it since the new move to this server then its not our Systems, My FR stays 40-70 and i still have lock-ups, i use about 199.00mb of my 512.00mb available, use 49.03mb of my 128.00mb Graphics card, So in no way when a freeze happens is it because of my system. Its only SINCE the move to the NEW SERVER. :cry
Originally posted by Skuzzy
In general, a pause in the screen is related to the CPU being busy or the video card stalling. The more players there are in your area, the more data your computer has to process.
If you select game settings which overload your video card, then you can experience stutters as well.
Originally posted by 4510
Boxboy,
I see you are in Tucson. Maybe it is an Arizona thing. I am down in Sierra Vista. Last night I flew in the MA for the first time since the change and saw a bunch of "wierdness". No discos fortunately, but had someone comment to me about "nice warp" and saw some warps. I shot a YAK point blank with a K4, had parts slam into my plane (thought I collided) and then the YAK just didn't exist anymore. No kill credit, no falling plane, no explosion, it just ceased to exist as if it had never been there.
My other Tucson based Arizona squaddie and I could not agree on our DAR. He would see my DAR counter over A10 and be looking to join up with me, I was flying over A53.
So I echo your comments. I can't explain WHY.. only that it IS. And these are issues that didn't exist prior to the change.
Originally posted by outbreakThe server is physically the same server. Identical. It is just connected to a different ISP.
Well something on the server is making it happen to a jack rabbit load of peeps, On the old server the game ran like Clockwork, No Flinches in the screen or anything, Since the server update when im flying and could be 100+ miles away from any fighter or fight at that, Still get screen lockups on occasion, Its since the move to the new server i noticed these, Not on the old but on the new, And they are very annoying, And if more people are having it since the new move to this server then its not our Systems, My FR stays 40-70 and i still have lock-ups, i use about 199.00mb of my 512.00mb available, use 49.03mb of my 128.00mb Graphics card, So in no way when a freeze happens is it because of my system. Its only SINCE the move to the NEW SERVER. :cry
Originally posted by BoxboyWho said ot cannot be the server because ping times are better? The server is the same server. Identical. Phyiscally moved from one location to another.
Skuzzy, outbreak and I are in the same boat, before the move no problems after the move all kinds of stuff is happening mine freezes, disco's, etc etc.
Now from a layman's POV nothing has changed on our end but something has changed on your end. The next thing we hear from HTC is that it cannot be caused by the move to the new server because ping times are better. Our refain is "it wasn't happening prior to the move". On it goes round and round, but I have to tell ya that if it remains like it is now I will be unable to continue because the game at the moment is, for me, unplayable.
Originally posted by SlapShot
The thread " How is the Main Arena connection for you?" was not good enough for this info ?
Originally posted by plank
Geez, it's the guys first post, could have just told him sans the uppity attitude.
Originally posted by Zazen13
On the previous ISP's/locations my ping to the server would get longer and longer the more people that were online. ...Zazen
Originally posted by Morpheus
What do BKs have to do with this?