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

[Bug] Dynamic lighting problem

Hi,  I found a bug where the dynamic lighting fails and all information are exposed to the players. I have sent a PM to Riley D. but he must have seen it yet.  Since with this bug players can destroy the games built by GMs I do not want to post in this forum. So, if Riley D. does not reply (my PM has been sent since 26/02/2016) how can I communicate this bug to the Dev Team?
1456746622
Ziechael
Forum Champion
Sheet Author
API Scripter
Hi Konstantinos, please be assured that Riley and the Dev team are very aware of this issue, I myself have fallen afoul of it in times past. Generally the issue is limited to players with slow/poor internet connections and a simple refresh of the VTT will allow their cache to pick up the slack and show the DL. If it is a frequent issue DM's have either places tokens on the GM layer to keep them hidden until all is confirmed loaded correctly or used Fog of War on a page initially with the area around the player tokens revealed so that the players can confirm whether or not the DL has loaded correctly for them... once confirmed the FoW can be removed completely and play can resume as normal. Frustrating, yes, but with the right, honest group, it at least allows for non meta-play to continue. As the problem 'usually' lies with the players connections/machine it is difficult for the Roll20 team to do anything about but since they are wizards of the highest order please follow the tech help steps to ensure there isn't something else at work here, it may also be of benefit to get the players affected to do the same steps too: Could you please carefully work through the first three steps of our guide to Solving Technical Issues ? Step 1: Make sure to use the right browser Please check if these issues persist when using both Chrome and Firefox. Step 2: Ensure that there are no extensions/addons interfering with Roll20 Please disable all add-ons/extensions and anti-virus programs. Step 3: Clear your cache If none of the above succeeds, please thoroughly work through Step 4 . (Don't forget the complete Console Log!) Thank you!
(As Ziechael posted above, please go ahead and follow the standard bug reporting guidelines and get us all that info and we'll do our best to help you and your players out. PMing me is actually more likely to end up with your issue not being handled quickly since my PM inbox gets pretty spammed on here, whereas the standard bug report forum has a lot more eyes on it).
Team, I also am having the same problem, intermittently. It occurs on multiple maps with multiple characters. It seems that once one token can slide through the light line, all the characters can. They think it great fun sliding into illegal areas so that I have to place them back into the legal zone--like picking up kittens escaping from a box that keep jumping out again. Most of the time, the tokens are restricted, but occasionally they can walk through walls. I use the Chrome browser on MacBook Pro OS 10.10 (Yosemite), and have each tokens' Has Sight and Restrictions flags set (explains why it works MOST of the time). I have checked and comply with the 3 steps Ziechel described above in his post.  --Falsoon
Roll20, One other comment that might be relevant. I noticed that a light line broken by even a pixel's width or two now allows tokens through that gap. Previously, the gap had to be close to the token's size for the token to go through. This might make the problem seem more common in that Restrictions can be seen as not working, when actually a gap exists in the light line. In my case, once I found that fact, I made sure my rooms were light-tight, but the tokens can still sometimes act etherally. --Falsoon
Roll20, Here is a good test. If you go to my Combination Castle, at the bottom right of the map is a circular room 19. I used a segmented outer boundary for the light lines, but I used a circle for the inner boundary (it is a circular stairwell). When I Ctrl-L into the room, my token can go INSIDE the circle, and the shadows reflect a SQUARE! I know there are no pixels missing from the circle (drawn with shape tool) but the lower left corner does not respect Restrictions. I will leave that as is for a few days so you can check it out. I have a game Friday so must repair it before then. --Falsoon
@Falsoon Circles don't work, that is a limitation of the tool.  You need to use the polygon/line tool to "simulate a circle".  Not saying there might not be another issue there, but this is one that I know is a limitation. Also, restrict movement is based on a small point on the center of a token, it doesn't matter the size of the token itself, this single point doesn't change.  So yes if you have a small break in the line and the players drag their tokens around through it, then can "squeeze" or move into areas that they shouldn't.  I have learned to overlap my dynamic lighting where I can, or use the poly/line tool with shift to snap to grid whenever possible.
1457027264

Edited 1457027330
Well.. the bug that I found is about printing the page. Whatever the GM does, the player can see the whole map if his token has the "Has sight" option.  Since you posted the other bugs... here goes the one I found :) (Tested with Safari) If the player's token has sight and the player try to print the page then, at the menu for printing where is a page preview thumbnail, one can see the whole map clearly as it gets. No matter what settings are in the dynamic lighting, at the printing menu one an see the whole map crystal clear.  So, I think, the console output and the cache advices are irrelevant. As I can perceive it, it should be something on how the dynamic lighting is handled by the js functions/modules/libs. 
Ok... that is a strange one.  I can confirm that this does happen on Safari on Mac, Firefox on Windows 10.  Strangely it doesn't happen with Chrome on either OS.
1457111006

Edited 1457111030
Hm.. Then I think the devs can narrow it down to the graphics engine of browser cause Safari and Firefox use the same one.