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

Maps not visible to players

Have Sunless Citadel module.  Plays can not see maps.  The dynamic lighting is OFF.  Going to the reveal buttons nothing happens.  This is the only module this is happening in.  
1768412623

Edited 1768417092
Here's my Dynamic Lighting Troubleshooting checklist. You've said that DL is off, but the 'My players can't see' still has several things to check that aren't handled by the DL tool. Troubleshooting General: ⁠The game creator needs to have a Roll20 Plus or Pro account to use Dynamic Lighting. ⁠Make sure you are using Chrome or Firefox. Do not use the Freehand tool to draw Dynamic Lighting lines. Only use the Polygon tool, and make sure that you don't have any lines that create 'sharp' corners. This is the cause of unexplained/invisible lines about 99% of the time. You should use a ' Dummy Account ' in order to see changes live/instantaneously when you make them as GM. There are other benefits as well (streaming, testing macros and other tricks, resetting the game URL). ⁠ Ctrl-L does not give you a player's view from a token. It shows you the token's 'Line of Sight' as GM. You will see everything on the GM layer, but players will not see anything on the GM layer from the same token. ⁠ 'Rejoin as player' is difficult because it requires logging back and forth into the game. A Dummy Account is free and can be readily toggled between two browser windows or tabs. ⁠ ⁠A player may control several tokens, and may see more or less than the GM sees when using Ctrl-L or 'Rejoin as player'. Do not use colored or tinted lighting effects. Colored light is currently bugged due to how those lighting effects are rendered. ( Here's a good example of Explorer Mode , which is probably similar to how colored light works.) If you want to have a colored/tinted area, use an invisible token with a colored aura instead . Animated .webm tokens were previously bugged and may not not work correctly. Check other page settings, such as 'Restrict Movement' and make sure you are not using Legacy Dynamic Lighting.  Clear your browser cache and the game chat archive. If you have a Pro subscription, you can install the DL Tool script to troubleshoot vision problems. My players can't see: Token and light source need to be on the correct layers. Token must have vision enabled. Token must be 'controlled' by the player who is checking vision. ⁠There needs to be a light source. ⁠ Tokens always emit light from the center of the token as a circle that is some small percentage of the image size. If you set the map image as a light source, you'll get some funky behavior. ⁠Ensure that a token's vision is not blocked by Dynamic Lighting lines. Make sure you don't have a Permanent Darkness layer on. ⁠Make sure you don't have Explorable Darkness blocking vision. ⁠Make sure the view is centered on a token that has vision enabled and a light source. ⁠Make sure you/your players are on the correct page. Double check that they have not been split from the Party ribbon. ⁠If a player cannot see, move their token. There was a bug with UDL that prevented player vision from 'activating' until after one of their tokens is moved on a page. My players see too much: Make sure you don't have 'Daylight' turned on for the page. Walls need to be placed on the 'walls' (lighting) layer. ⁠ ⁠If a token has "line of sight" to an area illuminated by a light source, then they will be able to see that area. The only thing that blocks line of sight are Dynamic Lighting lines (walls). ⁠ Tokens cannot block light. ⁠ Permanent Darkness covers an area, but does not prevent light from passing through. ⁠Explorable Darkness is saved for each player. So if a player has control of a token, they will see all of their 'explored area' in greyscale. ⁠Look on the 'walls'/lighting layer for any unexpected light sources. They will show up as small rectangles there. ⁠Confirm which tokens the player controls. Try moving all tokens to the GM layer temporarily and moving individual tokens back to the Objects layer one by one. ⁠Page 'Cell Width' settings can have an affect on a token's vision, especially if the 'light multiplier' is set to something other than 100%. Switch the Cell Width to '1' and see what happens. Token vision isn’t correct when pulled out of the journal: Make sure to set up a token’s vision how you want it to be, and have the **very last step** be to save it as the default for that character sheet. Any changes made after saving as the default token will not be saved as the default unless the default token is saved again. This is intentional to allow for temporary changes. ⁠Make sure you do not have any duplicate character sheet names. ⁠Also check the Journal Archive. ⁠After pulling out the token, check which character sheet it is linked to. ⁠A character’s default token can be linked to a different character sheet.
1768415585

Edited 1768415691
Gold
Forum Champion
tebatoz said: Have Sunless Citadel module.  Plays can not see maps.  The dynamic lighting is OFF.  Going to the reveal buttons nothing happens.  This is the only module this is happening in.   Check to make sure that in the Pages Menu/Toolbar, the Players Ribbon is on the Page that you want / expect, the same page you're looking as a GM.  Sometimes the issue for this is, if they're parked on a different page.  Jarren  said: Here's my Dynamic Lighting Troubleshooting checklist. They said DL is OFF
1768417185

Edited 1768417351
Ah yep I saw that and meant to add a comment about the 'My players can't see' still having good info for other reasons besides the DL tool and totally forgot to add it when I was cutting and pasting. :)  Thanks for catching that - I've edited above to add the comment now. The rest of it might be helpful for anyone who stumbles upon this thread later on.