 |
QueenB
Newbie
Joined: 29 May 2004
Posts: 4
Location: USA
|
 Posted: Sat May 29, 2004 3:57 am
Problem with slow walking
|
I'm having trouble with slow walking, using both the map and paths. The commands to move are being entered too quickly, and Achaea/Imperian will cancel the movement. I've tried to change a number of options in the Preferences, but to no avail. I appreciate any help with this.
Thanks!
- B. |
|
|
|
|
nexela
Wizard
Joined: 15 Jan 2002
Posts: 1644
Location: USA
|
Posted: Sat May 29, 2004 6:08 am
|
I think alot of these have been answered here Search the forums and see if anything that comes up might be able to help you. If you still can't figure it out post here again :P
|
|
|
|
|
QueenB
Newbie
Joined: 29 May 2004
Posts: 4
Location: USA
|
Posted: Sat May 29, 2004 7:11 pm
|
quote:
Originally posted by nexela
I think alot of these have been answered here Search the forums and see if anything that comes up might be able to help you. If you still can't figure it out post here again :P
I did search the forums before I posted. I used every suggestion for fixing the problem I could find, but nothing has worked thusfar. 
Thanks for any assistance!
- B. |
|
|
|
|
Insomniac
Wanderer
Joined: 25 Mar 2004
Posts: 78
Location: United Kingdom
|
Posted: Sat May 29, 2004 7:38 pm
|
I'd recommend increasing the number in the step delay box on your mapper properties.
The value is in milliseconds, so 1000 = 1 second. |
|
|
|
|
QueenB
Newbie
Joined: 29 May 2004
Posts: 4
Location: USA
|
Posted: Sun May 30, 2004 3:20 am
|
I increased the step delay to 3000, which works nicely, however, I have a new problem now. The slow walker is skipping steps. Any idea on how to fix this?
Many thanks,
- B. |
|
|
|
|
sirscribe
Newbie
Joined: 05 Jun 2004
Posts: 4
Location: USA
|
Posted: Sat Jun 05, 2004 10:24 pm
|
If it helps, for Achaea I use the following, which seldom gives me problems:
In Slow Walking dialog, UNcheck 'Timeout aborts Walk', Timeout Value=850, and no 'Strings'.
Of course the downside to this is it is no longer checking for successful movement, which could be bad if you hit lag. You could always increase the Timeout Value to 1000 if you wanted to play it safe, and might also create a 'lag trigger' in the form of #TRIGGER {%t$%t$%t} {#pause} which will check to see if direction commands start stacking up on one another, and pause your slow walk if so. You can then restart it by typing #step.
Hope that helps? Maybe someone else has an easier way to go about it? |
|
|
|
|
|
|
|
