Ruler doesn't work with Hex grids

I know this has been mentioned before, but every thread I could find was closed. Simply enough, the ruler tool doesn't work for hex grids. Even when comparing the same number of hexes' distance along the 6 directions that go straight through each hex, you get different results depending on whether you go on a diagonal or not, (using Euclidean). This suggests the hexes aren't regular hexagons? Ideally the ruler would count the number of hexes passed through to the destination hex. Currently I'm working around by setting grid size to 0.93, and only using the ruler along the the 6 directions that go straight through the middle of each hex, which requires two measurements and adding them together. This gives a number that's close enough most of the time, but not always and it's a pain in the butt. Last thing broken about hexes: The labels miss every second number.

This was with Vertical hexes, and diagonals set to Euclidean

James , the ruler isn't broken per se but is not set up properly for Hexes. However, there is a workaround that should help. The best way to get the proper approximation is to measure a long stretch of distance. Example: 20 hexes. Then divide that by the result of the ruler. Step 1: Measure the straight line (horizontal or vertical) distance out to 20 hexes. At scale = 1 and unit = 1 for Hex (V) I got 20/21.5 Step 2: Measure the diagonal disttance out to 20 hexes. At scale =1 and unit = 1 for Hex (V) I got 20/21.9 Step 3: Decide which direction you want to be most accurate or split the difference. In this case splitting the difference I do the following: ((20/21.5)+(20/21.9))/2 = ~0.9217 Step 4: Set the scale to the desired value. Note: I split the difference and then I mentally round up or down. It will be so close that over the 20 hexes of distance the ruler is only off by only +/-0.2 in either direction. Longer distances and more decimal places will produce more accurate results. If you need me to come in and help you set it up let me know. - Gauss

Yeah that's the same process I already did, I used 0.93 though, as desribed above.

The errors used to correspond to a misapplication of sine instead of cosine (or vice versa); now, they don't correspond to anything I can identify. They need to stop putting devs who failed trig class on this problem. The Manhattan Distance doesn't work either, and that's an easier problem to fix, and more likely what players are after, anyway.