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 .
×
×

Cookie Preferences

We use Cookies to help personalize and improve Roll20. For more information on our use of non-essential Cookies, visit our Privacy Policy here.
May your rolls be merry + bright! 🎄
Create a free account

Google Chrome Vision Bug

  1. Community Forums
  2. Bug Reports & Technical Issues
  3. Google Chrome Vision Bug
1472786125
Mike F.
Permalink for 3911102 Quote
In Google Chrome, under advanced settings, "Use hardware acceleration when available", if checked, grants full vision to the player.  In our campaign, when disabled again, desired vision returned.  The actual setting is in the attached picture.
1472861250
Gid
Roll20 Team
Permalink for 3914860 Quote
Hello Mike, I'm trying to replicate the same issue you've discovered in Chrome. After toggling hardware acceleration off and on several times, I still had my playspace obscured. Was this something that all of your Chrome players were able to see your campaign when they toggled on hardware acceleration? And were they able to see through Fog of War, items on the GM layer, or through dynamic lighting?  If it was just one particular player, I'll need them to follow these steps from the  Solving Technical Issues wiki page: 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!)
1472863677

Edited 1472864078
Scott C.
Forum Champion
Sheet Author
API Scripter
Compendium Curator
Permalink for 3915024 Quote
Hey,&nbsp;Kristin This is an issue that has plagued DL for a while. There are several bug reports on it (which now that we have you for a dedicated QA dev should be helpful). It appears to also be caused by javascript being disabled/crashing/out of date (not sure which of those). From personal experience, I can say that it is one of those bugs that will appear one day and be gone the next as I have had players be able to see DL as it was supposed to be seen one map and then have their browsers completely ignore it the next map. Relevant posts (not all of them have a great deal of detail, and I'm sure this isn't all of them and I'm sure you've seen at least some of these before): <a href="https://app.roll20.net/forum/post/3896609/slug%7D" rel="nofollow">https://app.roll20.net/forum/post/3896609/slug%7D</a> <a href="https://app.roll20.net/forum/post/3560344/slug%7D" rel="nofollow">https://app.roll20.net/forum/post/3560344/slug%7D</a> <a href="https://app.roll20.net/forum/post/709062/slug%7D" rel="nofollow">https://app.roll20.net/forum/post/709062/slug%7D</a> There was another one where we discussed the hardware acceleration and javascript, but I can't find it now. I could swear that for that person, turning hardware acceleration on made it work for them. -Scott
You must Login to your Roll20 Account to post a reply.