Zugg Software :: View topic - Honestly can't explain it easily, blank space issue?

Apprentice Joined: 30 Oct 2004 Posts: 127

Every since I updated to 3.25, my system has still worked fine, but for some reason every time I do a QL or L to see the room, or I move to a new room, the name of the room is shown after about 4-5 blank lines.....

example:
<prompt>
<blank>
<blank>
<blank>
<blank>
Medina Street.
The stars twinkle in the clear night sky. A sewer grate looms darkly beneath your feet. There are 3 peacemaker of Enorians here. An argent intercessor is poised here, hefting an ancient-looking halberd in her glowing hands. A bright-eyed missionary serenely patrols the streets of Enorian.
You see exits leading north, southeast, and west.
<prompt>

I wouldn't mind this THAT much, but when I move and there's a lot of this going on, the blank lines almost seem to overlay the previous rooms so I lose bits and pieces of the buffer, unless I click on the buffer then it all seems to reset back, but still a load of blank lines.

I looked at the debug window, and the only thing I can think might be causing it, is the telnet lines being gagged, but I somehow doubt this seeing theres 3 telnet lines . Any ideas?

Wizard Joined: 26 Mar 2008 Posts: 1547

I'm wondering if it's buggy GMCP lines.

Posted: Thu Sep 09, 2010 4:53 pm

Post the output from the debug window (be sure to turn on the Raw Input/Output message in the debug window).

Wizard Joined: 17 Jun 2006 Posts: 1201

Firstly, this is Achaea we are talking about. Secondly, it is being caused by the mapper being opened. I was going to post about this but someone beat me to it I see. It only happens after you open the map. It continues even after you close the map until you restart Cmud. It is a serious problem because it not only splits paragraphs in half in the display but actually hides text. You have to actually click on the main window to make the text reappear but the blank lines remain.

For example, this is simply entering quick look (QL) or moving a room:

Apprentice Joined: 15 Jun 2010 Posts: 121

Hmm I've seen this once in a blue moon as well recently.. but I always assumed it was because of wacky gagging of the prompt, or some other weird script stuff I do where I #gag and then #echo in the same trigger since #sub never worked for me well

Apprentice Joined: 30 Oct 2004 Posts: 127

Ah good, someone else posted all that. This is the exact issue I'm having too, and yes my mapper is open, so I'll assume it is the same issue.

Posted: Thu Sep 09, 2010 9:07 pm

Please turn off all triggers (via the Options/Enable Triggers menu) and see if it still happens. You have several triggers firing on the text from the MUD that might be interfering with this. Then re-post the Script Debugger output with the triggers turned off if the problem still happens so I can see the clean results.

Wizard Joined: 17 Jun 2006 Posts: 1201

Display:

Wizard Joined: 17 Jun 2006 Posts: 1201

Display:

Posted: Thu Sep 09, 2010 9:59 pm

I'm not sure you captured the data that I needed. Your first "display" starts with a MUD prompt, but the "raw i/o" starts with the room name.

I converted the raw i/o to this test statement:

Wizard Joined: 17 Jun 2006 Posts: 1201

Display:

Wizard Joined: 17 Jun 2006 Posts: 1201

That should work right? Here you can see I galloped and you have the before and after.

Edit: By the way it does this even if I disable all triggers or even disable my package.

Posted: Thu Sep 09, 2010 10:28 pm

Can you try this test in your session (do it just after the problem happens on the MUD):

Wizard Joined: 17 Jun 2006 Posts: 1201

It happens differently (displays differently) but consistently in about every room when moving or doing look or quick look. I sent you a screenshot in a pm of my session screen. I'll get back to you on the test.

Posted: Thu Sep 09, 2010 11:21 pm

One more thing that might help me reproduce this...it's a bit of a pain, but at the beginning of your session (after you are logged in), type:

#DEBUGFILE test.txt test.raw

