Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
May your rolls be chill this holiday season!
Create a free account
This post has been closed. You can still view previous posts, but you can't post any new replies.

CTRL + L showing all token vision

I am having an issue when I use ctrl+L to view a specific token's vision, it shows all token vision.  See the screenshot below of the settings I am using.  I set everyone to a 5 ft range so I could show it easier. It's almost as if the tokens are all set to "all players see light"  but that is not the case. Any ideas?
1556739737
Brian C.
Pro
Marketplace Creator
Compendium Curator
My guess is you are running into Known Issue 5 in this thread.&nbsp; <a href="https://app.roll20.net/forum/post/7368015/advanced-fog-of-war-feedback-thread-2-dot-0/?pagenum=1" rel="nofollow">https://app.roll20.net/forum/post/7368015/advanced-fog-of-war-feedback-thread-2-dot-0/?pagenum=1</a>
1556739778
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
This is issue #5 from this thread . You can track the progress there: CTRL-L doesn't work properly for GMs; If Enforce Line of Sight is off, one token will not see the other token's light source, even if they are unobstructed. This only affects GMs, however; the player can see the other token. GMs using CTRL-L will see all tokens, even if they do not have "All Players See Light" enabled, and will also see the full range of vision, blocked only by Dynamic Lighting (see Known Issue directly above this one.)
1556739792
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Sniped by Brian!
1556739830
Brian C.
Pro
Marketplace Creator
Compendium Curator
keithcurtis said: Sniped by Brian! There's a first time for everything. ;)
Hello Trisden, As Brian C. has stated, this is a known issue. You can follow that thread for updates. As such, I am going to ahead and close this thread.&nbsp; Thanks!