 |
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
 Posted: Wed Sep 26, 2007 1:57 pm
[2.03 and Pro] Automapper zone change crash
|
I've sent a bug report on this, but just to be sure it is on the list of things.
I'm getting a virtually complete crash whenever my mapper is open and it switches map zones. On rare instances, it seems to be able to (though the only when I've barely moved), but most of the time I am forced to close the mapper before moving then relocating myself after the move. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Sep 26, 2007 5:08 pm
|
Does it only crash when you move between zones, or does it also crash when you select another zone via the dropdown list at the top of the mapper? Do you have any way to determine if this happens with any map, or just a certain specific map?
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Wed Sep 26, 2007 5:24 pm
|
Also, what do you mean by "virtually complete"?
|
|
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Wed Sep 26, 2007 10:01 pm
|
It happens when there is an actual move into a new zone. You can select the list and change zones still. I have it happen with all my maps, for multiple muds.
By 'virtually complete' I mean that at least once after the crash I tried to continue without exiting. No new text was sent to my screen. Tried ESC and nothing changed, tried pressing direction movement buttons and nothing. However, after I exited out and came back onto the mud, my character had moved away from the room that the crash had been in like the commands (directions) I had sent with no screen response. So, in other words, it seemed that commands still could be sent, but there was no displayed response.
And after reading the Unconfirmed Lockup topic, this is almost exactly like what thinjon has happening. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Sep 26, 2007 10:16 pm
|
Another question: How are you moving to the new room on the MUD? Are you pressing a key on the keypad (which executes a macro), or are you entering the direction manually into the command line, or are you speedwalking?
Also, when this happens and it stops displaying output from the MUD, can you still type the #THREAD command to see if any other threads are running in the background? |
|
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Thu Sep 27, 2007 12:51 am
|
| Zugg wrote: |
| Another question: How are you moving to the new room on the MUD? Are you pressing a key on the keypad (which executes a macro), or are you entering the direction manually into the command line, or are you speedwalking? |
Hmm, interesting. May be something to do with the speedwalking to another zone. Using both the keypad and typed directions triggers it when moving to the zone. Normal speedwalking inside the zone works, but when you go to speedwalk to a room in another zone, the crash happens after the first room move. In all cases, it appears that the room is moved in the mud and the mapper, but only in the case of attempting to speedwalk to another zone does the mapper update before the crash. In the other two cases, the mapper is correctly positioned after I restart CMUD (in the new zone).
| Zugg wrote: |
| Also, when this happens and it stops displaying output from the MUD, can you still type the #THREAD command to see if any other threads are running in the background? |
Nope. I get no response from that either. |
|
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Thu Sep 27, 2007 1:17 am
|
Also, my mapper is configured to use ATCP messages from the MUD, as I only play IRE muds.
|
|
|
|
|
|
|
|