then do whatever on the MUD until the problem occurs. Then exit CMUD and email me the above two files as email attachments to sales@zuggsoft.com. Also paste the last page of MUD text into the email so I can see what your screen looked like.

This will allow me to replay the entire raw session as it was received from the MUD. That might allow me to reproduce it. I'll probably also need to know your setting for the number of lines in your scrollback so I can set my session the same. The window size might also matter.

Wizard Joined: 17 Jun 2006 Posts: 1201

Sent the email. I also included the session log file. It also shows the problem in the log file.

Posted: Fri Sep 10, 2010 4:28 pm

Got the files, but still having trouble getting it to happen here.

Could you try this: Run CMUD and close the Session window to get a blank window. Then type:

#READ test.txt raw

where "test.txt" is the debug file that you send me. It should dump the log to your screen. Tell me if your screen shows the extra blank lines or not. It's possible this is a bug that cannot be reproduced offline.

Posted: Fri Sep 10, 2010 5:25 pm

Also, I need to know if you turn off GMCP in your session, does the problem still occur?

Posted: Fri Sep 10, 2010 7:11 pm

OK, this one is really driving me crazy. I just wrote a new read routine that will parse the debugfile output and properly handle all packet boundaries and also simulate sending the commands to the MUD. The normal "#read raw" routine was just stuffing the entire raw data into a single network buffer. This new routine takes the human-readable debug file and handles the "in" and "out" lines and creates a network packet for each "in" line and a user command from each "out" line.

I opened the mapper and configured it. Then I ran this new read debug routine. It properly created rooms on the map in map mode and walked around the MUD.

But I never saw the problem with the extra blank lines. So I'm completely stumped on this. All I can think of is that you have some sort of room scripts that might be doing this. Turning off Triggers will not turn off any room scripts. Not sure how to really test that on your system. But the blank lines are appearing exactly where the GMCP data is being processed, which can move you to the room on the mapper and cause your room scripts to execute. So that's all I can think of that would be different between your session and mine.

Since you said this only happens when the mapper is open, that is all I can think of.

To test this, you would need to create a new session for your MUD with no scripts in it. Then create a new map for it and start moving around. Let me know if you can reproduce the problem in a completely new session.

Wizard Joined: 17 Jun 2006 Posts: 1201

Well the problem is I don't have any room scripts. The only script I had was a trigger firing on the room name and capturing the next line for the description. BUT even that trigger is only capturing like half the description when the problem occurs because it is being broken in half right where the GMCP data is, or at least that is what is showing in the Debug window. I don't have any room scripts running. Also this map was completely brand new. I had just made it. Additionally it only happens after the buffer fills up. I'm also not the only person having the issue.

I read the test.txt raw in an untitled and it didn't happen. It's not even exhibiting the same behavior that happens.

I'm going to make a test session and connect. Will get back to you on the results.

Posted: Fri Sep 10, 2010 8:43 pm

Hey, this is interesting. I starting playing Aardwolf today and I was able to get the problem to occur.

It only seems to happen when I speedwalk more than one step at a time. If I move manually then it doesn't happen. But if I start clicking on the map, then I see it.

Still not sure what's causing it, but at least I can see the problem here now.

Posted: Fri Sep 10, 2010 8:53 pm

What really sucks about this is that as soon as I set a breakpoint in my code to try and debug this, then the problem goes away! So this is going to be a real pain to track down without my debugger.

Wizard Joined: 17 Jun 2006 Posts: 1201

I can confirm it happens in a completely new test session with no triggers or script at all while I am creating a brand new map.

Wizard Joined: 17 Jun 2006 Posts: 1201

Ah nice you posted before my post went through. Laughing

Well at least you can see it happening now. It's something to do with having the map open for sure. I had this new one in mapping mode and on slow walk at the time. Was trying everything. I think last time it was in slow walk. However, it happens all the time to me once it starts happening it doesn't stop after that. Even if I do "look" as above or simply move a single room it does it.

Wizard Joined: 17 Jun 2006 Posts: 1201

Hmm look at this. Is this right?