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

Freakish Issue with Adv. Fog of War: Ruined Maps

My problem: I cannot interact with my maps, tokens, fog layers, or really anything. If I add tokens to a map, they do not appear unless I refresh the entire page. Nothing I add to the scene appears unless I refresh. This is not currently playable or usable. I have some suspcicions where my problem came up: I think that the adv. fog of war layer has a feisty bug. Here is what my editor looks like: My details: Chrome, v 62.0.3202.94 (latest, I believe) Problem persists on Firefox v 56 as well Windows 10 Home 64 bit Javascript is enabled Malwarebytes (free version) as antivirus, shouldn't affect browser Addons: only one, BlueJeans Meeting (for work) My background to the problem: I recently added the Roll 20 Pro Map Pack from my game's landing page. When I went to one of the maps to look at it, I used the reveal areas tool. The map didn't have fog or adv fog, so the map prompted me: Would you like to use fog? I turned on Adv Fog. Everything broke after that. Things I have tried: I removed the Map Pack and all maps involved (thinking it was bugged) I rolled my game back to yesterday's version I have tried deleting the bad maps, switching to other maps, and creating new maps I cleared my browser cache and temp files These did not solve the problem. Here is currently how I recreate this issue (CONSOLE included in screenshots): First, I load the game fresh, with my last map viewed being a currently active map for my group. This looks fine. I add a new page, looks like the console says something is wrong "Uncaught TypeError: (d20.Campaign.activePage(...).get(...) + (d20.Campaign.activePage(...).get(...) / 2)).toFixed is not a function at m (app.js?1510076098:31)" The zoom is the first thing I tried to fiddle with, it does not zoom correctly (note the hexes are the same size as the previous screenshot) I add a character to the view (note the console logging it happens). I see nothing: I try to reveal the fog, and the reveal fog box does not go away. It also throws more errors of the same kind (50 of them, this time): I switch to a new page, the view is now broken on this page (note the page-toolbar is back to the map I first landed on): If I try to return to the map that I created for this test, you see that it is now absolutely monstrous: I opened the location the error is coming from, in the JS file. It seems to be trying something with the fog of war (but I am not entirely sure what is going on here): This is the original popup that I clicked when it all started: If I refresh the page and zoom out, here is the view (note how dark it looks, with lines running through it): Please advise. Thanks, Frank Braven Games
It appears they are having AFoW issues in general... many people can't even open their games. 
Hi Frank E., I'm sorry it's taken a while to assist with this bug.  Could you give the name of the game or games in which the issue is occurring?  It may help me to create a reproduction path for the issue.  Additionally, I can forcibly disable Advanced Fog of War on all pages in a given campaign to see if that resolves the problem for you as a workaround. Thanks, Jeff
Hi Jeff, Should I send you a link to the game in a PM or do you just need the name?
Jeff, I just ran into this same issue. I created a copy of my game for debug purposes: "Strange Aeons: In Search of Sanity (Debug Copy)" and set the game settings as close as possible to the original. I have tested and verified that I am seeing the same behavior as in my original game. ENVIRONMENT: Browser: Firefox 57.0.1 (64-bit) System: MacBook Pro (Retina, 13-inch, Early 2015) | macOS Sierra Version 10.12.6 (16G1036) Game Settings: I have configured default new page settings to use dynamic lighting and advanced fog of war STEPS TO REPRODUCE: 1. Use the "Create New Page" button on the Pages Toolbar to add a new page to the game. 2. Click on the new, untitled page that was created 3. Select a drawing tool and attempt to draw something on the map 4. Navigate to any other page that has already been created (suggestion: use "The Furnace Rooms", "Briarstone Asylum" is enormous and loads slowly) 5. Reload the page 6. Change the settings of the new untitled page to not use any fog of war or lighting settings 7. Navigate to the new untitled page RESULTS: * The new untitled page background is grey and featureless * Anything drawn on the map "disappears" * After viewing the new untitled page, other pages fail to load * Reloading the page allows other pages to load again as normal * After removing lighting/fog of war, the shapes previously drawn on the canvas are visible but the (red) gridlines are not EXPECTED RESULTS: * The game settings has the gridlines set to a dark red color, these should be appearing over the white (gray with fog of war) background * Drawings should persist on the background * Other pages should load after viewing the new untitled page NOTE: Disabling the advanced fog of war and dynamic lighting in "Game Default Settings" fixes the issue with not being able to see anything when loading the newly created page, but the gridlines still aren't there. I suspect that there may actually be two separate bugs here.
1513733039

