With Dynamic Lighting, the Ctrl+L GM control option was introduced to quickly be able to see what the player would see based on lighting effects. It would appear that there are some bugs with this that produce very distinct differences between the Ctrl+L option and actually logging in as a player controlling the token. Bug 1. With Ctrl+L, the "player permissions" for light sources are used from the GM "player" rather than from the player controlling the token. This means that from the Ctrl+L view of a token which is controlled by only one player, all light sources can be seen regardless of who actually has permissions to see the light source. This doesn't match the actual player view, which correctly limits the light visibilities to those visible to all players and those the player has permissions for. In the following image, the light has been setup to have the "all players see light" option unchecked, the page properties are set with "enforce line of sight" checked, and the player token is in an enclosed dark room with only the one light source. From the Ctrl+L view, this is what is seen: This was originally reported as a bug with the dynamic lighting mechanism, but after changing to player view manually, it's evident that the player cannot actually see that light source since they don't control it. Bug 2. Fog of war with light sources operates differently for Ctrl+L versus actual player view. If I put a light source visible to all players in a closed room with fog of war over it, the Ctrl+L view shows the following: The player view however shows this: I would assume the Ctrl+L view is supposed to replicate the player view exactly for the purposes of light effects, but it seems there are some permissions issues with it. At a guess I'd say it's probably an issue with whatever API is used to determine visibility not correctly filtering out the GM as the permissions source on a token when in Ctrl+L view, while in player view the GM isn't listed as a permissions source and the correct view is seen.
