Not signed in (Sign In)

Support::Gatherer: What happened to the range on the HUD?

Bottom of Page

1 to 19 of 19

  1.  
    • CommentAuthorfyrekev
    • CommentTimeMar 29th 2008 edited
     
    After upgrading to the 2.4 version, I notice that the HUD has apparently been gimped. Prior to the patch, the HUD would cover a very large area around my character, and new and distant nodes would slowly fade into view as I got closer to them. I would never have to open the map screen at all to look at node locations, the distance that the HUD covered made that unnecessary. But now since 2.4, the HUD covers just a small area around me, not much wider than the size of the minimap. This effectively forces me to open the map frequently to plot my next course. What changed? Or are there some settings that I am missing somewhere?
    • CommentAuthorRockSlice
    • CommentTimeMar 29th 2008
     
    Please look in the Gatherer HUD options for "range"
    • CommentAuthorDragonWin
    • CommentTimeMar 30th 2008
     
    Ohh!!! just had a brainwave when I noticed the range where exactly the same as the minimap. Seems the 2 are tied together in some way, so when I increased the amount displayed on the minimap it also changed the amount displayed on the HUD.

    Is it possible to have those 2 separate, so my minimap does not go berserk with 50 nodes ?
    • CommentAuthorfyrekev
    • CommentTimeMar 30th 2008 edited
     
    Rock, I did adjust all of the options in the HUD settings, they did not do anything to put it back the way it was pre patch. The range before hand was still much longer than it is now.
    •  
      CommentAuthorNechckn
    • CommentTimeMar 31st 2008
     
    Fyrekev,

    You should still be able to set the HUD to track nodes over an exceptional distance above that shown in the minimap- and there have been no changes made to limit that distance.

    Perhaps you have modified the size of the nodes or some such thing?

    The full changelog since October of 2007 is available: http://www.gathereraddon.com/?p=home

    DragonWin- The options allow seperate settings for the number of nodes, distance covered, ad infinitum for the minimap and the GathererHUD. Simply set each to your desired settings.

    Happy Gatherering,

    Nikk :shades:
  6.  
    I can confirm, that the number of nodes diplayed on the hud is linked to the number of nodes on the minimap.
    Just moving the optionbar on the Miniap options, pops in and out the nodes on the hud.
    The max display is 30, that's not enough. In the Hud-Optionmenu is no optionbar to set the number of nodes to display.

    Checking the code, i didnt find a variable like MiniMap.count (default seting 20) for the hud.

    This problem occurred allready in the past, by seting the default value from somewhere 30 to 100 or even 300 solved the problem.
    I couldn't find the apropiet posting in the forum.
    •  
      CommentAuthorNechckn
    • CommentTimeApr 4th 2008
     
    Spacetrapper,

    Have verified, in game, that 3.x, 3.1 and 3.11 versions of Gather most certainly allow you to adjust the number of nodes for the GathererHUD independently of the settings for the Gatherer display on the minimap.

    To test, simply bring up the Gatherer options menu, via the Gatherer button on the SlideBar, installed by default just below the minimap. Select the HUD module, grab said window and slide down the screen a bit and adjust the size, scope, and number of nodes tracked and the HUD responds appropriately with no impact on the minimap.

    Also, zooming in on the minimap has no affect, what so ever on the HUD display.

    Perhaps you have some sort of remnants that no one else has seen, so try deleting the Gatherer folder and GatherHUD from the ..\WorldofWarcraft\Interface\AddOns\ folder and reinstall a clean copy from GathererAddOn.Com/dl.

    If you find some other thing happening, kindly provide a screen shot or two. You are welcome to upload the images to Up.Norganna.Org, if you so desire.

    Nikk :shades:
  8.  
    The Screenshots

    HUD Options:
    No Optionbar to set numbers of Nodes (scrolling down, ther are only options for colors and tracking)
    http://up.norganna.org/index.php/v2aduzy/HUD_Options.JPG

    20 Nodes Display:
    http://up.norganna.org/index.php/vPa1akB/Minimap_20_Nodes.JPG

    30 Nodes Display:
    http://up.norganna.org/index.php/vqRRF4Q/Minimap_30_Nodes.JPG

    Minimap Disabled:
    http://up.norganna.org/index.php/vmQiFTG/Minimap_Disabled.JPG

    About:
    (Check Version)
    http://up.norganna.org/index.php/ve6PHAT/Gatherer_About.JPG

    And yes, i delete the folder every time i load a new version.
    •  
      CommentAuthorNechckn
    • CommentTimeApr 5th 2008
     
    SpaceTrooper,

    Apologize for not being more clear, thought it was. The interplay of options works like this- the minimap is the master and the HUD the slave, for lack of better terms.

    Once you have set the minimap to your liking, then change the "range" setting on the HUD options, which has not changed from 2000.

    This means that the HUD is variable to any size, smaller than the minimap. "Range", in this case, being set on the HUD- figure one of those you posted.

    As the HUD is an extension of the minimap, if tracking is set to off, then tracking will be, effectively, off for both.

    The original question, posed by Fyrekev, was in regard to the range of the HUD and if the settings have been decreased, which they have not.

    Certainly hope that clears up any misconceptions.

    Happy Gatherering,

    Nikk :shades:
    • CommentAuthormihale
    • CommentTimeApr 7th 2008
     
    I was throughly upset with the latest patch thinking you had nerfed the hud. Even though my flightpath showed up over a great distance the hud was only displaying nodes within a very close range. I played with just about every setting under the hud options to no avail. It wasnt until I read this that I changed the mini map setting to display the 50 (maximum setting) closest nodes. This is better but is no where near the number of nodes that used to appear on the hud. At this point I'm going back to a previous version and can only hope that you will either increase the maximum setting or better yet, unlink the minimap display from the hud display.
    • CommentAuthorEsamynn
    • CommentTimeApr 7th 2008
     
    How do I say this more clearly???

    THE BEHAVIOUR OF THE HUD HAS NOT CHANGED IN MONTHS!!!

    Period.
    • CommentAuthoriffer
    • CommentTimeApr 10th 2008 edited
     
    umm Esamynn... maybe it hasnt for you, but for me the behavior has changed dramatically.
    last week, the hud showed nodes from all around the zone. this week with the gatherer upgrade all it shows is the nodes very close to my location. This wasnt a subtle change. Maybe with your settings it isnt noticable?

    Nechckn's description of the behavior (that the HUD is a subset of the minimap selection) matches what I have seen, but as the HUD is a much larger area/overview using just nodes on the minimap isnt a good criteria. Maybe use the world map display criteria?
    Is it possible the change is from the new "show closest xx nodes" option?
    A workaround would be to set the minimap range very large - but then the edges of the map get crowded (I want some on the edges, but not the whole zone worth - I have other arrows and guides up there to see too!).
    If you like I can post my settings file - perhaps I'm using the settings in a manner you hadnt expected (lol I'm doing it wrong) but obviously from this thread, I'm not the only one seeing a change in the display.

    Jennifer
    •  
      CommentAuthorNorganna
    • CommentTimeApr 10th 2008
     
    The trouble is that the calculation of the "nearest nodes" is a very expensive operation, and being as it's recalculated as many times per second as it is already, doubling that number is not exactly a wise move.

    This is why the HUD and the minimap share the same set of nodes (so there's no need for recalculation)

    I had thought that there was a piece of code in the minimap code prior to the Gatherer -> Gatherer+HUD separation that used max(numMinimapNodes, numHudNodes).

    It may be that this code has since been removed due to the fact that HUD is now a separate addon. If you guys were using pre-separation Gatherer and upgraded to post-separation Gatherer, I can see how you would be observing this phenomena.

    I'll have a look and see if I can add some API function to Gatherer to let it know we need more nodes calculated than just what it requires for it's own minimap display.

    Thanks for the feedback.
    • CommentAuthoriffer
    • CommentTimeApr 10th 2008 edited
     
    Hi Norganna
    yes - this is the first upgrade for me with the HUD as a plugin
    and yes - there are quite a few expensive calcs in there. but in this case it should be less expensive since
    the hud only needs to examine the nodes based on global filter rules and range calcs.
    (as opposed to the mini map which needs a seperate max range+nearest N+clip to minimap border+fade+detection range icon/circle selection filtering/render pipeline)
    Maybe just swap it so that the minimap is a subset of the HUD nodes?
    Thanks tons
    Jen
    ps
    Thinking about it - the "closest xx nodes" must be an incredibly expensive operation (sorted list with insert/delete)! Does setting it to zero disable the filter? (I would hope there is someway to turn off that flitering operation)
    On the other hand, if you are doing a range sorted list, then your boundry pruning is just a list lookup rather than the re-calc range for every clipping operation and the modules can be updated to take advantage of the pre-computed range values out of the list.
    (I looked at the hud code and its computing range from coords)
    Jen
    • CommentAuthorEsamynn
    • CommentTimeApr 11th 2008 edited
     
    Posted By: NorgannaIt may be that this code has since been removed due to the fact that HUD is now a separate addon. If you guys were using pre-separation Gatherer and upgraded to post-separation Gatherer, I can see how you would be observing this phenomena.


    Oops, I didn't intend for that to get removed, but it was. I have been checking the HUD code for changes, I didn't think to look over the changes made to Gatherer's core code during the separation because I tried to be very careful to not change anything substantially.

    Always helps when the primary author looks into stuff, thanks norgs.

    Edit: My apologies for taking such a hard line on this. I really should have done a more careful check of the changes that I made, when I was pulling the HUD out to make it into a plugin, before I started being such a hard head.
    • CommentAuthorsieraj
    • CommentTimeMay 31st 2008
     
    Is there an update coming to restore the range on the hud to it's pre-Gatherer+Hud split levels?

    I used to have half of a zone up on the screen to plot a good route.... now I've got less then viewing range. =/
    •  
      CommentAuthorNechckn
    • CommentTimeJun 1st 2008
     
    Sieraj,

    That is one of the things in the "To Do" list.

    Unfortunately, there is, at present, one developer who is focused on Gatherer and they have been extremely busy with 'life' stuff.

    When a new version is released, keep an eye on the "release notes" for what has been included/changed.

    Happy Gatherering,

    Nikk :shades:
    • CommentAuthorMerendel
    • CommentTimeJun 11th 2008
     
    Found a way to ungimp hud somewhat but it comes with a rather drastic performance hit.
    In the GatherConfig.lua file find this line
    gui:AddControl(id, "Slider", 0, 2, "minimap.count", 1, 50, 1, _trL("Display: %d closest"))

    Change the 50 to however many nodes you want as max. I put in 350 for mine. now in minimap settings you can set max nodes slider higher than 50 closest nodes. To keep the edges of the mini map from being packed set fade distance to about 500yards and distance fadeing to 100%

    you'll need to adjust the hud size a bit in the hud config to make things readable but you can now get about half a zone visable on the hud. Major drawback is both the hud and minimap stutter a bit while moveing instead of smothly flowing like normal. If you can live with that this is a viable workaround till the developer has a chance to fix this.
    • CommentAuthorEsamynn
    • CommentTimeJul 14th 2008
     
    I have opened the jira ticket GHUD-7 for this issue.

    I hope to have it resolved for the next release. Sorry for the delay.

1 to 19 of 19

  1.  
World of Warcraft™ and Blizzard Entertainment™ are trademarks or registered trademarks of Blizzard Entertainment, Inc. in the U.S. and/or other countries.