Jump to content
SubSpace Forum Network

Recommended Posts

Posted

I try to play hyperspace, EG, TW and others. Im specced in some zones and am just laggy in others.

 

My ploss for about 3 years was 0.1% constant. My ping never exceeded 30ms for the same amount of time.

 

About a month ago my ploss is now around .2% Server To You  and 1.5% to 4.0% You To Server, with a ping around 40ms though.

 

 

Why is my ploss constantly high now? Heres a trace..

 

Tracing Zone: SSCU Trench Wars  IP Address: 66.36.241.110

Hop IP Address      Host Name                        Loss(%) Min/Avg/Max Ping
--- --------------- -------------------------------- ------- ----------------
  1 xxx.xxx.xxx.xxx Wireless_Broadband_Router.home      0.0      0    0    0
  2 98.109.156.1    L100.NWRKNJ-VFTTP-101.verizon-gn    0.0      0    0  160
  3 130.81.109.126  G3-0-2-1701.NWRKNJ-LCR-07.verizo    0.0      0    0   10
  4 130.81.29.8     so-5-0-1-0.NWRK-BB-RTR1.verizon-    0.0      0   10   80
  5 130.81.23.192                              0.0      0   10   60
  6 152.63.16.9     0.ae5.BR3.NYC4.ALTER.NET            0.0     10   10   50
  7 4.68.111.137    te-7-3-0.edge2.NewYork2.level3.n    0.0      0   10   70
  8 4.69.138.222    vlan51.ebr1.NewYork2.Level3.net     0.0     10   10   50
  9 4.69.132.89     ae-3-3.ebr2.Washington1.Level3.n    0.0     10   10   50
 10 4.69.134.154    ae-82-82.csw3.Washington1.Level3    0.0     10   20   60
 11 4.69.149.132    ae-32-80.car2.Washington1.Level3    0.0     10   50  220
 12 ...             ...                                 0.0   1000000    0    0
 13 ...             ...                                 0.0   1000000    0    0

Cycles: 101

Posted (edited)
slow rendering

whats your fps

Im not sure how to check fps in subspace, but when i go here http://ie.microsoft.com/testdrive/performance/fishIETank/default.html

 

i get 55-60+ fps when I use 50 fish or below but sometimes it dips down to 28-32 so its sporadic, and when i go to 100-500 fish i get like 15-25fps with dips to 9fps..

 

do you think my frame rate could be responsible for ploss though?

 

 

Also, I just cleaned my computers fan out with a dust blower, and I have had norton 360 running for the last year so it cant be any sort of adware or virus..

Edited by ronaldmcdonaldTW
Posted

Hit escape, then F in Continuum to show the FPS counter, it will show up as a red number at the top.

 

Also, if you're playing over a wireless network, you will get some packet loss, especially if there are other devices on the network.

Posted (edited)
Hit escape, then F in Continuum to show the FPS counter, it will show up as a red number at the top.

 

Also, if you're playing over a wireless network, you will get some packet loss, especially if there are other devices on the network.

oh thanks. then it shows at 170 fps on average. i still am completely stumped. my ping is constant at 30 or 40, and ever since 1 month ago or so, my "YouToServer" ploss went from 0.1% to 1.5 to 4.0% . every day its over 1.5% without fail. "ServerToYou" is 0.1% always.

 

also, im playing with a modem that is basically cable from the wall, although it does have wireless capability its not used. theres only 2 computers that use this modem and both use cables from the wall basically. also, we have used it this way for 3-4 years and this ploss just started 1 month ago, so i highly doubt anything is related to the modem.

 

im still stumped.

Edited by ronaldmcdonaldTW
Posted

Looks like I have the same problem.  Was fine for years (0.1% just like ronald) but sometime in late 2011/early 2012 I started having this problem.  Couldn't find a solution for it for months and then sometime in mid-2012 the problem seemed to just go away.  Then about two days ago the ploss came back.  When I first saw your post (my ploss had been fine for months at this point) I did a trace:

 

 

Tracing Zone: SSCU Trench Wars  IP Address: 66.36.241.110
 
