Using ctrl+L when testing Dynamic Lighting; buggy?

I've finally gotten around to playing with DL. I think I have the gist of it but I'm finding that using ctrl+L on a token to "see" what the token sees isn't working properly for me. I have a second browser open, logged in as a player for comparison.

Image 1 logged in as GM, token layer


Image 2 of using ctrl+L on "Kal"


Image 3 is from second browser logged in as "Kal"


Some Details:
Kal - has sight 360
Kyra - emits light 40' 20' 360, all players see light, has sight 360 and her character/token is controlled by All Players.
Elzbeth - emits light 80' 40' 360, has sight (low light vision)
William - has sight 360
I have a light source token by the entrance to the east placed on the Dynamic lighting layer to hide the token from players.
This lighting token is set 90' 45' 180, all players, has sight 360. and the token is set to be controlled by all players.
I have DL w/out LoS, and Update on Drop enabled for map settings.

Clearly something isn't right when using ctrl+L. Is this normal? I thought I was doing something wrong when using ctrl+L. I also noticed that other tokens viewed Elzbeth's low light vision as a light source when using ctrl+L, but the second browser looked correct.

Please send me a join link. I will take a look.

Control L shows you everything you have permission to see, which as GM is everything. Log in as player and you see the plasyer view, if you have not given yourself specific control of everything.

al e., that depends on if he has "Enforce Line of Sight" on or not.

With "Enforce Line of Sight" enabled the GM (using Ctrl+L) will see from every token that has "Has Sight" enabled.
This is because the GM has control over all tokens and Ctrl+L is checking what each token can see.

With "Enforce Line of Sight" not enabled the GM (using Ctrl+L) will only see what the is set to on that token.

My guess is that, based on the images, Vince is not using "Enforce Line of Sight" and thus Ctrl+L is checking the light radius only.

Edit: LOL, I just realized he had posted that he did not have LOS enabled. I missed that.

Vince, after checking your campaign my previous guess is correct. Ctrl+L is working correctly for the settings you have enabled ("Enforce Line of Sight" is not enabled).

Thanks for your time Gauss. So "Force LoS" needs to be enabled for ctrl+L to work... OK. It still seems strange however. I guess it's because the GM has control over everything. If I move Elzbeth(lowlight vision) across the cavern(north), using ctrl+L on Kal now limits his vision to LoS, as expected, but the distances he can see is way off. He can see all the way across the cavern in the other room apparently "seeing" what Elzbeth sees with her lowlight vision. I would still expect his sight to be limited by lack of light across the cavern.

No, Ctrl+L has existed long before "Enforce Line of Sight" was implemented. It does not need to be enabled.

What is happening is that Ctrl+L is checking something different than what you expect when LOS is turned off. The GM having control is not relevant to this use of Ctrl+L.

When you do have LOS turned on then there is a known issue because the GM has control over all tokens. Ctrl+L combined with LOS is checking all tokens that the controller of the selected token can see from. Since the GM has control over all tokens it is basically useless.

Currently, the best way to check what a player can see is to give yourself control over the one token and then switch to player mode. Note: do not give yourself control over all tokens. (Some GMs give themselves control over every token.)

That makes things very clear now. Thanks Gauss

NP