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 .
×
Create a free account
This post has been closed. You can still view previous posts, but you can't post any new replies.

Dynamic Lighting and Advanced Fog of war Problems

1554391458

Edited 1554391524
Hi folks. This is my first time here...so if i am in the wrong place for this pls tell me :) Otherwise let's get started. I DM-ed for a long time now and allready used the dym light and the advanced fog very efficiently. Now me and my party had a long break (5 months) and now we returned only for me to find out that this awesome feature just doesn't work (the same way as before) anymore. So i am looking for answers / patchnotes / help. So what is my problem / my settings:  1) Torches don't work. Players got sight (and sometimes a lightradius) but they just can't see the torch even when in their light. 2) "ctrl-L" just does not show the right thing. We had a session where i thought i had figured it out and tested it with "ctrl-L" but when they joined they could only see their own light. 3) To emit any light, i had to create a character (NPC, just controlled by me) and set the torches to this character. If they are "no character / general token" it just does nothing. So what did i try: 3 torches with 12 / 6 light. One without "all players see light" and "has sight", one with "has sight" and the last with both. I copied them and made the 2nd three to the NPC player tokens. Now the first three don't emit light at all and don't see anything. The second three ALL see their light. Why?  Map setting is advanced fog and dyn light on, nothing else
1554392803
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
There are significant bugs going on right now regarding DL and it's interaction with AFoW. There is a thread discussing the issues here . Ctl-L does not currently provide an accurate view. I can only offer two workarounds until these are fixed. Use a dummy account to check player sight during setup instead of Ctrl-L, and turn off AFoW if you are using DL. :(
1554392804

Edited 1554392876
Brian C.
Pro
Marketplace Creator
Compendium Curator
You want to be in the&nbsp; <a href="https://app.roll20.net/forum/post/7160288/animations-and-afow-offical-feedback-thread" rel="nofollow">https://app.roll20.net/forum/post/7160288/animations-and-afow-offical-feedback-thread</a> &nbsp;thread. The short answer is the devs tried to make AFoW more efficient back in January, and many of the patches have made things worse. Turning off AFoW will make DL work for the most part. Ctrl+L is fairly broken at the moment as well. A test account running in a different browser will give you a true representation of what a player would see. As for your questions. AFoW is blocking sight and messing with light sources. With both AFoW and DL on, if you look at a torch as a GM and move it around, you should be able to see the DL area of light move, but it is actually darker &nbsp;than the rest of the map where the light does not touch. Currently, a player can only see light from tokens they control. Turning off AFoW fixes this. The only way to truly see what a player can see right now is having a test account joined to the game and running that from a different browser (i.e. Firefox if you normally use Chrome. This is more useful when setting things up and not quite as useful when you are actually trying to run a game. The only way to get tokens to see other light sources at the moment is to turn off AFoW. EDIT: Ninja'd by the amazing keithcurtis. &lt;whisper&gt;He's everywhere.&lt;/whisper&gt; :)
Wow okay thanks for the responses...that really really sucks...the feature was fine how it worked :/ One of the main reasons why i got the monthly sub...
André L. said: One of the main reasons why i got the monthly sub... Same here. Hope this has priority to get fixed.
As mentioned above, there's an existing thread for this known issue.&nbsp; I will be closing this one now.