Routing

[Ambeco]

The option to find a route through the current gathering nodes is nice, but frequently has me fly up one side of a valley, and then back down the other side when one sweep up the middle would show them all. I assume this is the case because it tries to find the shortest path between the points. I believe that if it is set to treat the distance between each node as 80 yards shorter (or whatever is the tracking distance) with a minimum of zero, that should cause it to "path" an entire valley in one swoop instead of two or three, leading to more optimal loops through the zone. I'll dig through the code and see if I can test it myself, and will post my findings IF I can get it.

[Ambeco]

I replaced line 9615

local dis=(x-pt.X) ^ 2+(y-pt.Y) ^ 2

with:

local dis=(x-pt.X) ^ 2+(y-pt.Y) ^ 2 - 80
if dis<0 then dis=0 end

I didn't move between testing the original code and my code, but the original path was 72 nodes with 12136 yards, and my code was 72 nodes with 11319 yards. It only saved about 817 yards, but also had much less doubling back than the original code, which I found very nice.

Obviously, this isn't really a bug, but I feel that the "feature" could use this easy optimization.

[Ambeco]

I should also mention that I can't really read the code easily around there, and I don't see a square root function, so you guys can probably implement a similar change that is more accurate or efficient.

[Ambeco]

Nevermind on that change, I actually read more of the code, and that's totally the wrong place/code. I don't know why it shows a shorter path. The correct change is at line 24767, but I haven't quite interpreted enough to implement my suggestion.

[Jigain]

...or you could just change the options in the game?

Right click the map, Route... then adjust the sliders you see there.

And for future reference, the Blizzard tracking distance is 80 yards.

[Ambeco]

After studying the code, and getting only the vaguest idea of how the path optimizer works (Nx.Map:RoO and Nx.Map:RoS), and testing to see that subtracting 80 from each distance formula didn't work, I've determined that this is a little harder than I thought. I just wish I didn't go through Thunderfall, Dun Niffelhim, and Brunnhildar twice each for each loop through the Storm Peaks.

[Ambeco]

OMG.
I can apparently read through the code and interpret their unformatted LUA code better than read the options menu that I've been using to test.

[carboniteaddon]

Originally Posted by Ambeco I should also mention that I can't really read the code easily around there, and I don't see a square root function, so you guys can probably implement a similar change that is more accurate or efficient.

We don't need a square root function for that since we are comparing squared distances for closeness, which is the same as doing it on the root of the distance, but faster. Subtracting 80 won't work since you are doing it on the square. You need to do that after a square root or using 80*80. That would give different results than the UI distance, which is a check after the route is calculated.