Measurement arrow gives false information after 10 feet

This may not be the case in all systems, for D&D 3.5 diagonal movement is counted as 1 square (5') for the first diagonal movement, then 2 squares (10') for the second, 1 square for the third, 2 squares for the fourth. Essentially 1.5 squares rounded down per square moved diagonally. A square marked as 15' away going diagonally the entire distance is actually 20' away. Perhaps a "movement calculator" and a "distance measurement" could be implemented?

This is not a bug, it is how it is currently coded. It is based on D&D 4E measurement rules but since this is reported quite often they may be working on changing it or giving an option for a different measurement system. Note: if you go gridless the measurements are accurate. - Gauss

makes no sense to use 4e rules for those who do not play 4e so yes a choice would be nice

I agree Punisher, but remember that this is a work in progress that has only been up since...May? I am still quite impressed with the features Roll20 does offer while still being easy to use. I am sure they will fix this at some point so we can use it properly. There are other measuring tool requests that are out there are such as counting squares and hexes (rather than feet or other units of measurement). Note: I don't play 4E either, I play PF (amongst other games). - Gauss

Riley, thank you for asking. 3.X/Pathfinder uses a 5-10-5 (in feet) measuring distance. What this would amount to is Euclidean rounded to the nearest 5. A square counter would be great also. Many people measure distance in squares rather than feet. For 3.X/PF that would be 1-2-1 rounded to the nearest whole number. Also, Hexes do not measure correctly. The best way I can see to count hexes would be an actual hex counter (rather than distance). Perhaps you can see some other option to make hexes count properly. I would count hexes from center to center of each hex. Thanks for your time on this. - Gauss

The 3.5 or pathfinder distance would be most helpful. Every other diagonal counts as 2 squares. Additionally, in the future anarea measuring for effects and spells would be nice based on this distance dynamic. Currently the square supports 4E radius and the circle supports Euclidean radius, but the 3.5 distance results in an odd shaped hybrid based on the distance. Keep up the excellent work. Note - For those who are enjoying the roll20 experience, I highly recommend upgrading to the $10/mo version. I have greatly enjoyed my upgraded mentor status and my group loves the upgrades for our weekly game night.

I think its connected with measuring distances alghoritms, so i'll post it here. Today i wanted to use auras to show area of illumination for players, and sadly, when my grid is set to 1,5m per grid tile and i set aura radius to 6m, it behaves like it was rounding grid size down to 1m, and aura is 50% bigger than it should be(9m in radius).

I really can't get over the fact that you consider "Doesn't cater to how my system handles diagonals" as "false information".

I'm glad you implement other measurement systems! When are we see the changes in prod? =D The type of measurement will be configured from the settings tab?

Has there been any more updates on this since?

A lot of these issues would go away if we could set waypoints with the spacebar as we measure.

Has nothing to do with tokens... it's about measuring. Being able to measure using waypoints would fix the issues with 3.5 and Pathfinder. Characters don't move from point A to point B directly. They move along a specific path of squares. Setting waypoints would fix the issue.

.

Frostaqua: While humans can easily figure out what you just posted the computer is a stupid beast of burden. The trick is how to represent what humans can do naturally in the form of an equation that works? Pathfinder's movement system is not easily converted to an equation. - Gauss

Actually we just pushed out the 3.5/Pathfinder one as well. It works well for diagonals and straight lines, not really sure how non-45-degree-angle diagonals should be handled... Your best bet on doing this for Roll20 is to do the following: To get the correct distance on a Pathfinder/3.5 non-45 degree angle, calculate the diagonal component first, then the straight component and add them together. Guaranteed to be correct every time. Of course, this is just for checking range and for checking movement in open areas. Anything more complicated, like double cost for moving through difficult terrain, around corners, etc., is going to have to be calculated by the players/GM as this is beyond what Roll20 should be doing as a system-agnostic virtual tabletop.

Riley: 3.5/Pathfinder does not require that the diagonals be consecutive. If I move diagonally, straight, and then diagonally I keep track of the diagonals as one stretch for the purposes of counting. The measurement tool needs to count diagonals and straight elements separately and then sum them up. Mel's second picture is a good example of this. - Gauss

Even if you take one diagonal right at the beginning (counts as 5ft) then go straight for 5ft, then take a final diagonal, that last diagonal will still count at 10ft in pathfinder. Even if the straight part in the middle is 1000ft, the two diagonals always count as a total of 15.

4E diagonal movement is easier to do. Pathfinder/3.5 is a bit harder, but gives a more circular radius instead of a square. The game Monsterpocalypse did something different to fix the "square" radius. In that game, you could do "one and only one" diagonal for a regular move, the rest had to be straight. Luckily for you, Riley, you don't need to know the Pathfinder rules. There are plenty of us here that do. Glad to help.

Looks great! Thanks, Riley.

I tried setting one of my maps to Euclidean distance measurement, but it appears to still be giving me 4E style measurements.

Could you please doublecheck that that map is currently set to Euclidean by going to the Page Settings? Thanks - Gauss

Aha! I was closing the Page Settings popup without clicking 'Okay'. My fault. And of course, then when I tested the ruler it still behaved like 4E. However, when I re-entered the Page Settings popup, it still *displayed* the 'Euclidean' setting. Giving me the impression that I'd successfully changed it. You should probably make sure that the popup doesn't display any un-'Okayed' changes if the GM closes and re-opens it.