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 Breaking Tokens and Causing Maps to Not Load

1469296132

Edited 1469297245
On any of my pages whenever I have dynamic lighting turned on and I try to move a token the clickable token moves, but the image of it remains in place, so there is an invisible token on one spot and a non clickable image of it on the other. Only happens when dynamic lighting is turned on on that page, problem just started and I'm not sure what is causing it. It also causes every map (even ones without dynamic lighting turned on) to not load properly. Turning off dynamic lighting and refreshing fixes it until dynamic lighting is turned on again. Update: After bringing an archived map with dynamic lighting back and testing on it everything appears to be working normally. Still extremely confused and wish I knew what caused this so I can avoid it in the future.
1469317171
Scott C.
Forum Champion
Sheet Author
API Scripter
Compendium Curator
Just curious, do you have any API scripts installed?
Yeah, here's a list of what I have installed
1469480015
Phil B.
Forum Champion
Sheet Author
When stuff like this happens, it's usually network issues related. Were you haven't other internet problems at the same time? If it's not that it can also be something getting wonky in your cache that's messing up the images on the screen, and the best way to fix this is to clear your browser cache. If this ever happens again, and your network is fine and you've cleared your cache, please do step 4 in the  Technical Issues Wiki and paste the console log into the forum post. Since you said this is now working as intended, we will hope that it was just a 1 time thing, I'm going to go ahead and close this thread. If it's not and you see it happing again, or anything else for that matter, please create a new thread with the console log mentioned above.