24 - Disappearing Waypoints.

What steps will reproduce the problem?
1.@ Rut'theran Villiage
2. /tway Darnassus 47.97 14.16 TheHowlingOak3
3. /tway Darnassus 46.04 34.73 TheHowlingOak2
4. /tway Darnassus 41.88 48.25 TheHowlingOak1
5. then go through the portal to Darnassus.
6. The last two waypoints disappear.  Happens on about 1:3 of the logins.

What is the expected output? What do you see instead?
I expected to see 3 waypoints.  Instead I saw one.  When I reached the waypoint, it removed itself, but the other three were still active, but invisible.

What version of the product are you using?

Do you have an error log of what happened?

Please provide any additional information below.
Originally from

User When Change
LudovicusMaior May 11, 2011 at 17:04 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of LudovicusMaior LudovicusMaior Jun 02, 2011 at 00:08 UTC - 0 likes

    In this ticket, on Sun, 15 May 2011 05:20:42, you wrote:

    FWIW, you can just UNcomment out this bit in Astrolabe:GetUnitPosition()

    Last edited Jun 02, 2011 by LudovicusMaior
  • Avatar of Cladhaire Cladhaire Jun 01, 2011 at 21:35 UTC - 0 likes

    I forget what the Astrolabe change was, honestly... there was so much going on and there wasn't a specific ticket for it. Hrm.

  • Avatar of LudovicusMaior LudovicusMaior Jun 01, 2011 at 20:52 UTC - 0 likes

    Release 1.4.0 has addressed my issues.

    I note that you did not include the Astrolabe change.

    However, Now that WoWPro quiesces  between PLAYER_LEAVING_WORLD and PLAYER_ENTERING_WORLD and defers setting waypoints until the initial PLAYER_ENTERING_WORLD, it looks like that change was not needed.

    The " waypointMap[uid] = nil" was the key.


  • Avatar of LudovicusMaior LudovicusMaior May 24, 2011 at 14:12 UTC - 0 likes

    Grand! Thanks.

  • Avatar of Cladhaire Cladhaire May 24, 2011 at 09:33 UTC - 0 likes

    I can do it before then, but I'd like to have as much cleared up before then. I'll see what tickets I can knock out tonight.

  • Avatar of LudovicusMaior LudovicusMaior May 23, 2011 at 23:51 UTC - 0 likes


    When were you planning on making another release of TomTom?

    I'm cutting the next WoWPro release on June 1 and it would be nifty if I could claim the Worgen starter zone problems were fixed by upgrading both addons to the latest versions.

    Otherwise, I might have to do see what I could to patch TomTom:ClearWaypoint(uid) for the existing release, but that would be a nasty thing.

    Last edited May 23, 2011 by LudovicusMaior
  • Avatar of LudovicusMaior LudovicusMaior May 20, 2011 at 22:14 UTC - 0 likes

    Well, it plays like a fix.

    I took a worgen from Level 1 all the way to Darnassus.

    Not one mapping glitch and the arrow worked like a champ.

    So I think the combination of the TomTom:ClearWaypoint() change and the tweak to Astrolabe:GetUnitPosition() fixed the TomTom issues.

    It also took changes in WoWPro not to try to set waypoints when the mapping system might be wonky.

    PS:   I think it also raised my FPS rates.  I was quite happy with 60 before, but now I seem to peak at 90+.  No config changes made.

    Last edited May 20, 2011 by LudovicusMaior
  • Avatar of Cladhaire Cladhaire May 20, 2011 at 10:36 UTC - 0 likes

    Just wanted to make sure =)

  • Avatar of LudovicusMaior LudovicusMaior May 20, 2011 at 09:01 UTC - 0 likes

    I am not calling this function directly, but it does get called on my behalf when I use TomTom:RemoveWaypoint().   I put in monitoring code at the TomTom and astrolabe levels and noticed that when the error occurs, that waypoints[m] had the right entries, but waypointMap had dozens of entries with different keys with the same point object and that astroabe.MinimapIcons had only one entry.

    So I will only claim this fixes a problem with unknown symptoms.  I was actually suspecting the point cache had gotten corrupted and that the same point had gotten in there more than once.  I can not connect the dots between my hypothesis and this fix.

    My next 3 tests were successful in that I could no longer recreate the error that used to happen reliably, but I am far from claiming the problem solved.

    I'll play the last toon through the zone and report back.

  • Avatar of Cladhaire Cladhaire May 20, 2011 at 07:30 UTC - 0 likes

    You're absolutely right in that when I updated that function for the new version I didn't properly clear the waypoint. However, I hope you're not calling that functions, it's private! I've added this to my local copy, waypointMap[nil] actually belongs at the end of the if block.

    So you're saying this *does* fix the issue, or is there still some outstanding problem?

    Last edited May 20, 2011 by Cladhaire


May 11, 2011
New - Issue has not had initial review yet.
Defect - A shortcoming, fault, or imperfection
Medium - Normal priority.

Reported by

Possible assignees