Zugg Software :: View topic - [302B] Mapper forgets last location on map load.

Posted: Wed Dec 03, 2008 4:34 am

When the map is loaded it outputs to the session window the correct location. But the map itself is not positioned at that location. In fact, it is positioned at the same location that it was when it was first loaded (converted).

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

If I remember correctly, Zugg said that certain things won't save in this version because that isn't what he focused on.

Posted: Wed Dec 03, 2008 5:36 pm

Hmm, the map should be centering on whatever tracking location was last being used. The tracking locations *are* saved in your normal package file, so if it isn't remembering your locations then it sounds more like a bug.

Posted: Wed Dec 03, 2008 6:42 pm

Yeah. It doesn't save for me either. Not sure why, just thought it was something else...

Charneus

Posted: Wed Dec 03, 2008 7:02 pm

I'm curious to know if it's the Locations not saving, or something the mapper is doing. So here is a test:

1) Open your session offline and open your map.
2) Set the current tracking location (the blue dot) to a different room.
3) Type the #LOC command to see the room number of your location and make a note of it
4) Now, Close the map window (this is IMPORTANT).
5) Exit CMUD and restart CMUD and load your session offline again
6) Now type #LOC and see if the location was saved properly and has the same value you noted in (3)
7) Finally, click the Map button to open the map. Now type #LOC again and see if the location value changed.

Posted: Thu Dec 04, 2008 1:28 am

OK ran your test and here are the results:

(at open map was positioned to room 29930)

set location to room 37.

#LOC command outputs the following: * :Aardwolf at room 37 (blue) <AardwolfV3 Map>

Closed map window. Exited CMUD and restarted.

#LOC command outputs the following: * :Aardwolf at room 37 (blue) <AardwolfV3 Map>

Opened the map.

#LOC command outputs the following: * :Aardwolf at room 29930 (blue) <AardwolfV3 Map>

Which is the location displayed when I originally opened the map.

I can tell you why the map is at this location even though I wasn't at that location (I was at 215) when CMUD was closed last. That location is the last location I was when I modified the map. Same with the location that I was when I noticed the problem. That was also the last location I was when I modified the map. As I pointed out before, though, when the map loads it outputs the right location to the window even though the blue dot is elsewhere which means, to me, that the tracking was off (also it means that the map position and the tracking position are separate). However, after the tests it lost its (correct) position and settled for the displayed position. That is, the map position and the tracking position merged (at the wrong location).

Posted: Thu Dec 04, 2008 5:34 pm

Try opening the mapper and in the Action menu select the "Clear Start Room" option. Then try the above procedure again. If a Start Room is set in the map file, it will override the current location.

Posted: Fri Dec 05, 2008 3:56 am

Firstly, I did the following:

(My location at the close of the session was 215.)

#ECHO %roomvnum(): the output is 29930 (It still displays this location even though it ouptuts the correct location to the session window).

From the Actions menu I selected Clear Start Location.

Set location to room 37.

#LOC command outputs the following: * Aardwolf at room 37 (blue) <AardwolfV3 Map>

Closed map window. Exited CMUD and restarted.

#LOC command outputs the following: * Aardwolf at room 37 (blue) <AardwolfV3 Map>

(Note: even though the map window is closed, the location was sent to the session window and it matches what #LOC outputs. However, it doesn't see any exits from this room, which is wrong.)

Opened the map.

#LOC command outputs the following: * Aardwolf at room 29930 (blue) <AardwolfV3 Map>

Which, again, is the displayed location (each time the map opens) but not the current location.

EDIT: I now understand why the exit sent to the session window says Exits: none when, in fact, there are exits from that room. The reason is that
the information was stored in the package (the location) but the map database is not yet open so there is no information about the room.

Posted: Tue Dec 09, 2008 6:29 pm

OK, it definitely sounds like a bug when opening the map that is changing the current location.

If you want the map database to be open even if the mapper window is not displayed, then you need to go into your Settings, find the Map Object and make sure the AutoLoad option is set for it. That causes the map database to be loaded when the location objects are loaded from your session.

Posted: Thu Dec 11, 2008 9:09 pm

Found the problem. Should be fixed for the next version.

Newbie Joined: 18 Apr 2008 Posts: 2

Hmm...I'm having exactly the same problem with my Zmud 7.21 running under Vista.
When I close my mapper and restart it, it seems to forget which room I was last in. Regardless if I manually set a recal location or not. After restarting my mapper the roomvnum is set to -1 and the mapper centers around my very first mapped rooms.
I could isolate the problem to my newly mapped rooms though. It seems my mapper can't handle vnumbers around 45.000. My old rooms with numbers for example between 1 and 10.000 still work fine. I haven't exactly checked up to what point that still works but it seems that this is the problem.

Does anyone have a solution for this problem? It seems kind of sad that I will have this problem with every newly mapped room from now on :(

Posted: Mon Apr 13, 2009 5:17 pm

This forum is for CMUD questions, not zMUD. zMUD is not supported on Vista, so you are on your own dealing with that. We can only help with CMUD users on Vista.

Newbie Joined: 18 Apr 2008 Posts: 2

Uh, sorry. I didn't even notice that I changed the forum while looking for someone with the same problem.
I guess I'll post the same thing then again in the zmud-forum. O_o