Zugg Software :: View topic

Posted: Thu Jan 25, 2007 1:50 am

In the image below, you'll see a messed up screen... Don't know what is causing this - CMUD will run fine for a while, but it'll occasionally break into split screens. I've tried to reinstall CMUD, checked my graphics, and haven't come up with a reason. Anyone have any suggestions as to what's causing this?

Charneus

EDIT: Thanks, Guinn, for your suggestion of imageshack. :)

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

can't view that pic, angelfire doesn't like linking.
try using www.imageshack.us

Posted: Thu Jan 25, 2007 2:19 am

Open a new browser and paste the link. That works.

And that is bizarre. I've never seen that before.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Also no clue at all, never seen anything like it either. Would have to cede to Zugg for the answer if it's not graphics card/driver related.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

If you can find any way to consistently get it to happen, then it would be useful if you used the #DEBUG command to make sure there aren't bad VT100 codes causing it. The syntax is #DEBUG test.txt trace.txt. One of the files contains some formatted data that will let us check the control codes. While it doesn't seem likely that this is the cause it is possible.

Another possibility is a memory corruption issue that would be quite difficult to track or replicate.

Newbie Joined: 23 Jan 2007 Posts: 7

My screen gets split like that regularly.

I find just clicking around the text/higlighting some of it and clicking about fixes it within a second, maybe two.

Is yours more severe?

Posted: Thu Jan 25, 2007 7:51 pm

Vijilante is correct about doing the #debug to check for bad VT100 codes from the MUD. Also, you should definitely make sure you have the latest driver for your graphics card.

I'd also be interested in knowing if this happens in zMUD as well as CMUD, or if the problem is unique to CMUD.

You should also both post which MUD you are playing to see if it's a MUD-specific issue.

Clicking on the MUD output screen causes CMUD/zMUD to perform a full screen refresh, so that should always fix this kind of problem. The "split screen" is caused by the CMUD/zMUD screen scrolling optimization where it only scrolls the amount of text that is really necessary. If the MUD sends back VT100 scrolling region controls, then that can mess up the scrolling optimization. Since CMUD and zMUD use the same screen output routines, I'd expect the same problem to occur in both clients, but I haven't seen any reports like this for zMUD in many years, so it's possible that CMUD is doing something new somehow.

Posted: Thu Jan 25, 2007 8:09 pm

I vaguely remember this kind of "tearing" happening in zMUD a couple of times with single lines, but clicking on the screen refreshed it and it went away, so it didn't really bother me.

Posted: Fri Jan 26, 2007 9:49 pm

Playing Aardwolf. My graphics card does have the latest driver. It's never happened to me in zMUD, and tried the #debug test.txt trace.txt suggestion, but for some reason, it produced nothing. Unless I'm missing something - I couldn't find the files. But the clicking on the MUD output screen seems to be working - although I could swear I was doing that before and it didn't work. Oh well. Thanks!

Charneus

Posted: Fri Jan 26, 2007 10:21 pm

After typing

#DEBUG test.txt test.raw

and then issuing the command on the MUD to display the text. After it shows the tearing problem, type

#DEBUG

to close the files, then exit CMUD. The test.txt and test.raw files should have been created in your CMUD directory. Works fine here.

Posted: Sat Jan 27, 2007 1:37 am

Okay. Here's the report from the #DEBUG files. It's this last part that caused the tearing in the screen, but if you need the whole thing, I can upload it to a site for you.

Posted: Sun Feb 04, 2007 1:55 am

Just an FYI for Zugg, this does occasionally happens to me in zMUD. It seems to be pretty spontaneous, and as previously suggested, a screen click always fixes it.

Posted: Mon Feb 05, 2007 8:21 pm

I can't do anything with the files pasted into the forums. I need the actual files themselves. You need to either email them as attachments to support@zuggsoft.com, or post them somewhere and email the links to me.

Odoth: as mentioned earlier in the thread, the problem is most likely caused by the MUD sending improper VT100 scrolling region codes (or other bad control codes). The problem in CMUD seems to be different and more common. If the debug files allow me to reproduce the problem, then I might be able to tell you more.

Apprentice Joined: 11 Oct 2007 Posts: 154

the clicking in the screen to refresh the display..... I know when it does this to me.

This has Always happened to me when I use the #sub in conjunction with <send> tag (even in Cmud beta 3.06):

Apprentice Joined: 11 Oct 2007 Posts: 154

I went into session settings, Emulation preferences and turned off the VT102 option and it has not bothered me since! YAY! Thanks Zugg, pretty sure I read that in another post or something.

EDIT: I posted too soon, it still does it, but it does it like every 3rd time the #sub <send> is sent....... instead of every single time.

Posted: Thu Apr 30, 2009 4:45 pm

xekon: Please do not re-open old posts list this and please do not post the same problem to multiple threads. I have answered your issue in the other thread and have asked for additional information there.