Lag issue on SSCE Hyperspace

[dartvader6]

The anti lag on hyperspace is crazy

 

It pics me out and i dossent lag

[Hakaku]

What does your ?lag say? Are you on wireless? Can you post a Trace of the zone (via the menu)?

[»Lynx]

Probably the fluctuate mod they have now, I can't play there either.

 

-L

[CRe]

Probably the fluctuate mod they have now, I can't play there either.

 

-L

 

Yeh, Arnk's nazi lag module.

[dartvader6]

one thing to say GET RID OF THE MOD and FIX THE ANTI LAG SCRIPT

[Gannon8]

one thing to say GET RID OF THE MOD and FIX THE ANTI LAG SCRIPT

+1

 

Can't really think of anything else to say since that says it pretty darn well.

[dartvader6]

Thanks sorry for the thing before this was quite angry on the server (tryed to play)

 

One thing evrybody that likes SS say YAY

Edited April 25, 2009 by dartvader6

[Samapico]

I'll move this to the hyperspace forum, we'll see if they have anything to add. And you can close it when you want

[Cheese]

if theres 2 things you can not do in HyperSpec, its alt tab or play with TOO MUCH FLUX OMGGGGGGGGGGGGGGG O NOEZ

[Kilo]

Nothing needs to be fixed/removed, insofar as this lag module actually detects laggers in an effective manner unlike subgame or asss standard. As you can see, even cheaters like cremey are butthurt over it.

 

If you are running other programs or are on a heavily shared connection it is probably going to detect the negative impact that has on you. If you could post a ?lag -a it would be helpful so I could point out things to try, or if we met in game I could run some additional commands on you to make sure it's being reasonable.

Edited April 25, 2009 by Kilo

[CRe]

Shutting off my firewall does the trick.

[dartvader6]

1.Thanks 2.Not that smart Edited April 25, 2009 by dartvader6

[Kilo]

Lol, what firewall causes you to lag that much?

 

For ?lag -a: Enter the zone. Wait about 2 minutes so it can gather data. Then type ?lag -a, and copy/paste the results here.

Edited April 25, 2009 by Kilo

[»Lynx]

@Kilo:

 

(around a minute or so of playing)

You have been specced for excessive average ping fluctuation: 39 ms breaks the limit of 30

 

session: 0:03:08

lag: ping: s2c: 0 (90-110) c2s: 60 (30-240) rel: 49 (44-110) loss: s2c: 0.15 (0.35) c2s: 0.00 (0.00) wpn: 0.00 (0.00) etc: flux: 6,9 (6,9) drift: 2 (2)

 

(A little after)

 

lag: ping: s2c: 0 (90-110) c2s: 53 (30-179) loss: s2c: -0.07 (0.15) c2s: 0.00 (0.00) etc: flux: 0,0 (0,0)

 

session: 0:06:07

lag: ping: s2c: 102 (90-240) c2s: 51 (30-215) rel: 51 (44-55) loss: s2c: -0.02 (4.30) c2s: 0.00 (0.00) wpn: 0.00 (0.00) etc: flux: 0,0 (0,0) drift: 0 (0)

 

----

 

Completely fresh install of Windows XP SP3 (Fully patched), no other applications running (this includes background processes). I'm on a Core 2 Duo T8300 @ 2.40GHz with 4GB RAM, 512MB NVIDIA GeForce and n wireless card.

 

ISP: Virgin Media (20MBPS <1KM from Exchange)

 

I can't play for anything longer than two or three minutes without getting specced.

 

So, what ideas do you have?

 

 

Also, on your whole theory about butthurt cheaters... I'm sure that the new lag module 'detects laggers in a more effective manor' however, mind explaining your philosophy on laggers? As far as I can tell, this lag module is removing lag far too harshly - shouldn't one focus on only removing the excessive laggers (as the SG/ASSS standard lag detection does), and if anything to check for short-term laggers wouldn't one just make lagchecking the option? Then again, that's just my opinion.

 

-Lynx

[Kilo]

I was calling cre a cheater for fun, but it so happens that in HZ which has been using this module a bit longer, a lot of negative qualities it is picky about magically disappeared from certain notorious laggers once they were being enforced, and those players are not notorious laggers anymore. In most cases where people were having trouble, they were running extra programs in the background or had other users on their network doing high-bandwidth things, usually manifesting as ping fluctuation.

 

Ping fluctuation is a measure of how spiky you are. Some of the seemingly laggiest players can have decent ping times, the pattern that was discovered is that these players bounce around erratically (instead of getting packets at a regular interval, the interval osscilates like a sine wave.) This is usually a lot more disruptive than a high ping alone, which is why it's included in calculation.

 

