Yeah I know you can't do anything with it. It was a straight fresh first-time install, no plugins or anything involved. No Python either, obviously. :-) My posting was intended to hopefully point out it isn't plugin-specific and help point out it isn't an old issue that has no relevance anymore.
Maybe someone else will see it, realize they have it, and stuff can pick up from there. Who knows. :)
I just connected to Firan under XP and the latest MUSHclient. Interaction seems instantaneous to me.
No information was given as to what, if anything, she had loaded (eg. plugins). There was a vague idea before that Python might be to blame. Who knows?
I accept that under some circumstances some people are having problems. With such little detail though it's impossible to go further. Next time:
Please provide a summary of your world configuration:
Either use the scripting Immediate window (Ctrl+I) to execute: Debug ("summary")
or
Install the Summary plugin (see
"Summary" feature) and type "summary"
Then copy the resulting information from the output window, and paste into a Forum message.
You need version 4.55 onwards of MUSHclient to do this.
Newest version, I pointed her to it. OS, I don't know. Game is Firan (firan.legendary.org). Again, I can't say I experienced it, but the fact people are getting this problem means it does exist in some really weird combination of circumstances.
This thing still exists. I was helping someone switch to MUSHclient, but because MUSHclient gave 4 second delays and other clients didn't, she gave up on it. (Same computer, same MUSH and login data...)
I don't blame her, and after suffering through it with me for two hours I can't ask her to go through a bugtesting session. :/ Regardless, I felt it was necessary to point out it still lurks somewhere, somehow.
I use Vista Home Premium myself and don't experience a delay... so I'm not sure it's specific to a single OS. I also have a G11 (pretty much a gamer's keyboard, just missing the LCD from the G14), though admittedly I don't really use its macro keys.
Amended on Thu 17 Dec 2009 07:50 PM (UTC) by Nick Gammon
Message
The other variables it would help to look at are:
Operating system - is there a common thread here? For example, is the "slow" version always running on Vista? (Or are you still using Windows 95 maybe?)
Operating system configuration. Occasionally I get complaints that MUSHclient shows text "right to left" in the command window. This turns out to be that they have activated right-to-left keyboard entry in Windows. The command window is just a Windows "Edit" control, and thus is subject to operating-system parameters like that.
Other operating system optional things, like "sticky keys".
Other known external software, such as "automated macro" recording. This may be slowing down processing of input as the keystokes are first recorded by this software.
A virus or trojan horse (keylogger). Try scanning for viruses. Maybe when you press <enter> the keylogger busily adds what you typed to a lengthy file on disk (or sends it over the Internet to the site which installed the Trojan).
Some other unusual configuration you haven't mentioned, such as running under Ubuntu, or on a Mac on Parallels, or via a network using pcAnywhere.
They keyboard is some non-standard keyboard, like a gamers keyboard with an LCD screen, or a wireless keyboard, and it is a long way away from the computer.
For what it's worth, you can fairly easily subtract network delay from your test by running 'ping <server>' in the console window, and subtracting that amount from the test results. It only makes sense to do that with the trigger version of the test, though.
I'm running Smaug so it's exactly the same match as yours. Even removing the preceeding * it doesn't print. Might be a colour code in there, I'll check.
Also, modified execute test: Time taken = 0.074 seconds.
I'm in Canada and my server is in Belgium so I do expect some delay and that's probably what I'm seeing in these results. As I said it doesn't particularly bother me anyway. :)
aka: Hana
Owner in Training of: Fury of the Gods
alm-dev.org:4000
A better test again might get rid of some of the decimal places, I think the last ones are a bit irrelevant. Try this:
tstart = GetInfo (232)
for i = 1, 20 do
Execute ("look")
Execute ("score")
end -- for
tend = GetInfo (232)
print (string.format ("Time taken = %1.3f seconds", tend - tstart))
Running that I got:
Time taken = 0.003 seconds
Effectively this truncates the results down to milliseconds, after that I think things become a bit problematic, because things like another program becoming active for a few microseconds are going to affect the results.
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.