Enemy Tokens Always Visible On Map

[Brian D]

5e Campaign in FGU on Windows 11: Enemy Tokens Always Visible On Map

For the last two sessions this month enemy tokens always remain visible on battle maps. LOS works fine and the token location (even behind walls) makes no difference to player visibility. I've deleted tokens, reset maps, rebooted the software, reloaded the combat tracker of all friendly and enemies, tried other campaigns, and the problem persists. A brief overview of actions taken thus far:


Moved tokens from combat tracker to battle map, ensuring 'Mask Sensitive Visibility' toggled on token and 'Hide NPC' active on combat tracker. No combination of on or off hides tokens from the players.
Turned off all extensions. (This did not fix token visibility in either campaign loaded into my computer)
Updated the software.
Looked through forums without finding a solution.

Two pictures are linked below, one with Player Vision Preview and the other without.

Thanks!

54136

54137

[Zacchaeus]

So your screenshots are from the DM view and as DM you will see where enemies are if they are on the map (no matter what settings you have) and even if they aren't in the LoS of any of the PC tokens. Are you saying that your players see all the enemy tokens?

If that is the case you'll probably need to zip up your campaign so the devs can take a closer look to try and establish an issue.

[Moon Wizard]

When the token is grayed out, it is only visible on the GM client application (even with player preview).

If you want to see exactly what the end users see, start a second instance of Fantasy Grounds and connect to your own session.

Regards,
JPG

[Brian D]

My players all saw the tokens, no matter the location on the map. I'll need to zip up the campaign. Please PM for where to email the files

[Zacchaeus]

Attach them to a post here or put them on Dropbox or similar and post the link.

[Brian D]

I unloaded and reloaded all ext. files and tokens, then restarted a combat with a second client and so far have not been able to reproduce the token problem described by my players. This is more than likely an operator malfunction with the 'Mask Sensitive Visibility' function being set to 'Always Visible' without me being aware of it during the game. It seems I needed to ask for help publicly to figure out I more than likely had my token visibility default set incorrectly.

As always, thanks for the prompt response Zacchaeus and Moon Wizard. I appreciate the help :)