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
This post has been closed. You can still view previous posts, but you can't post any new replies.

Post 7/30 Update: Map and token lag.

Just checked out Roll20 with the new update, and map rendering and token movement are very laggy. I don't have the issues with maps randomly discombobulating themselves, or blowing to pieces, but the lag is very noticeable (for instance, moving a token is not smooth - it hangs for about 0.5 seconds, then jumps to the mouse cursor, then hangs another half a second, etc). OS: Windows 7 Enterprise, 32-bit Browser: Firefox 13.0 Flash: 11.2.202 (not sure if that matters anymore, but there it is) Also...has the select/move tool always shown the 4-way mouse cursor when it hovered over things? I seem to recall it used to just be the normal arrow.
The switching mouse cursor is new. Would you mind testing it out in Chrome for me? Curious if it's your computer or Firefox acting up.
Also, go to "about:support" in your Firefox bar, and about mid-way through there should be a section on Graphics -> Direct2D Enabled? My guess is your Firefox is falling back to a software renderer for some reason and that's causing slowdown...
Sure, no problem. I used Chrome 20.0.1132.57 m. Here's what happened: 1. Accessed the roll20 site by going to <a href="http://www.roll20.net" rel="nofollow">www.roll20.net</a>. 2. When I signed in, I was taken to a app.roll20.net/sessions/create, the visible content of which was: /campaigns/ 3. Hit refresh, was prompted that it was a form resubmission, and continued - the campaigns page loaded normally after that. 4. Selected my campaign "Barbarians of the Tabletop" and it loaded somewhat slowly, and at first displayed a non-fully-rendered image (only the left, maybe, 2 inches of map was showing). Moving the mouse wheel caused it to rerender, and it showed the map I expected. 5. When moving tokens and maps, it was a bit faster in chrome, but still noticeably not smooth - it seemed almost flickery. 6. I've attached a screenshot of the mouse cursor, and the token when I select it (it has a blue border with control handles, which I also don't remember). The upshot is that the cursor behavior happens in both Firefox and Chrome. I don't have any other browsers available to try it with (aside from IE, which pitches a 405 Method Not Allowed error when I sign in, but then, IE doesn't work with Roll20 anyway). Hope this helps!
Sorry, missed your comment about the "about:support" page. Yeah, Direct2D is blocked for this computer (it's a work machine, so it's not my primary computer or anything) so you are probably right on that count. Don't know if that has anything to do with the mouse, though.
The mouse is "working as intended" -- I take it you don't like it? It's supposed to help indicate when you're over somethign you can move (to help with user friendliness)...
Also I'll look into that redirect bug -- odd.
Ah, okay. It's not that I don't like it, necessarily, I just didn't recall it doing that, and I'm used to a different VTT where you have to select a token before you could do anything to it (hovering over it did nothing - well, it shows a popup of info if it's configured, but the cursor just remains a standard arrow cursor). Really, it's not a big deal. I think I just see that particular mouse cursor as more of a "move an object, not a token" cursor (i.e., for a not-entirely-logical-reason, that's the cursor I'd expect if I was moving a map tile into place, but not a token. Go figure :). Maybe it's just that of all the cursors I see the mouse change to every day, that's not a really common one?) If it's working as intended, then no problem.
Oh, btw - this one can be closed/resolved. It was the lack of hardware rendering that caused the choppiness.
Thanks for the update Chris!