Hop IP Address      Host Name                        Loss(%) Min/Avg/Max Ping
--- --------------- -------------------------------- ------- ----------------
  1 192.168.1.1                               0.0      0    0    0
  2 10.9.44.96                                 0.0      0   10   70
  3 130.81.110.36   G3-3-897.BSTNMA-LCR-08.verizon-g    0.0      0   10   70
  4 130.81.29.254   so-0-3-0-0.BOS-BB-RTR2.verizon-g    0.0      0   10   70
  5 130.81.19.66    so-7-2-0-0.NY5030-BB-RTR2.verizo    0.0     10   20   90
  6 152.63.2.81     0.xe-3-1-0.BR3.NYC4.ALTER.NET       0.0     10   20   50
  7 4.68.111.137    te-7-3-0.edge2.NewYork2.level3.n    0.0     10   20   80
  8 4.69.138.222    vlan51.ebr1.NewYork2.Level3.net     0.0     10   20   60
  9 4.69.132.89     ae-3-3.ebr2.Washington1.Level3.n    0.0     20   20   40
 10 4.69.134.150    ae-72-72.csw2.Washington1.Level3    0.0     20   30   50
 11 4.69.149.68     ae-22-70.car2.Washington1.Level3    0.0     20   50  240
 12 ...             ...                                 0.0   1000000    0    0
 13 ...             ...                                 0.0   1000000    0    0
 
Cycles: 112
 

 

 

After the problem started again I did another trace:
 
Tracing Zone: SSCU Trench Wars  IP Address: 66.36.241.110
 
Hop IP Address      Host Name                        Loss(%) Min/Avg/Max Ping
--- --------------- -------------------------------- ------- ----------------
  1 192.168.1.1                               0.0      0    0    0
  2 10.9.44.96                                 0.0      0   10   40
  3 130.81.109.62   G3-3-797.BSTNMA-LCR-07.verizon-g    0.0      0   10   30
  4 130.81.29.252   so-0-3-0-0.BOS-BB-RTR1.verizon-g    0.0      0   10   50
  5 152.63.18.222   0.ae3.BR1.NYC1.ALTER.NET            0.0     10   20   80
  6 4.68.62.41      ae11.edge2.NewYork.Level3.net       0.0     10   30  110
  7 4.69.138.222    vlan51.ebr1.NewYork2.Level3.net     0.0     10   20   70
  8 4.69.132.89     ae-3-3.ebr2.Washington1.Level3.n    0.0     20   30   70
  9 4.69.134.154    ae-82-82.csw3.Washington1.Level3    0.0     30   40   70
 10 4.69.149.132    ae-32-80.car2.Washington1.Level3    0.0     20   70  440
 11 ...             ...                                 0.0   1000000    0    0
 12 ...             ...                                 0.0   1000000    0    0
 
Cycles: 133
 
I still have no idea what the problem is or how to fix it though.
Posted (edited)

Looks like I have the same problem.  Was fine for years (0.1% just like ronald) but sometime in late 2011/early 2012 I started having this problem.  Couldn't find a solution for it for months and then sometime in mid-2012 the problem seemed to just go away.  Then about two days ago the ploss came back.  When I first saw your post (my ploss had been fine for months at this point) I did a trace:

 

 

Tracing Zone: SSCU Trench Wars  IP Address: 66.36.241.110
 
Hop IP Address      Host Name                        Loss(%) Min/Avg/Max Ping
--- --------------- -------------------------------- ------- ----------------
  1 192.168.1.1                               0.0      0    0    0
  2 10.9.44.96                                 0.0      0   10   70
  3 130.81.110.36   G3-3-897.BSTNMA-LCR-08.verizon-g    0.0      0   10   70
  4 130.81.29.254   so-0-3-0-0.BOS-BB-RTR2.verizon-g    0.0      0   10   70
  5 130.81.19.66    so-7-2-0-0.NY5030-BB-RTR2.verizo    0.0     10   20   90
  6 152.63.2.81     0.xe-3-1-0.BR3.NYC4.ALTER.NET       0.0     10   20   50
  7 4.68.111.137    te-7-3-0.edge2.NewYork2.level3.n    0.0     10   20   80
  8 4.69.138.222    vlan51.ebr1.NewYork2.Level3.net     0.0     10   20   60
  9 4.69.132.89     ae-3-3.ebr2.Washington1.Level3.n    0.0     20   20   40
 10 4.69.134.150    ae-72-72.csw2.Washington1.Level3    0.0     20   30   50
 11 4.69.149.68     ae-22-70.car2.Washington1.Level3    0.0     20   50  240
 12 ...             ...                                 0.0   1000000    0    0
 13 ...             ...                                 0.0   1000000    0    0
 