The module operates on a philosophy of if you are playing outside the limits, you are removed, and if you are outside of the limits, you cannot join the game. This is the same for lagaction and subgame, though each checks for these things in slightly different ways I'm sure. If you are able to enter the game, play for a few minutes, then are specced and locked for several moments, then you simply have an erratic connection. Which is shown in your ping times going up to the low to mid 200s, and your high s2c loss being 4.30.

 

Run a trace to the server and if you know enough about that, you can identify at least if it's something your ISP is doing, something wrong with your own hardware setup (people have had problems due to a bad router that needed to be replaced, for example), or something on another hop along the way.

Edited April 25, 2009 by Kilo

[Samapico]

The limit of 30ms fluctuation seems a bit overkill to me as well.

 

If someone has a ping changing from 10 to 50 ms he will be specced?

[Kilo]

No, if your ping is between 0 and about 100ms, your fluctuation is recorded as 0. 30ms fluctuation means +/- 30ms average, which would mean at least 100-160. But in practice the actual range is always higher because of the sine wave effect I talked about. The module whisks people away pretty quickly when they start hopping about, but if you had a consistent reading of 30ms and it kept you in the game it would be pretty ridiculous. If you have anything over 5 the effects are generally noticeable (most people have 0.) Edited April 25, 2009 by Kilo

[Samapico]

I see

[»Lynx]

Tracing Zone: SSCE Hyperspace  IP Address: 208.122.59.226

Hop IP Address	  Host Name						Loss(%) Min/Avg/Max Ping
--- --------------- -------------------------------- ------- ----------------
 1 192.168.2.1	 <unknown>						   0.0	  0	0   20
 2 10.95.128.1	 <unknown>						  98.7	 20   20   20
 3 62.31.32.199	<unknown>						   1.2	  0   10   70
 4 195.182.178.137 bre-bb-a-ge-210-0.network.virgin	0.0	  0   10   30
 5 213.105.174.226 bre-bb-b-ae0-0.network.virginmed	1.2	  0   30  300
 6 62.253.185.74   telc-ic-1-as0-0.network.virginme	1.2	  0   20  300
 7 213.248.100.97  ldn-b2-link.telia.net			   0.0	  0   20  280
 8 [img=http://www.ssforum.net/public/style_emoticons/default/mega_shok.gif].91.252.13	ldn-bb2-link.telia.net			  0.0	 10   20  280
 9 [img=http://www.ssforum.net/public/style_emoticons/default/mega_shok.gif].91.248.254   nyk-bb2-link.telia.net			  0.0	 [img=http://www.ssforum.net/public/style_emoticons/default/mega_shok.gif]   90  300
10 [img=http://www.ssforum.net/public/style_emoticons/default/mega_shok.gif].91.248.158   nyk-b5-link.telia.net			   0.0	 [img=http://www.ssforum.net/public/style_emoticons/default/mega_shok.gif]   90  300
11 213.248.95.46   0.te6-2.tsr1.lga3.us.voxel.net	  0.0	 [img=http://www.ssforum.net/public/style_emoticons/default/mega_shok.gif]   90  220
12 208.122.5.230   0.te1-49.dsr1.lga6.us.voxel.net	 0.0	 [img=http://www.ssforum.net/public/style_emoticons/default/mega_shok.gif]   90  110
13 208.122.44.54   v17.esr3.c3.lga6.us.voxel.net	   0.0	 [img=http://www.ssforum.net/public/style_emoticons/default/mega_shok.gif]   90  190
14 208.122.59.218  <unknown>						   0.0	 90  100  210
15 208.122.59.226  zone.rshl.org					   2.4	 [img=http://www.ssforum.net/public/style_emoticons/default/mega_shok.gif]   90  170

Cycles: 83

 

Probably the second hop there - unfortunately nothing I can do about that.

 

-L

[Kilo]

If by second you mean #3 then I agree, but it's probably worth complaining to your ISP about.

[Dr Brain]

yeah, #3 is where you're getting the large ping variation from.

 

I don't know what's up with the loss column for #2. I'd speculate that the server has some sort of filtering to ensure that it can't get pinged repeatedly.

[Samapico]

If by second you mean #3 then I agree, but it's probably worth complaining to your ISP about.

And #5

[Emit]

stop dling pr0n obv~

[Kilo]

If by second you mean #3 then I agree, but it's probably worth complaining to your ISP about.

And #5

...no, just #3