Key lag & ping times while 5-boxing

[Iru]

I can't tell wither it's pwnboxer, Jamba, or Just The Way Things Are with the following so I thought I'd ask.

Using an FTL config under pwnboxer with Jamba automagically generating the /target & /assist buttons, I find myself having to hit the /assist key multiple times on my current leader before all the slaves will recognise the new target. There's usually only one toon who misses but occasionally I can have a couple of toons go running off or at least not pick up the target.

Is there any difference in the latency between key press and key send to different games under pwnboxer? If not, I may try crafting a manual /assist FTL macro outside Jamba to see if it's getting in the way somehow instead.

On a related note, I am getting some significant differences in ping times between toons, including having specific toons DC. What kind of ping differences to people generally see between the different toons when 5-boxing?

[TheMuffinMan]

I have the same problem with having to occasionally hit my /assist button more than once to get all my toons to assist properly, and I use Jamba as well (but NOT for any macros, I make my own), but to my knowledge this is just something weird with WoW and macros or something... if someone has any other info that would be awesome.

As far as ping, on my 5 toons it is almost always the same and I have never had any issues with toons DCing

[Tim]

A thing to remember is when WoW reports latency, that is *NOT* network ping times.

Just ping google.com -t to see your real network latency.

[ebony]

Originally Posted by Tim

A thing to remember is when WoW reports latency, that is *NOT* network ping times.

Just ping google.com -t to see your real network latency.

his right its the ping it takes to go to blizzard "bad" servers and back to your pc there is a mod somewhere that changes your network settings to make the ping drop a good 90%

[Iru]

I am well aware of the difference between "WoW ping" and "real ping". My point was rather that I have wild variation between the 5 clients while all are playing simultaneously, e.g. game one reports 183ms response time, game 4 reports 450ms response time, and I'm wondering why.

EDIT: and the mod you're talking about is adjusting the TcpAck value in the registry, a fix that's not been necessary since 3.1 according to Google.

[Ualaa]

I believe it is because of the wow server.

For example, you are targeting mob A.
And then switch to mob B.

When your slaves have the macro:
/cast [at main's target] Nastiness

It takes a moment, for the server to let them know that the target has changed.

If you were to slow down your play, target something, wait a second or two, and then nuke... the slaves would almost always be with you.
Sometimes Wintergrasp latency, can make this worse then others.

On quick switches of targets, and immediate dps, you'll have wrong targets quite frequently, whether you press an /assist Me macro, or just spam the nuke with [target=FocusTarget] or whatever.

[Lindline]

Originally Posted by Iru

EDIT: and the mod you're talking about is adjusting the TcpAck value in the registry, a fix that's not been necessary since 3.1 according to Google.

It still improves performance. I dont know what they fixed in 3.1, but I couldnt stream and play without crippling pingtimes in the thousands. The TCPAckFrequency adjustment fixed that.

[Iru]

Well while setting TcpAckFrequency=1 has certainly lowered my in-game ping tie measures, it hasn't fixed my underlying problem of random DCs.

If anything it's made them worse as now ALL my toons DC instead of just one or two. Guess I'll try fiddling with automatic RWIN adjustment & see if that helps. Maybe its messing with my DSL Modem & Firewall

[Lindline]

Pick up a program called PingPlotter(standard trial will work the best). And have it run a continual ping of a routetrace to whichever battlegroup youre on. Now, let that run for 24 hours in the background. When thats done, check out any points where the is significant packetloss on any of the graphs.

Trying to locate/eliminate a network issue. Which actually sounds like is going on. Random disconnects have nothing to do with PwnBoxer and are likely an issue with either the WoW install or your connection itself.