Teller said: Some general performance feedback after testing one of my games: I had hoped to be able to use Roll20 again rather than another VTT for Dungeon of the Mad Mage, but it seems even with Jumpgate Roll20 isn't able to handle running it when using Explorable Fog of War. My maps are bigger than what old Roll20 advertises it can handle, but it's nothing other VTTs can't easily handle these days, so I figure Jumpgate should be able to handle it now. In this case, the page is 114x123 cells, or 8000x8600 pixels. The map image itself is 3.31MB, though as you will see below it seems its the fog of war that's the problem. My experience testing this map (on Chrome) in Jumpgate is as follows: a) Map loads fine, doesn't even take that long! Great so far. b) Works perfectly in the GM view. I can move around creature tokens (who don't have vision enabled), create new walls, doors, etc without performance issues. Big improvement over Old Roll20, and equivalent to other VTTs using the same map. c) The problem begins the moment I begin testing with one token with vision. I reset the explorable fog of war and place the token in the first room. I use CTRL-L to look through the token's eyes, then begin exploring the map, revealing the contents. A little big of lag when I move, perhaps 500ms of lag. Lag gets worse the more I explore. By the time I reach the third room, the entire browser window goes completely black, then after a second or so has passed, the browser returns and is once again usable, but the Map portion of Roll20 is black, leaving the only interactable items the chat window, the sidebar and the token settings (if token was selected before Roll20 crashed). The only way to see the map again is to reload the page. I assume the Roll20 canvas crashed. Okay thanks for the feedback, we'll investigate that CTRL+L explore slowdown...can you let us know what browser you're using and also is there a link to the game and the page in that game where this happened we can use as a test case?
