Map memory bug?

[nephranka]

I am noticing a lack of map memory for tokens if a FX layer is used. Maybe this is expected or I am doing something wrong.

Steps:
1. Open BattleMap01
2. Add a area of water fx on the map using add a mask/unveil area (center of Battlemap01 small circular area)
3. Drop the token on the map
4. Turn on preview
5. Move around

6. Open Battlemap02
7. Drop the same token
7. Turn on preview
8. Move around

No remembered areas in Battlemap01 but there are on battlemap02.

New campaign, no ext, no mods but FG maps.

[pindercarl]

I am noticing a lack of map memory for tokens if a FX layer is used. Maybe this is expected or I am doing something wrong.

Steps:
1. Open BattleMap01
2. Add a area of water fx on the map
3. Drop the token on the map
4. Turn on preview
5. Move around

6. Open Battlemap02
7. Drop the same token
7. Turn on preview
8. Move around

No remembered areas in Battlemap01 but there are on battlemap02.

New campaign, no ext, no mods but FG maps.

The fog-of-war does not persist when a token is removed from a map.

[nephranka]

The fog-of-war does not persist when a token is removed from a map.

Thanks. That is why I say "move it around" you will see no map memory. I used 2 maps to show the difference. Battlemap02 has the memory (while you are on it) and Battlemap01 does not.

[pindercarl]

Thanks. That is why I say "move it around" you will see no map memory. I used 2 maps to show the difference. Battlemap02 has the memory (while you are on it) and Battlemap01 does not.

Thanks for the clarification. That is indeed peculiar. I will have to investigate further.

[nephranka]

I was wondering if you were able to confirm or fix?

[pindercarl]

I was wondering if you were able to confirm or fix?

I confirmed the bug and am currently investigating a fix.

[nephranka]

I confirmed the bug and am currently investigating a fix.

Thank you for the update.

[pindercarl]

Thank you for the update.

This should be fixed in today's update.

[nephranka]

This should be fixed in today's update.

That looks to have fixed it. Thanks!