Zugg Software :: View topic

Adept Joined: 24 Aug 2004 Posts: 277

I figured I'd post a separate topic for this one. It's been getting worse lately, but periodically cmud pro 2.18, will freeze random blocks of text on my screen.

It does it in all sorts of crazy stoner hippy patterns.

It doesn't do this with any other program, including Zmud.

Posted: Tue Apr 01, 2008 11:49 pm

Unfortunately, we'll need much more specific details of the problem. Screenshots, #debugfile logs (just the human-readable ones, the forums eat the raw ones), and a procedure to reproduce the bug, which'll probably involve connecting to your MUD would be helpful. At very least, we need to know exactly what's going wrong. At the moment, your report just says "sometimes it looks a bit funny", which isn't very helpful at all.

Adept Joined: 24 Aug 2004 Posts: 277

Sorry, I tried explaining best I could. I didn't know I could post a screenshot here.
Where do I get this #debugfile?

Remember, this only happens in cmud, not zmud.
I can't reproduce it, is the problem.

Also, when it happens, if the screen messes up like that, simply clicking on the parent window will refresh the screen to what it should look like, but the next time i get output, it messes up again. I've tried highlighting something and let it scroll, but that didn't help.

Where do I submit a screenshot, will it simply paste into the forum?

Posted: Wed Apr 02, 2008 10:20 am

Upload screenshots to somewhere like imageshack and then you can link to the image or use an [img] tag to display it.

Read the help file that I linked you to on #debugfile. I can't remember whether they're created in your install folder or your data folder - it'd probably be easiest to name them something interesting and then do a search. Once you've found them, just paste the human-readable one into a post inside [code] tags. This is probably the most important bit, because it's probably your MUD sending invalid VT100 codes that's messing it up.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

#DEBUGFILE creates the output files in your install folder (i.e., C:\Program Files\CMUD), by default, which can be a problem on Vista. Specifying the absolute path for each file should get you around that.

Adept Joined: 24 Aug 2004 Posts: 277

there's the image

Adept Joined: 24 Aug 2004 Posts: 277

I guess I should explain...

from the magic portal, i ran to an area(coincidentally, the same area that gives me the out exit problem). Then I ran back. part of the screen on the right hand side is gibbled.

I caught another screen image of a much larger affected area...

[img=http://img134.imageshack.us/img134/9489/cmud1on7.th.jpg]

also, some more code to accompany this one.

Posted: Wed Apr 02, 2008 4:52 pm

I don't see anything obvious in the dump, but I will try to replay it here to see what happens.

But one thing to check is to turn off the automatic Timestamps in the window to see if that fixes the problem, makes it worse, or makes it the same. Timestamps are relatively new, so maybe they are messing up the scrolling in some cases.

This kind of problem is very hard to debug since I have to get my screen set up exactly the same as yours (size, font, etc) and then I have to try and reproduce the exact text coming from the MUD, which takes a while, so it probably won't get fixed in the next version.

But I appreciate the detailed dump and screenshots...that should really help. I've been trying to find this bug for a long time, so hopefully this will do it.

Adept Joined: 24 Aug 2004 Posts: 277

hrm.. odd.. timestamps were disabled in the preferences(I turned them on on purpose cause I like them.) I turned them on, then turned them off, and they disappeared...

I'll let you know if this helps.

Also, anytime if you want to remote onto my pc, you're more than welcome... Anything to resolve these troubles I'd be happy to help.

Adept Joined: 24 Aug 2004 Posts: 277

And no, timestamps didn't affect my display.

I thought maybe for a minute that my pc was overheating, and causing this problem. But it's stone cold, been on maybe 3 minutes, cpu cooling pad under it... so that's not the problem.

It only started recently, and it's been getting worse, and worse. Cmud is almost unusable at point...

Adept Joined: 24 Aug 2004 Posts: 277

I don't know if this is relevant or not, but I turned ansi output off from the mud, and it still affected my screen graphics.

Adept Joined: 24 Aug 2004 Posts: 277

Update: I tried with triggers off, because I run a lot of #gag's ... didn't help

Posted: Thu Apr 03, 2008 5:16 pm

Wow, if it still did it with ANSI turned off, then this really is a weird problem. When you run the #DEBUGFILE command like this:

#DEBUGFILE test.raw text.txt

can you do this to show the bug, and then send me both of these test files as email attachments to sales@zuggsoft.com? Also include another screenshot if you can so that I can look at it in detail and try to get my screen set to exactly the same size and font settings as yours. But if it happens even with ANSI turned off, then I might have a good chance of reproducing it with those dump files.

Adept Joined: 24 Aug 2004 Posts: 277

I'll try as soon as I can replicate the problem.. It hasn't happened yet today..

Adept Joined: 24 Aug 2004 Posts: 277

3 files sent. If you don't get them, please let me know and I'll resend them, or post them here..

Posted: Fri Apr 04, 2008 3:46 am

Yep, got the files. I'll run then tomorrow and see if I can reproduce it. Thanks.

Posted: Fri Apr 04, 2008 5:21 am

I've ran into this problem myself before (and I reported it way back in 1.34 non-pro, too). I've found, however, that clearing the screen a couple of times then clicking on the mud output window seems to help quite a bit as far as stopping the split screen.

Another way I do is by using this character:

gt &#268~;

That will appear to clear the screen (it doesn't) but it appears to help the situation, too. Weird.

Charneus

Adept Joined: 24 Aug 2004 Posts: 277

Zugg, I should probably point out, that the debugfiles, I started after the problem happened.

From what I could tell, the debugfile had a limited space, and only captured a small amount, so I started and stopped it within seconds of it happening.

If you need me to gather it differently, to possibly capture the initial problem, I can try that. Unless I'm not understanding it fully...

After the problem started tho, it would just keep going until I clicked on the main window, and alot of times that would fix it, if not properly refresh the screen until the next lines come through, in which it would be a little garbled again.

*EVERY*!!! and I want to stress that! EVERY time I clicked on the main screen, no matter what, it would display the screen properly. I could have alien writing on the screen, and a single left click would fix it. Sometimes for awhile, sometimes until something new comes across my screen.