Edited 1513733308
Here's a screenshot of the error message: And the raw text: TypeError: (d20.Campaign.activePage(...).get(...) + (d20.Campaign.activePage(...).get(...) / 2)).toFixed is not a function [Learn More] app.js:31:17546 b <a href="https://app.roll20.net/assets/app.js:31:17546" rel="nofollow">https://app.roll20.net/assets/app.js:31:17546</a> d20.canvas_overlay.postProcessing <a href="https://app.roll20.net/assets/app.js:31:30280" rel="nofollow">https://app.roll20.net/assets/app.js:31:30280</a> d20.engine.postProcessing <a href="https://app.roll20.net/assets/app.js:32:21001" rel="nofollow">https://app.roll20.net/assets/app.js:32:21001</a> renderAll <a href="https://app.roll20.net/assets/app.js:27:24822" rel="nofollow">https://app.roll20.net/assets/app.js:27:24822</a> renderAll self-hosted:950:17 d20.engine.renderLoop <a href="https://app.roll20.net/assets/app.js:33:27923" rel="nofollow">https://app.roll20.net/assets/app.js:33:27923</a> Regarding the possibility of there actually being two bugs, I also just found this error message when loading one of my pages where the gridlines were missing: Raw text: TypeError: window.currentPlayer is undefined [Learn More] base.js:3:45 anonymous <a href="https://app.roll20.net/assets/base.js:3:45" rel="nofollow">https://app.roll20.net/assets/base.js:3:45</a> jqote/&lt; <a href="https://app.roll20.net/assets/base.js:1:31844" rel="nofollow">https://app.roll20.net/assets/base.js:1:31844</a> each <a href="https://app.roll20.net/js/jquery.1.8.2.min.js:2:14" rel="nofollow">https://app.roll20.net/js/jquery.1.8.2.min.js:2:14</a>... each <a href="https://app.roll20.net/js/jquery.1.8.2.min.js:2:11" rel="nofollow">https://app.roll20.net/js/jquery.1.8.2.min.js:2:11</a>... jqote <a href="https://app.roll20.net/assets/base.js:1:31773" rel="nofollow">https://app.roll20.net/assets/base.js:1:31773</a> d20.journal.refreshSpeakingAsOptions <a href="https://app.roll20.net/assets/app.js:46:21245" rel="nofollow">https://app.roll20.net/assets/app.js:46:21245</a> d20.journal.refreshJournalList <a href="https://app.roll20.net/assets/app.js:46:14760" rel="nofollow">https://app.roll20.net/assets/app.js:46:14760</a> i/e&lt; <a href="https://app.roll20.net/assets/app.js:46:9137" rel="nofollow">https://app.roll20.net/assets/app.js:46:9137</a> <a href="https://app.roll20.net/assets/app.js:33:27923" rel="nofollow">https://app.roll20.net/assets/app.js:33:27923</a> Edit: phrasing and added the appropriate urls to the "[Learn More]" links in the error messages
To everyone with this issue: We're very sorry that you've been having some trouble with the Advanced Fog of war.&nbsp; We've made a few steps forward, but have still been unable to consistently reproduce this problem on our end.&nbsp; In the spirit of openness, I wanted to personally say that we are definitely still working on getting this solved.&nbsp; If you have anything else that you can add, such as alternate reproduction paths or environment information, whether the problem has changed / resolved with recent site updates, please continue to post in this thread or PM me directly. Thanks, Jeff
Hi Jeff, Thanks for responding. I've stopped using AFoW and I also stopped trying to troubleshoot it a while back. It's good to know you're still trying to resolve this. Something that I wasn't able to verify but I produced after I dug more into the problem: I believe that I had an AFoW actually on my page, but the ID was incorrect for some reason. Is there some process that assigns the AFoW ID? Could that have issues for some reason? How is the ID chosen? It seems that (as I followed): - Performing an operation that interacts with AFoW first requires getting the AFoW element ID - When attempting to getElementById, it did not return an element, so no "opacity" (or otherwise) could be determined - Since it returns empty/undefined, all operations for the AFoW layer obviously break and then all subsequent operations break I can attempt to recreate this again if you want. I may have these details wrong, because it's been a while.