[Bug]: Movement distance not shown in player mode (either server client or "show as player")

[jbrown123]

Describe the Bug

In this particular campaign file (attached) I don't see the token movement distance when in "show as player" mode. Same thing happens when using a client to a server session. I was asked to post this by @Azhrei on the discord server in #maptool-support.

I attempted to recreate this from scratch by starting a new campaign file but I'm not able to reproduce the bug in a new file. I THINK it has something to do with VBL. I note that this is the same behavior (no distance shown) when you move a token into a VBL area or into an area where there's no possible path from the origin to that location. It seems as though MT is partially confused about the VBL coverage. This is further confirmed by moving the token completely outside the area originally defined by VBL (outside the 'dungeon'). Outside that area (in the "grasslands") you DO see the movement distance displayed. Inside the "dungeon" you don't see it displayed (as player).

Campaign file (renamed to .zip): movement bug.zip

To Reproduce

1. Load the attached campaign
2. Make sure "fog of war" is on (Map | Fog-of-War)
3. Move the token "inside" the dungeon area
4. Note that you see movement distance both as a line and in the box below the token
5. Turn on View | Show as player
6. Move the token again inside the dungeon area
7. Note that you do NOT see the movement distance displayed nor the path of the token
8. Now move the token to a spot completely outside the dungeon area into the "grasslands"
9. Now move the token around on the grassland area and note that you DO now see movement distance

Expected Behaviour

I expect to see movement distance displayed when "show as player" is active

Screenshots

Movement distance shown when not in "player view":

Movement distance NOT shown in "player view":

Movement distance IS show in "player view" outside of VBL area:

Here's the defined VBL:

MapTool Info

1.15.2

Desktop

Win 10 64 bit

Additional Context

No response

[kwvanderlinde]

Haven't debugged it yet, but it seems there is some incorrect FoW information saved for the token. I'll try take a deeper look sometime this week to see exactly why that could be.

As a workaround, I tried restoring FoW. This seems to fix the issue. With the map open, go to the Map menu and select Restore Fog-of-War. After that the token movement should show properly again.

[jbrown123]

@kwvanderlinde interesting that restoring FoW fixes it. It's definitely something in the VBL / FoW code.

Edited to add: BTW, in the original campaign file this was happening to all the PC tokens, not just this one token. So it isn't unique to this one token or it's FoW information.

@Jmr3366 suggested on discord that this might be a known issue. Here's his comment:

I think this maybe a known issue but under another name.
When BL is drawn in a certain way something breaks* and this is the side effect. I removed all your BL, took your map to 25 per cell from 100, redid the VBL holding ctrl down (to lock BL to grid points), put your map back to 100, and it worked as expected. There are several points in your BL that are floaters (and it is a bug).