Zugg Software :: View topic

Newbie Joined: 18 Feb 2009 Posts: 3

I recently upgraded from zMud to cMud, and for the most part I love it. One thing that's killing me, though, is that every time I enter a command that's 3 characters or longer, there's anywhere from a half-second to a full-second delay before it executes the command. During this delay, cMud does not display any text it receives from the mud and it seems pretty much locked up. I've had to make a whole bunch of 2-character aliases for certain commands that I repeat a lot to try to avoid this delay.

I'm running the Windows 7 Beta as my operating system, so I admit that it could have something to do with that. The mud is SWMud, but since the delay occurs before the command is echoed to my display, it seems unlikely that it has anything to do with the mud connection. I've tried running with the Debugger Window open, and nothing appears in there until after the delay has occurred.

Since this doesn't happen on commands of 1 or 2 characters, I suspect that it has something to do with the command line history. I reduced the number of commands to save in history to 10, which didn't have any effect. I've experimented with pretty much all of the options on the Command Line page of the Preferences window, but haven't found any way around this.

Any ideas on other settings or workarounds to eliminate this delay?

Posted: Wed Feb 18, 2009 5:38 am

What version of CMUD are you running? Do you have any on input triggers? Do you have a lot of aliases? Do you mean zScript commands or commands you send to the mud? Is it all commands or just a particular set of commands?

Do you see this behavior in an untitled session?

Posted: Wed Feb 18, 2009 1:31 pm

I would guess that this is a result of whatever display component CMUD is using for the command line not being optimised for Windows 7 yet. CMUD probably won't be supported fully on Windows 7 at least until it's released.

Posted: Wed Feb 18, 2009 6:10 pm

I can't imagine that this is caused by Windows 7. It sounds more like a command history problem as cthrek mentioned since only lines longer than 2 characters are stored in the history. But setting the history size should have solved that.

If you converted your settings file from zMUD, my guess is that there is something in the conversion that caused the problem. Try creating a fresh, blank session for your MUD and see if you still have the same problem. If it works in another session or on another MUD, then the problem is related to something in your scripts.

Officially, Fang is correct that I cannot support Windows 7 until it is released to the public (I don't have any special access to Microsoft beta, nor do I have time/patience to mess around with Microsoft betas). However, from what I know about Windows 7 already, this really doesn't sound like something the OS would cause.

Posted: Wed Feb 18, 2009 7:50 pm

Windows 7 isn't all that different from Windows Vista except for a few minor changes, really, and most of those are on usability. I use it and don't have the problem described at all. My only complaint is the lag when executing scripts and not being able to input anything until afterwards. Oh well. :p

Charneus

Newbie Joined: 18 Feb 2009 Posts: 3

I'm using cMud version 2.37. I do have a few triggers and a large collection of aliases in zScript converted from zMud, however the delay occurs whether it's an aliased command or not as long as its three characters or more (even just three spaces) and I don't see any triggers being hit in the Debugger Window. Tried a fresh session for my mud and it still occurred.

I did have issues with a couple of my driver installations, and Windows is not performing as well on my machine as I would like it to. But everything else in cMud is working just fine, and 1 and 2 character commands perform great, so I guess I was hoping that there might be a setting I was overlooking in the preferences that might turn off whatever my computer's doing during that delay. Even setting the command history size down to 0 doesn't seem to help, though.

Posted: Thu Feb 19, 2009 4:56 pm

Newbie Joined: 18 Feb 2009 Posts: 3

Problem is fixed, had nothing whatsoever to do with cMud. Instead, was a BIOS issue on my computer... flashing to the latest BIOS fixed a number of problems on my computer, including this one. Now, cMud is performing wonderfully. Sorry for having posted this here, trying to treat a symptom rather than the cause.