Hi! Wonderful work overall on the addon, used Cartographer_Routes and switched to this a short time ago. I love the feature to Cluster nodes, it seems to work awesome. However, when gathering an herb, it always un-Clusters that herb and any around it, resorting to the un-Clustered route. The rest of the nodes in other parts of the zone remain Clustered.
Any changes I can make to fix this, or is it possible to "fix" this in a future version? Thanks!
Thank you for your report Bahl. I have removed 4 lines of code in r61401 that should fix the issue that you have reported.
I removed an unnecessary radius check in the node insertion code. Basically, the issue was that suppose your cluster radius is 60 yards. When you try to insert a node, it checks to see if the new node is within 60 yards radius of a nearby cluster. If this is 61 yards, it would not attempt to go into the cluster, even though the center point could have just been moved 2 yards and it would have worked. This has been fixed.
Thank you so much for this addon, and all the fixes. I now have awesome Shadowmoon routes that ignore the Path of Conquest and the big flayer hill in the middle of Netherwing Ledge, preventing many auto-pilot deaths. ;)
Minimap line drawing seems to be bugged.
The problem occurs in the latest version of the now discontinued cartographer_routes.
The problem, is that the lines are drawn, but have holes / gaps in them.
I suspect or presume that this is because the lines are not drawn on the minimap where there are normally gather icons.
I have hidden icons on the minimap as these were annoying.
However the line that is drawn on the map is now showing holes in it.
Hi BBR, this is intentional. You can disable "Draw line gaps" in the configuration options (in both Routes and Cartographer_Routes) if you do not want those line gaps to appear at all.
Also, not sure if this is fixed yet, but when you "find" new nodes while an optimisation is in progress. any nodes found while optimisation was running will be deleted.
BBR, that is intended and unavoidable. While optimizing a route in the background, I cannot insert any new nodes into the optimizing process as it is running it its own coroutine running about 10 layers deep of for-loops.
Basically, you should only be optimizing routes you aren't actively modifying, or you should just use Foreground Optimization instead of Background.
Foreground doesn't seem that much faster, and locks up the game, so i avoid using that.
What i recommend is this (Much like swapping water in 2 jars, you grab a third)
* When optimisation is started, create a temporary buffer, and insert any new nodes found in there.
* When optimisation ends, read the temporary buffer and insert all nodes found into the main database after that.
Basically, don't insert new nodes into the main database while optimisation is running, but keep them in a seperate buffer (or both) until optimisation is finished.
This would prevent the loss of nodes.
Kind of silly to use an addon like Routes without having GatherMate_Data or Cartographer_Data or whatever so that you have 99.9% of known nodes available to Routes.
I've found nodes not in those data packages. Not many, but a few.
I have no problem with foreground processing freezing, it only takes a couple seconds, even on a massive pile such as all herb and mine nodes in HFP ^^.
using the latest routes (61470) and gathermate (62191) my new nodes for swamp gas do not auto added to the route. even a decompressing and new optimizing ..they dont add to the route. must delete the route and made a new one. no bugs in bugsack. dont know for herbs in actuall versions but autoadding to route had worked..at least for herbs. im sure it has worked for gas also before.
sorry for ma english but i think you know what i mean^^
Kind of silly to use an addon like Routes without having GatherMate_Data or Cartographer_Data or whatever so that you have 99.9% of known nodes available to Routes.
Gas nodes are quite sparse tbh, while i'm gathering those, i tend to do the occassional optimize to figure out a better search path.
And the added code would be pretty small, for a great benefit.
1. After creating a Route that includes a node type, if you harvest a new (to GatherMate) node of a type that is included in the current Route, the Route is not updated to include it. This is similar to the problem listed in a post above, except I am not harvesting during the optimization phase or anything like that.
2. The other problem I've been having is that the Routes lines on the map have not been updating when GatherMate 'nudges' the node icon after harvesting it. This results in Routes that look like this:
I love this addon and am using this for mining but a problem I have is there if about 400 lines because of all the nodes. Is there away I can set this so the current line I am following will be a different color from the others so I dont get off track or hop on the wrong one when lots of lines intersect? If your current line would turn yellow or such that would make this addon so much easier when you mine. Please consider adding this feature if its not availble. Thank you.
sfagent07,
1. Cluster and Optimize your route(s).
2. Set a different line color in the options for each route in the same zone.
3. Show/Hide the routes in the current zone that you do not want to see (RoutesFu works well for this).
Recluse@Norgannon,
I have numerous reports of gas clouds not being updated to existing routes, but I have not been able to determine the cause. However, herbs/ore/etc work fine for auto-updating as far as reports go.
1. After creating a Route that includes a node type, if you harvest a new (to GatherMate) node of a type that is included in the current Route, the Route is not updated to include it. This is similar to the problem listed in a post above, except I am not harvesting during the optimization phase or anything like that.
[2008/02/29 20:40:32-1979-x1]: Routes\Routes.lua:1251: attempt to call method 'Print' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:492: in function `OnAccept'
Interface\FrameXML\StaticPopup.lua:2411: in function `StaticPopup_OnClick':
<string>:"*:OnClick":1: in function <[string "*:OnClick"]:1>
Any changes I can make to fix this, or is it possible to "fix" this in a future version? Thanks!
I removed an unnecessary radius check in the node insertion code. Basically, the issue was that suppose your cluster radius is 60 yards. When you try to insert a node, it checks to see if the new node is within 60 yards radius of a nearby cluster. If this is 61 yards, it would not attempt to go into the cluster, even though the center point could have just been moved 2 yards and it would have worked. This has been fixed.
The problem occurs in the latest version of the now discontinued cartographer_routes.
The problem, is that the lines are drawn, but have holes / gaps in them.
I suspect or presume that this is because the lines are not drawn on the minimap where there are normally gather icons.
I have hidden icons on the minimap as these were annoying.
However the line that is drawn on the map is now showing holes in it.
Please look into this.
Also, not sure if this is fixed yet, but when you "find" new nodes while an optimisation is in progress. any nodes found while optimisation was running will be deleted.
Basically, you should only be optimizing routes you aren't actively modifying, or you should just use Foreground Optimization instead of Background.
What i recommend is this (Much like swapping water in 2 jars, you grab a third)
* When optimisation is started, create a temporary buffer, and insert any new nodes found in there.
* When optimisation ends, read the temporary buffer and insert all nodes found into the main database after that.
Basically, don't insert new nodes into the main database while optimisation is running, but keep them in a seperate buffer (or both) until optimisation is finished.
This would prevent the loss of nodes.
How many people do a background while actively hunting new nodes? :S
I have no problem with foreground processing freezing, it only takes a couple seconds, even on a massive pile such as all herb and mine nodes in HFP ^^.
sorry for ma english but i think you know what i mean^^
Gas nodes are quite sparse tbh, while i'm gathering those, i tend to do the occassional optimize to figure out a better search path.
And the added code would be pretty small, for a great benefit.
1. After creating a Route that includes a node type, if you harvest a new (to GatherMate) node of a type that is included in the current Route, the Route is not updated to include it. This is similar to the problem listed in a post above, except I am not harvesting during the optimization phase or anything like that.
2. The other problem I've been having is that the Routes lines on the map have not been updating when GatherMate 'nudges' the node icon after harvesting it. This results in Routes that look like this:
(yeah, my fps sucks in terrokar :p)
1. Cluster and Optimize your route(s).
2. Set a different line color in the options for each route in the same zone.
3. Show/Hide the routes in the current zone that you do not want to see (RoutesFu works well for this).
Recluse@Norgannon,
I have numerous reports of gas clouds not being updated to existing routes, but I have not been able to determine the cause. However, herbs/ore/etc work fine for auto-updating as far as reports go.
Same issue as found here : http://www.wowace.com/forums/index.php?topic=11280.0
Hope it's fixed soon.
Haven't seen any line-nudging myself.
[2008/02/29 20:40:32-1979-x1]: Routes\Routes.lua:1251: attempt to call method 'Print' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:492: in function `OnAccept'
Interface\FrameXML\StaticPopup.lua:2411: in function `StaticPopup_OnClick':
<string>:"*:OnClick":1: in function <[string "*:OnClick"]:1>
---
I have finally found the issue with the non-updating routes in Routes. This is fixed in r63250. Please update and test.
----------------
Hi Elsia,
Fixed.