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] - Random image on token Layer can't be selected or removed

I was checking over my maps today in prep for tonight's session when I noticed that i had a strange fireball image on my GM layer. I could not select it and if I looked at the map with just the right horizontal and verticals, it disappeared but would reappear on the next scroll. Although I couldn't select it specifically, if I did a ctrl+a on the GM layer, it was grouped with all of the other objects and could be moved around. I moved those to the token layer and one by one, moved things back to GM. Now this huge fireball is still on my token layer but I cannot select it or otherwise modify. I have a feeling when I was looking to put some other similar images on the field I may have put this object down but moved on to another when I didn't see it render (happens every now and then). Today was the first I've seen of this object on this map. Also, there are tokens below this fireball that can be moved to the front or back so this image is being treated as a layered object for sure, but without my control.
Aaaaand, it's gone! As soon as I refreshed the browser, the image disappeared. Based on the object and my screenshot, I think what happend is that the original image of this object was being rendered instead of the single cell, tinted version that should be underneath the guy in the upper left of my image. I probably couldn't select it since it was still thinking of it as existing in the boundaries of the 1x1 cell. It was just the graphic that wasn't being rendered properly. Problem solved, but still and odd one-off worth reporting.
It's always good to have a report. Please let us know if it happens again!