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

Processor Ripping on Gifs

I currently run a game every Thursday @7-11PM EST. I have 5 players and myself. I purchased a Gif package for weather which is awesome when I can use it. But what I have found is that I need several to fill a map or even a couple. When I do this the you duke hits the fan! Its not just me other players say its frozen or have issues. I don't have the best newest age machine but it is a 6 Core 3.5ghz processor. I play high end games on high graphics with no issues. I am having freeze issues and the web base design is slow. Sometime rolls take 10 seconds to come in or longer for some players. The gifs though offer me the most grief. I use firefox and maybe this is some of it. Also can someone answer me if I am acting as the server for the others or are we actually log into a Roll20 server? Does anyone have ideas or is Roll20 working on a real program instead of Java web based stuff? There is a big market for this and I think this would be a good step. Fantasy Grounds does not offer gif support and with animations now it make online play that much better. I have used roll20 since 2014 and plan to continue just want smoother game play! Roll On!
Hi Jake, We're sorry to hear that you are experiencing issues with this. Please carefully work through to the first three steps of our guide to Solving Technical Issues: Step 1: Make sure to use the right browser            - Please check if these issues persist when using both Chrome and Firefox. Step 2: Ensure that there are no extensions/addons interfering with Roll20            - Please disable all add-ons/extensions. Step 3: Clear your cache If none of the above succeeds, thoroughly work through Step 4 . (Don't forget the complete Console Log!) Thank you!