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

Another Dynamic Light Failure: Whole map revealed to player again

So I recently posted about a Dynamic Light Failure which (among other errors) ruined an entire session.  In short, some players could not see anything while one could see the whole map.  I was given some advice about browsers and extensions.  The player switched browser and so far, seems to be ok for that player. However, I was playing on Wednesday with two of my players, both started the game with DL working just fine.  Then all of a sudden the entire map popped into view for one of the players (not the same player as before).  She was using Chrome.  She switched to Firefox and all was good.  This cannot be explained by simple browser issues as it started off working and then half-way through the session it failed.  I'm currently running the purchased campaign The Sunless Citadel.  This is most frustrating.  GMs need to be able to rely on the system not revealing secret parts to the players.  Thankfully this one player was honest. I would be grateful for a permanent solution to this issue please.  Apologies for the agitated tone but its very frustrating to purchase content that is not working properly.
1574620888

Edited 1574620919
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
It sounds like possibly a failure of the browser to allow JavaScript. That would kill DL (and some other stuff, also on other sites, but we're focusing on DL). Have her click on the site settings (the lock icon next to the web address) and chooses "settings". Make sure JavaScript is specifically allowed on Roll20.
Hi Keith, thank you for your response.  Couple of points: if it were a browser issue, why would the problem arise half way through the game session. More importantly, this is kind of a problem as it means the Roll20 platform gives a work around for info that should be secret to GMs.  It means even if I set everything up properly my end, I cannot be confident that my game (which I purchased) will run properly?
Hi&nbsp;Allan -&nbsp; Would you mind providing me a link to the game in question? I'll take a look at it and see if anything pops out off the bat. Also, if they ever encounter this issue again, would you mind asking them to try and provide a console log from the time at which the issue occurs, please? Directions for providing a console log in Chrome can be seen here: <a href="https://support.google.com/docs/thread/1873663?hl=en" rel="nofollow">https://support.google.com/docs/thread/1873663?hl=en</a> . The directions for Firefox will be similar, but will use the Firefox interface, which is described here: <a href="https://developer.mozilla.org/en-US/docs/Tools/Web_Console" rel="nofollow">https://developer.mozilla.org/en-US/docs/Tools/Web_Console</a> .
Thanks Nicholas. &nbsp;Much appreciated. &nbsp;I will do just that. &nbsp;Thanks again.
Link sent. &nbsp;Thanks again
Hi&nbsp;Allan -&nbsp; After further inspection, nothing appears to be wrong with your game or settings. As keithcurtis mentioned, this might be caused by some sort of browser error, most likely related to JavaScript. To confirm, do you know if your players have any extensions or addons installed for both of those browsers? Maybe like an adblocker or something? Also, can you clarify, what were they doing with their token when the issue popped up? Were they simply moving it on the map and then it occurred? Ultimately, for us to best diagnose and troubleshoot what's going on, we would definitely want to get a console log from the player that experiences this, if they can get it - might be kind of difficult in this situation. Any additional information you can provide is greatly appreciated!
Thanks Nicholas. &nbsp;That’s very much appreciated. I had the player use the same browser as caused the issue for a game on Wednesday so we could grab a console log but, Sod’s law, it’s didn’t repeat the issue. &nbsp;We’ll keep going and if it happens again, I’ll get you the log. &nbsp; Thanks again for your help.