Zugg Software :: View topic

Newbie Joined: 02 Jan 2002 Posts: 2

I don't know if anyone else has encountered this problem...

Sometimes my screen freezes and it seems like lag, but the commands that i key in are executed on the mud in real time.

Anyone can help here?

I'm running win2k, and have 256mb RAM on a PIII 700, so I don't think it's a performance issue.

GURU Joined: 10 Oct 2000 Posts: 1116 Location: USA

You'll have to give us a bit more please. What version of zMUD are you running? Does it happen when you disable all triggers? Does it happen only at certain times? Are you using the #wait command anywhere? Are you using any #oninput triggers? Does it happen with just 1 mud or all the muds you try to connect to? Please give us a bit more info, thanks.

Iljhar

Newbie Joined: 02 Jan 2002 Posts: 2

The problem seems to occur in 5.56, 6.16 and 6.24.

It seems to happen when there's a lot of scrolling involved, say moving fast through lots of rooms. I'm not using the wait command, nor am i using #oninput triggers.

I can't be sure if its only this particular mud or not, because i don't mud elsewhere, but i have several different setting files and they all act the same way.

On the other hand, it could be lag - but lag wouldn't allow my commands to be executed in real time would it?

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

It sounds like you might be experiencing one-way transmission lag. That is, output from the MUD is getting delayed at some point and then sent on in large chunks, while input from you to the MUD is going straight through. This isn't all that unusual, since the input from you (a direction or action command) is probably 100-1000 times smaller than the output from the mud (a room description/fight round) and is therefore far less likely to overtax the bandwidth.

LightBulb

Wanderer Joined: 29 Sep 2001 Posts: 75 Location: Israel

The same thing happens to me. It is not uni-directional lag, because it freezes forever, and you have to relogin (which helps for a couple minutes). In addition, it happens on small and big ammounts of text, without any difference.

- Amfitrion.

Newbie Joined: 21 Mar 2006 Posts: 2 Location: Michigan

I realize the note is quite old but it describes exactly what is happening to me. Using windows xp, zmud 7.20b. Will be chugging along doing fine, but if severe netlag occurs I stop receiving output from the mud on my screen, but I am still able to send commands. Lightbulb mentioned it a likely being one way transmission lag and I understand that, but is there anything I can do about it instead of having to relog everytime it happens? Thanks for any input.

GURU Joined: 26 Jul 2001 Posts: 1958 Location: Canada

When you say commands you key does that mean commands you enter through the command line or are they from your triggers?

I have seen it where I'm getting huge chunks of mud output and it appears my triggers are still firing but in reality I'm sucking a 10 to 30s lag when I examine the log files and see the reality of the output.

Newbie Joined: 21 Mar 2006 Posts: 2 Location: Michigan

commands I key. basically I could continue playing, I am just not getting back anything from the mud. I can enter a lot of emotes and communications and when I relog, I can check my history and they are all there. my drivers are all up to date, the only thing I can think of is it must be some setting for the wireless card or a setting for something else I'm unaware of. All my other applications work fine, it's just zmud I'm having trouble with, possibly because it's telnet, but that is another guess.

Posted: Sun Mar 26, 2006 1:38 am

i've had times where this has happened to me and i'll spam the heck outta commands so that my groupie wont get killed cause of my inactivity.
All the commands happen as if they were input at the right times.
really weird, but i guess it would be attributed to the whole packet sending stuff.

GURU Joined: 26 Jul 2001 Posts: 1958 Location: Canada

#DEBUG texta.txt textb.txt

See if you can catch the spam out and see what the real in/out packets looked like.

I'd personnaly blame the mud engine and it dropping segments of output due to a time out. Many mud's have cheap drop code.