Archy - Archaeology Assistant

384 - Digsite distances wrong

What steps will reproduce the problem?
1.Log into the world. I see the Fragment box, but no Digsite location Box.
2.Open the World map, right click to continent view. Close the map.Digsite Location box is now showing, but distances are 9999999
3.Move Character slightly, distances numbers correct themselves but are still incorrect based on my location.

My character is at 51,27 in the Badlands (Hammertoe's Digsite). The Archy Digsite window says the Plaguewood Digsite in EPL is 92 yards away. This is after a reload as well.

What version of the product are you using?
1.8.18
Do you have an error log of what happened?
Producing zero errors

Please provide any additional information below.
Adding a screenshot as well to clarify.
**Edit**  As an additional note, clicking on the Digsite name in the Digsite list, does open the map to the proper zone.

  • Distance_error_no_digsite.jpg
    Digsite Error
  • world_map_showing_zone_digsites.jpg
    World Map showing zone wide ...
  • world_map_showing_continent_digsites.jpg
    Worldmap with Digsites shown on ...
  • reload_ui.jpg
    After a reloadui
  • mouseover_world_digsites.jpg
    Mouseover of minimap button ...
  • worldmap_opened_then_closed_nomovement.jpg
    WorldMap cycled to update ...
  • moved_character_distances_updated_still_incorrect.jpg
    Character moved slightly. ...
User When Change
Vis_wowi Mar 13, 2012 at 14:46 UTC

Deleted attachment WoWScrnShot_031212_161014.jpg: duplicate of others

Vis_wowi Mar 13, 2012 at 14:44 UTC

Added attachment moved_character_distances_updated_still_incorrect.jpg

Vis_wowi Mar 13, 2012 at 14:40 UTC

Added attachment worldmap_opened_then_closed_nomovement.jpg

Vis_wowi Mar 13, 2012 at 14:35 UTC

Added attachment mouseover_world_digsites.jpg

Vis_wowi Mar 13, 2012 at 14:34 UTC

Added attachment reload_ui.jpg

Vis_wowi Mar 13, 2012 at 14:19 UTC

Added attachment world_map_showing_continent_digsites.jpg

Vis_wowi Mar 13, 2012 at 14:18 UTC

Added attachment world_map_showing_zone_digsites.jpg

Vis_wowi Mar 13, 2012 at 14:17 UTC

Added attachment Distance_error_no_digsite.jpg

Dridzt Mar 12, 2012 at 23:13 UTC Changed assigned to from Torhal to Dridzt
Vis_wowi Mar 12, 2012 at 20:25 UTC Changed description:
  Producing zero errors

  Please provide any additional information below.
- Adding a couple screenshots as well to clarify
+ Adding a screenshot as well to clarify.
+ **Edit**  As an additional note, clicking on the Digsite name in the Digsite list, does open the map to the proper zone.
Vis_wowi Mar 12, 2012 at 20:21 UTC

Added attachment WoWScrnShot_031212_161014.jpg

Vis_wowi Mar 12, 2012 at 20:19 UTC Create

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

  • Avatar of Dridzt Dridzt Mar 17, 2012 at 18:26 UTC - 0 likes

    As a temporary fix Archy detects the incompatible setting in TomTom and offers to disable it in 1.8.19 and later.

    Unfortunately this will either need a significant re-write or a fix from TomTom side for a proper fix.

    Leaving the ticket open for now to signify this as a 'loose end'.

    Last edited Mar 21, 2012 by Dridzt
  • Avatar of Dridzt Dridzt Mar 16, 2012 at 05:27 UTC - 0 likes

    Could be yes, I already closed another ticket that was duplicate to this one.

    As an update I've been unable to solve this on Archy's side other than by forcibly disabling the problematic TomTom option from Archy's code which is not something I'd like to do.

    I've filed a ticket with TomTom's author and hopefully he can sort it on his end.
    The main problem is the offending function in TomTom (ObjectivesChanged()) runs in an OnUpdate (ie continuously) so it's very hard to workaround.

  • Avatar of Vis_wowi Vis_wowi Mar 16, 2012 at 02:26 UTC - 1 like

    @Dridzt: Go

    Is it possible that this is the same thing that's happening to Barleduq on ticket 380? I was reading the comments on WoWinterface and the effects sounds really similar. And once the addon is acting up, I'm guessing any behavior is possible,.

    I'll cross my fingers and hope you get 2 birds with one stone.

  • Avatar of Dridzt Dridzt Mar 15, 2012 at 15:06 UTC - 0 likes

    Got a scare there as I couldn't reproduce even with your directions.

    It turns out it's not only that you need to have tracked quests and the relevant option in TomTom to automatically set quest waypoints.

    There also needs to be such a quest and the resulting automatic waypoint on the current continent.

    That said we're back on track, at least I have a way to reproduce the problem now :-)

  • Avatar of Vis_wowi Vis_wowi Mar 14, 2012 at 22:13 UTC - 0 likes

    Good luck on figuring out a way to make it work. That's beyond me. I know how to get around it and what triggers it as a user now so I can still use both addons without severe issue until you get the fix out.

    Thanks for a great addon :)

  • Avatar of Dridzt Dridzt Mar 14, 2012 at 21:50 UTC - 0 likes

    @Vis_wowi: Go

    That's some great detective work there... I'll be sure to give you credit when we finally solve this. :-)

    If I have a way to reproduce it I'll find a way to fix it, changes in TomTom or not,
    my main issue has been doing guesswork because I couldn't make the problem appear on my side.

    Last edited Mar 14, 2012 by Dridzt
  • Avatar of Vis_wowi Vis_wowi Mar 14, 2012 at 17:19 UTC - 1 like

    I think I've found the conflict.

    Do a fresh install of the latest versions of both Archy and TomTom. Leave everything as default and it all works perfectly fine.

    Show the Archy windows while you do these changes.

    Now to make it fail, go into Interface Options to TomTom's settings. Under the Quest Objectives heading, add a checkmark to the empty box next to "Enable automatic quest objective waypoints". The "Arrival Distance" slider does not matter.

    Reload your UI. Only the Artifact Window should be showing. The Digsite window is hidden/gone. Mouseover the minimap button and your current continents digsites will not be shown. All the other continents will be shown though.

    This only occurs when you have Quests you are tracking. If you have no quests in your log, then changing that one setting has no effect.

    If I'm right and that is the conflict, I'd guess the fix would be to ask Cladhaire to code in some form of priority or switch system. Maybe one that temporarily disables quest tracking and their waypoints while the Archy windows are shown. Then once Archy is hidden again, the Quest Waypoints go back to normal. I have no clue how that all works though.

    Last edited Mar 14, 2012 by Vis_wowi
  • Avatar of Vis_wowi Vis_wowi Mar 14, 2012 at 16:41 UTC - 0 likes

    I did another clean install of both Archy and TomTom and have only them active. Everything set to defaults "out of the box". Everything is working perfectly fine. I've gone through probably 15 digsites with no glitches whatsoever.

    Then I changed the settings of both Archy and TomTom to my liking. And saved them to a different profiles.

    That's when the issue started to re occur. After I changed settings. While I was having the issue's if I set the Active profile for both TomTom and Archy back to the default, everything went back to normal. No problems. Somewhere there is a settings conflict. But I'm not sure how to duplicate it 100% right now. Any suggestions besides going one by one through both addons options?

  • Avatar of Vis_wowi Vis_wowi Mar 14, 2012 at 14:26 UTC - 0 likes

    @Dridzt: Go

    I am playing on Win7 64 bit. Generally I play windowed. I am using the 64 bit Alpha client. I am using the latest version of TomTom which is v40300-1.4.4.

    If it matters, I also have all libraries embedded with the addons. I do not run them separately.

    I'll do some more testing on my end today. Namely, I'll recheck to see if using Fullscreen or the 32 bit client make any difference.

    • A thought before hitting post* You mentioned Astrolabe. Code/Version wise is there a difference when you call or load "Astrolabe" which Archy calls, or "Astrolabe-1.0" which TomTom calls? Shooting from the hip and knowing just enough to get myself into trouble, wouldn't that force two separate instances of Astrolabe to run? Both trying to do the same thing and effectively when needing to be called, cancel each other out or create strange gremlins? Again, just a thought from a non coder.
  • Avatar of Dridzt Dridzt Mar 14, 2012 at 03:32 UTC - 0 likes

    Can you give me a couple more details.

    Are you playing on Windows or a Mac?
    Are you playing fullscreen or Windowed(Fullscreen)?
    Are you using the beta 64bit client by any chance?
    Have you updated TomTom to the latest version?

    If I can't figure this out (the major problem sofar being I can't reproduce it on any of my chars with or without other addons) I might upload a special alpha with debug information for you.

    What this looks like is that either some events don't fire on your system or Astrolabe (a map library both Archy and TomTom are using) fails to return information.
    Unfortunately that's only a 'best guess' by analyzing the code, as I can't make the problem happen for me.

    Last edited Mar 14, 2012 by Dridzt

Facts

Last updated
Mar 13, 2012
Reported
Mar 12, 2012
Status
New - Issue has not had initial review yet.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
0

Reported by

Possible assignees