Zugg Software :: View topic - Walking with double-click veeeery slow.

Wanderer Joined: 30 Nov 2006 Posts: 50

Hi,
I've noticed very big difference between speed of walking in v2 and v3. At this moment every time I got long speedwalk path cmud starts to send direction after direction (I always walk in fast mode) and it looks as it is waiting for some confirmation from mud. An example:
<double-click on map>
<cmud starts sending directions>
10:44:02:283 | nw 
10:44:02:611 | n 
10:44:02:924 | n 
10:44:03:262 | nw 
10:44:03:567 | w 
10:44:03:883 | nw 
10:44:04:223 | n 
10:44:04:526 | n 
10:44:04:841 | n 
10:44:05:178 | nw 
10:44:05:496 | n 
10:44:05:803 | nw 
10:44:06:080 | w 
10:44:06:345 | nw 
10:44:06:608 | n 
10:44:06:869 | nw 
10:44:07:137 | ne 
10:44:07:401 | n 
10:44:07:661 | nw 
10:44:07:926 | n 
10:44:08:190 | nw 
10:44:08:450 | w 
10:44:08:710 | nw 
10:44:08:979 | w 
10:44:09:249 | w 
10:44:09:513 | nw 
10:44:09:772 | sw 
10:44:10:018 | w 
10:44:10:278 | w 
10:44:10:517 | w 
10:44:10:755 | w 
10:44:11:002 | s 
10:44:11:259 | s 
10:44:11:514 | s 
10:44:11:770 | most 
10:44:12:028 | s 
10:44:12:292 | s 
10:44:12:545 | se 
10:44:12:800 | sw 
10:44:13:055 | s 
10:44:13:308 | s 
10:44:13:560 | s 
10:44:13:812 | d 
10:44:14:118 | n 
10:44:14:390 | w 
<After 12 seconds since first direction was sent my character starts to move>
10:44:14:688 | Ruszasz niespiesznie na zachod. 
Any suggestions how to start run path without this delay?

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

If it's waiting for confirmation, you are not in fast mode. CMud doesn't care whether you run into walls or otherwise fail to move when you are in fast mode--you just start the move, CMud immediately moves the location dot, and then you get superspammed with the game output. Because the GMCP functionality was recently included, you are most likely in SAFE mode--which sort of combines the frontloading and speed of fast mode with the careful confirmation of slow mode.

Wanderer Joined: 30 Nov 2006 Posts: 50

I do walk in fast mode - at last this is option I've chosen, that's why I'm asking why mapper behaving this way. I don't know what is GMCP for so I got it disabled.

Posted: Sat Nov 13, 2010 5:36 pm

Maybe something is corrupted in your map. The Fast/Safe/Slow mode is tied to the specific Location object that is active in your session. So maybe the location object is screwed up somehow. You should use the #LOC command on the command line to see what location is active, then make sure this is the location shown in the lower-left corner of the mapper as the tracking location. Then you can try switching to Slow mode and then back to Fast mode to see if it makes any difference.

You might also try turning off your triggers in the Option/Enable Triggers menu to make sure it's not some script running in the background.

I can use fast walk instantly on both of the MUDs that I have tried here without any problem at all. So it's definitely something specific to your settings or session.

Wanderer Joined: 30 Nov 2006 Posts: 50

#loc
#print Walk mode is %walkmode()
> Locations (* is current, - is disabled):
* eidur at room 7982 (blue) <arkadia Map>
Walk mode is 0 also all triggers are disabled and still there is no difference in speed -
11 directions first was sent at 05:28:52:499
second at 05:29:17:512 (25 seconds later)
last one at 05:29:18:278

Posted: Sun Nov 14, 2010 10:11 pm

Try running your map through the map conversion tool and back... that -may- fix a map corruption, and is a lot quicker than trying to remake the map.

Wanderer Joined: 03 May 2005 Posts: 72

My speed walk seems to be getting the same error here. This is a fresh map created with the new database, but I'll recheck my settings. currently even a 25 - 30 room walk takes about 30 seconds to speedwalk.

edit> when i close cmud and reopen it seems to work much much faster

Wanderer Joined: 03 May 2005 Posts: 72

ok I figured it out. Seems if you have the map zoomed out while double clicking it moves much slower than normal. Try zooming in on the map till you have about 15 rooms or so then using the #walk command and it works much quicker

Posted: Tue Nov 16, 2010 6:13 pm

In your Map Properties in the Speedwalking tab, check the "Center map after every movement" and "update map on each step" options. I have those both turned off here and turning them on might cause CMUD to try and repaint the map for each step which can be slower when you are zoomed out and there are a lot of rooms to draw.

Wanderer Joined: 03 May 2005 Posts: 72

Worked I think your correct in the mapper was trying to redraw the location

Wanderer Joined: 30 Nov 2006 Posts: 50

I have both options turned off so reason must be somewhere else. I've noticed another thing - maybe that could be a clue. I double-clicked destination and start to walk toward it with SendDelay set on 3500 ms - as I was walking I switch to window with documentation and after switching back to main window cmud send full path in one single command - 5n2hw2hw2h2j

Newbie Joined: 17 Dec 2010 Posts: 4

I have the same problem. Tried switching to slow walk (and back), tried unchecking "center map after every movement" and "update map on each step". Maybe in upgrading from 2.37 to 3.33 something got missed?

edit:

Okay, this might shed some light. In the Window menu option, I see my mapper listed 5 times. If I choose one of them and close it, it is still listed. Is my mapper permanently open five times?

Beginner Joined: 18 Dec 2010 Posts: 17

Same thing in 3.33a .The problem is not lag in sending. It looks like a lag while preparing the path, sending is instant as soon as it is done. Loading 40 steps is around 2-3 seconds.

Newbie Joined: 17 Dec 2010 Posts: 4

I manually hacked my .xly file to get rid of the extra lines. Only one mapper open now, and speedwalk is back to its speedy self.

Beginner Joined: 18 Dec 2010 Posts: 17

Ok, OP, I have temporary solution. Set the senddelay (#call %pref(senddelay, x)) to anything over 0. Will send the commands immediatelly.