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

Exploit: Rapid Mouse-wheel Scrolling temporarily removes Dynamic Lighting

Hey! This is an odd "exploit" one of my Players alerted me too last Sunday while the party was exploring a dungeon map using Dynamic Lighting. The player (using Firefox/Windows7) would rapidly use his mouse-wheel to scroll vertically, the Dynamic Lighting on the map would remove temporarily allowing him to see the full map for maybe 1-2 seconds before the lighting re-appeared. I regrettably don't have screen shots of this and hope to try and replicate this tonight but my Players were able to identify tokens that were on my screen, still on parts of the map they shouldn't have been able to see after testing this process out on their own. I've fixed this by placing tokens on the GM layer (which I'm seeing more posts saying this is a best-practice) however this slows down "reveals" using light to a degree as I need to then quickly move these tokens back to the Token I thought I'd make a post to see if anyone else is experiencing this.
1358920781
Gauss
Forum Champion
For me, this occurs at high zoom settings on a system which renders a bit slowly. When the system is unable to draw fast enough it switches to a "delayed render" mode. This mode can result in players seeing things they shouldn't. I suggest using the GM layer and Fog of War in addition to the Dynamic Lighting. The Fog of War will prevent players from seeing sections of the map they shouldn't (which is advisable anyhow since they can just move tokens into other sections and see them) and the GM Layer will prevent them from seeing NPCs until the proper time. As a GM it doesn't slow me down much to do this. In the meantime I will forward this to the Devs. Perhaps there is an order of rendering problem. - Gauss