Cycles: 112
 

 

 

After the problem started again I did another trace:
 
Tracing Zone: SSCU Trench Wars  IP Address: 66.36.241.110
 
Hop IP Address      Host Name                        Loss(%) Min/Avg/Max Ping
--- --------------- -------------------------------- ------- ----------------
  1 192.168.1.1                               0.0      0    0    0
  2 10.9.44.96                                 0.0      0   10   40
  3 130.81.109.62   G3-3-797.BSTNMA-LCR-07.verizon-g    0.0      0   10   30
  4 130.81.29.252   so-0-3-0-0.BOS-BB-RTR1.verizon-g    0.0      0   10   50
  5 152.63.18.222   0.ae3.BR1.NYC1.ALTER.NET            0.0     10   20   80
  6 4.68.62.41      ae11.edge2.NewYork.Level3.net       0.0     10   30  110
  7 4.69.138.222    vlan51.ebr1.NewYork2.Level3.net     0.0     10   20   70
  8 4.69.132.89     ae-3-3.ebr2.Washington1.Level3.n    0.0     20   30   70
  9 4.69.134.154    ae-82-82.csw3.Washington1.Level3    0.0     30   40   70
 10 4.69.149.132    ae-32-80.car2.Washington1.Level3    0.0     20   70  440
 11 ...             ...                                 0.0   1000000    0    0
 12 ...             ...                                 0.0   1000000    0    0
 
Cycles: 133
 
I still have no idea what the problem is or how to fix it though.

 

it might be a problem with verizon but for me it happened just a few months ago. doing a trace on TW's zone IP shows no packet loss but checking the packet loss in game using "udp" or user defined packets shows huge packet loss. I had 17% loss tonight for example.

 

my friend who was nice enough to try and help me told me it might be because my IP address is stale. So i had verizon try to break the lease and give me a new IP address, but when they tried to do that it wouldnt work (ip address stayed the same). so they shipping out a new modem to me to see if that fixes it.

 

overall, i dont know what the problem is, im just attempting trial and error right now. i find it really strange that i go from 0.1% packetloss everyday for a few years, then to 4% to 20% daily. and it never shows when i do a ping trace, only when i do ?packetloss in game, meaning the UDP is whats wrong here im guessing.

 

ill let you know if a new ip address/modem does the trick. if anyone else has any tips... 

 

 

For me, i can only think of 3 reasons why this is happening:

 

1) verizon changed something recently and it affects user defined packets. (possible but why only affect subspace and not other things).

2) Subspace and the zones changed something recently and its affecting the same. (unlikely since it only affects certain/few people).

3) Some ridiculously stupid and easy solution like a stale IP or something else like refreshing something lol (usually the case when nobody can point out the obvious given the symptoms).

 

hopefully its 3

Edited by ronaldmcdonaldTW
Posted
Are you getting the speeds from your ISP that you are supposed to be getting? Did you ISP change something about the network which can sometimes cause older cable modems to have issues?

 

my speeds are perfect on everything except subspace. i did tons of ping traces (although they dont trace UDP) and it all comes up perfect. As far as i know my ISP didnt reveal anything changed when I asked, but they are somewhat stupid too.

 

my modem is about 3-4 years old, and im replacing it in a day or two, so ill see if thats it.

Posted (edited)

FIXED. It was the stale IP. As soon as I installed a new modem (same brand/style though), it changed my IP and as a result my packet loss is now 0.1% and 0.0% respectively.

 

So yeah, friend was totally right, it was a stale IP that was affecting UDP in some way.

 

Anyway if anyone is having the same problems with verizon, then this is likely the problem. If verizon tries to send a break/lease command to your modem and it changes the IP, then it will probably fix it, otherwise your gonna have to swap modems like I did.

 

Amazing how something as little as that gave me 10% avg packet loss for like 3 months.

Edited by ronaldmcdonaldTW
  • 1 year later...
Posted

FYI, I have the same problem as you and burnt and I did get Verizon to reissue my IP to see if my issue was due to a stale IP. This did NOT fix the problem.

 

I would guess that your fix was likely the modem and not the stale IP. I will check into getting a new modem from Verizon to see if this fixes my problem too.

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...