Unexpected calculations when moving up Terrain Mapper Elevations

[a-mannered-bird]

Hello and before all thanks for this amazing module!

I'm currently working on adding a lot of elevation to some of my battlemap, but I found that the Elevation Ruler is behaving inconsistently when calculating a diagonal on a Terrain with Elevation.
In the example below, moving down on a "Plateau/Mesa" or "Ramp/Steps" elevation terrain of 5ft elevation totals 10ft of movement. But if I try to move one block on normal terrain and "fly" 5ft up, it only costs 5ft of movement.

In both cases I would have expected 5ft of movement only, because I consider that both movements are in fact a simple diagonal move. Is it a bug or a choice in this calculation? Is going up the plateau calculated as difficult terrain or something?

I'm running Foundry V12 Stable 331
Dnd 3.3.1
Elevation Ruler 0.10.12
Terrain Mapper 0.4.6

[caewok]

How about in ER v0.10.13 and TM v0.4.7?

[a-mannered-bird]

Thanks for the answer @caewok. I tried ER v0.10.13 and TM v0.4.7 and the problem stayed the same.
I also tried with ER v0.10.14 and TM v0.4.8 but the issue remains. I tried to recreate the terrain just in case but it doesn't change anything.

[a-mannered-bird]

@caewok Any news about this issue? Are you able to reproduce it?

[caewok]

I looked into it some more. It appears that moving into a region breaks the move into 2 waypoints from the ruler's perspective. So here we have:

1. Origin --> Move 5 feet south.
2. From Ruler display between users does not update when elevation is changed #1 --> Move 5 feet vertical up the plateau.

By definition, the ruler measures each waypoint separately. There are some good reasons for this. A horizontal movement followed by a vertical movement is qualitatively different than a combined diagonal that moves horizontal and vertical at the same time.

Unfortunately, I don't see a reasonable way to combine the two distinct movements here. And depending on what you think of the geography, it may in fact make sense that the plateau causes you to move straight up. If the two moves were combined, it would mean the token could fly, as there is no "plateau" under the token for most of a combined vertical/horizontal diagonal move. (Again, I am aware that this fails to measure a diagonal move even if flying is the token's status, but base Foundry does not treat it this way.)

Something to revisit in Foundry v13, which is making a lot of changes to elevated movement, regions, and measurements.