Difference between revisions of "Optimizing Roll20 Performance"
From Roll20 Wiki
Kristin C. (Talk | contribs) m (removing hangouts) |
(→Mobile) |
||
| (29 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{revdate}}{{HCbox| {{hc|articles/360041544654-Optimizing-Roll20-Performance Here}} }} | |
| − | |||
| − | + | As far as most gaming-related applications go, Roll20 has very low network and graphical performance requirements. The vast majority of our users never need to worry about any of the following. However, if you(as [[GM]]), or one of your [[players]], has a very slow Internet connection or a very old computer, these tips may help you have a smoother time playing. | |
| − | + | Roll20 is a web-based application, and as such there are two primary performance considerations: the speed of the network connection, and the speed of the graphics rendering on the client's computer. | |
| − | + | '''Note''': Your own individual results may (and probably will) vary from other people playing in your game. If you're the [[GM]] designing the Roll20 Game, you'll want to keep the worst performing client (which may not be you) in mind. Just because a 500 unit by 500 unit map scrolls smoothly on your computer doesn't mean it will work well for your player with a 4-year-old machine. | |
| − | + | '''TL;DR''': Slow network connection? Your biggest hit is going to come in the video chat department. Try switching your game to broadcast audio-only. Have a [[player]] with a really old computer? Try limiting the number of objects on-screen. | |
| − | |||
| − | + | == Graphics Rendering == | |
| − | ' | + | The graphics rendering performance of your computer is determined by several things, including having an up-to-date browser, your CPU speed, amount of available system memory, and your graphics card. While you certainly don't need a high-end gaming PC to use Roll20, playing on an underpowered netbook computer may cause you to experience jerky or unresponsive performance. For best results, consider using a mid-range computer (one built in the last 3 or 4 years should be more than sufficient, and old computers may be fine as well) with a dedicated graphics card and a screen resolution of at least 1280x1024. |
| − | + | The graphics rendering of your computer directly affects how quickly things can be drawn on your screen as the scene changes. So when a [[token]] is moved or added, or you [[zoom]], or [[Select and Pan Tool|scroll/pan]] around the map, the screen is being constantly redrawn. The better your graphics rendering performance, the smoother those operations will "feel". | |
| − | + | '''{{Pro}} users:''' Creating a [[Library Campaign]] for storing unused maps & characters for large campaigns is a good idea, so you can use the [[Transmogrifier]] to retrive content to the active game campaign from your Library Campaign. | |
| − | + | ===Optimize Campaign=== | |
| − | + | * '''Figure out how large your campaign is: {{fpl|10675897/ Campaign Survey}}''' - helps you inventory the size of your campaign, by listing how many pages/characters/handouts/graphics/etc it has, how often each are used, etc. | |
| − | + | ||
A few tips for getting the most out of Roll20 with a low-performance PC (sorted by "most likely to help" to "least likely"): | A few tips for getting the most out of Roll20 with a low-performance PC (sorted by "most likely to help" to "least likely"): | ||
| − | * Limit the number of | + | * '''Limit the number of PC and NPC {{Journal}} Entries in each game.''' A vast majority of users that report issues have games that contain entries for several hundreds or thousands of [[Characters#Characters|Characters]] and Creatures. |
| − | * Keep map sizes small. (The default size of 20x20 is a good bet.) Divide | + | ** (fairly certain) Having a large number of [[Handouts]] makes a neglect-able difference, it's the large number of [[character sheets]] that slows down Roll20. |
| − | * Turn off the grid and/or | + | * '''Limit the number of images that you use.''' For example, try to use only a single image on the Map [[layer]], instead of a large number of map tiles, furniture, etc. Instead, create the map in an external program and then import it as one JPG or PNG file. The fewer objects that Roll20 has to render individually, the better your performance will be. |
| − | * Limit your use of the | + | * '''Keep map sizes small.''' (The default size of 20x20 is a good bet.) Divide larger maps encounters across several pages if need be. |
| + | * '''Turn off [[Dynamic Lighting]]'''. Larger maps takes a larger performance hit than smaller ones. Applies both for [[LDL]] and [[UDL]] | ||
| + | ** '''reduce number of light sources | ||
| + | ** '''reduce number of [[tokens]] that have vision''' | ||
| + | *** While players need to see, NPCs managed by the GM seldom have use for vision as the GM sees the whole map and can somewhat judge if individual NPCs have Line of Sight or not. | ||
| + | ** '''reduce amount of DL lines''' | ||
| + | *** if you have many shorter segments draw on the map, they might take more processing than fewer, but larger segments covering the same area | ||
| + | * '''Turn off the grid and/or [[Fog of War]] mechanics''' -- both of these require extra graphics processing on each new frame draw to use, slowing down your computer. | ||
| + | * Limit your use of the [[Drawing Tools]] | ||
| + | * {{Pro}} users can move unused content to a [[Library Campaign]] with the [[Transmogrifier]], and later copy things back if those things are again needed. | ||
| − | + | '''Note:''' '''Archiving characters/handouts/maps does not improve performance,''' only hides them from your direct access, and don't improve game performance''' | |
| − | + | =Browser= | |
| + | {{main|Browser}} | ||
| + | '''Roll20 officially only supports the [[Browser#Firefox|Firefox]] & [[Browser#Chrome|Google Chrome]] browsers''', so if you encounter a problem using other browsers, it's recommended to switch to either of these. And no, using any Chromium-based browser like ''Microsoft Edge'' is not the same thing as using Chrome. Roll20 often works well on other browsers, but your mileage may vary. | ||
| − | + | There is no consensus on which browser works best for Roll20, as it seems to vary based on things like what operating system you use(Windows/Mac/Linux), your hardware(physical computer), your ISP, what [[Browser#Plugins|browser plugins]] you use, and even what version of the browser you have. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | Some have claimed Chrome is faster, others swear by Firefox. It can be a good idea to try out the other (Firefox/Chrome) in case things are more smooth with it. | |
| + | It's possible some [[Stylus#Stylus|Stylus]]-scripts can hide or adjust how roll20 looks, in a way that improves performance, but not guaranteed. | ||
| + | |||
| + | == Chrome == | ||
| + | {{cleanup|section}} | ||
Chrome has adjustable flags that may improve performance on some systems. However please note that these are '''advanced settings''' and in certain cases '''can cause degradation or unexpected behaviors'''. To view the Flags section browse to chrome://flags/ in the address field. | Chrome has adjustable flags that may improve performance on some systems. However please note that these are '''advanced settings''' and in certain cases '''can cause degradation or unexpected behaviors'''. To view the Flags section browse to chrome://flags/ in the address field. | ||
| Line 54: | Line 61: | ||
* '''GPU compositing on all pages''': Force GPU compositing on all pages, not just those with GPU features. | * '''GPU compositing on all pages''': Force GPU compositing on all pages, not just those with GPU features. | ||
| + | ==Firefox== | ||
| + | {{main|Browser#Firefox|Firefox}} | ||
| + | * '''turning off "form autofill"''' {{dot}} Sometimes Firefox mistakes Roll20 [[CS|character sheets]] for web form to be filled out, and then processes all the suggestions it can figure out for each field, for each character sheet. | ||
| + | * '''turn on [https://support.mozilla.org/en-US/kb/performance-settings Performance Settings]''' {{dot}} turning on hardware acceleration ensures your firefox uses as much of your computer's processing power as possible | ||
| + | |||
| + | = Network Connection = | ||
| + | {{cleanup|section}} | ||
| + | Network connection refers to two things: the amount of information your connection can carry at once ("bandwidth") and the speed at which it can make a round-trip to the Roll20 servers ("latency"). | ||
| + | |||
| + | The virtual tabletop itself is very lightweight from a bandwidth perspective. Common actions such as [[text chat|sending a chat message]] or moving a [[token]] require very little data. In fact, you and your players will spend much more time downloading image files for tokens and maps included in the game, than you will due to performing actions in the interface. For example, you would need to move 1,000 tokens at the same time to generate as much data as it takes to download one small 7 KB token image. This means that even if you have a "slow" connection (e.g. 768 Kb/s, a common low-end DSL speed), your use of the Roll20 tabletop should not be very affected. A slow bandwidth will mostly cause you to have a long initial load time, and you may see images loading in slowly if your GM adds more throughout the game. | ||
| + | |||
| + | Latency, on the other hand, determines how quickly you'll receive changes during gameplay. If you have a very unreliable connection (such as via a 3G cellular signal or satellite Internet service), you may experience high latency. Roll20 is designed to be fairly fault-tolerant, so you'll still be able to participate, but you may experience delays of several seconds between someone moving a token piece and it appearing to move on your screen. | ||
| + | |||
| + | ==Video Chat== | ||
| + | {{main|Video Chat}} | ||
| + | |||
| + | |||
| + | By far, the part of Roll20 most-affected by your network connection is the integrated voice and video chat. It is recommended that you have at least 250 Kb/s of downstream bandwidth for each member of your group, as well as at least 250 Kb/s of upload bandwidth for broadcasting a video stream from your computer to the group. High latency will also affect your video chat performance, causing there to be delays or even dropped/skipped frames (resulting in "jerky" video). | ||
| + | |||
| + | If you are using the built-in Roll20 video chat and it's not working well for you, and especially if you are located outside of the United States, you could consider using another voice/video service. Many use [https://discordapp.com/ Discord] for voice/video, instead of Roll20's built-in options. | ||
| + | |||
| + | Using a separate service for voice, while using Roll20 for the tabletop and video only, might make for a more stable Roll20 experience. That way, if your video/voice service or Roll20 have issues, you have the other one to rely on. If Discord is acting up, you can then switch to use Roll20 again for voice. | ||
| + | |||
| + | = Common Issues = | ||
| + | Below are a few common performance issues seen by Roll20 users, and their cause: | ||
| + | |||
| + | * '''The map and [[sidebar]] are compressed into the top of my browser.''' This is usually caused by an extension or plugin. Try deactivating your extensions and plugins until you find the one causing the problem. | ||
| + | * '''Jerky/slow scrolling/panning/zooming.''' This is caused by low graphical rendering performance. See the section above for tips on improving graphic performance. | ||
| + | * '''[[Fog of War]] and/or grid completely disappears on the map.''' This is caused by your graphics card running out of video memory. You'll need to use smaller maps. | ||
| + | * '''When scrolling/panning, the grid or fog of war "lags behind", revealing parts of the map.''' This is caused by low graphical rendering performance. Your best bet is to use a smaller map, or not use the fog of war feature. | ||
| + | * '''Jerky video chat, skipping, dropped frames, "laggy".''' Could be caused by either network or graphical performance issues. Try using voice-only chat, using a dedicated video chat service, or disabling Roll20 video/voice chat entirely. | ||
| + | * '''There is a delay between when I see a text chat message appear and when someone says something about it in the video chat.''' There is a standard delay of a second or two in the video chat -- a lot of data has to make a trip to a server and then to your other group members, and the connection speeds and latency of the hops in between slow things down. If you're seeing a larger delay than that, it's most likely a latency issue. | ||
| + | |||
| + | =Mobile= | ||
| + | Offloading some tasks from the computer to a tablet or smartphone, such as character sheets with the [[Mobile]] app, could help your computer keep up. | ||
| + | |||
| + | = Additional Suggestions from the Forums = | ||
| + | Optimization Tips/Suggestions copied from the forum post: {{fpl|10257507/ Lag}} | ||
| + | |||
| + | # Uninstall the very questionable third party tools and use the scripts made here in their place. | ||
| + | # If you have [[Door Knocker]] API installed, make sure any other non door maps are not accidentally drawn in the colors for doorknockers color codes. If they are, that’s a TON of doorknocker api auras drawn on the page and will lag you to all hell. ('''Additional Comment:''' If you are careful with your DL line colors, Doorknocker shouldn't be an issue. I use it all the time.) | ||
| + | # Health auras looks so cool, but the more [[Token#Auras|auras]] on tokens, the “laggier” the game gets. Keep an eye on various API's cause some use invisible auras like doorknocker. | ||
| + | # Turn off [[Dynamic Lighting]] completely. If you use Dynamic Lighting, do not use Freehand mode for your barriers (lines and shapes are much faster to load). | ||
| + | # If you are using dynamic lighting and have twilight clerics, try to get away with only doing 120ft DV on their tokens, until they ask for full visibility. | ||
| + | # Host on [[Dev Server]] on weekends. | ||
| + | # Don't share sessions to non paying users. You are contributing to the congestion when you give folks pro sessions to host with. ('''Additional Comment:''' I do host games for my friends to run, but only games for which I am a player. If that's the use case, it won't impact the number of games being run.) | ||
| + | # Try to offload assets to other sessions and run a very narrow live session for the players. Pro users have the [[Transmogrifier]] that lets you move virtually everything between your live campaign and a [[Library Campaign]]. Its at the very bottom of the settings tab on the right side. Its hidden if you have the third party tools installed. ('''Additional Comment:''' Heavy agreement with the use of [[Transmogrifier]] to maintain a [[Library Campaign]]. This and the API are the biggest draws to a Pro account.) | ||
| + | # If you use Torch API, try to limit the use of flicker to just player tokens and use stationary lights for environmentals. | ||
| + | # Keep players sheet access to less then 5 total sheets, keep yours as low as possible, drag out from monster manual or create a bestiary and transmog creatures as you need them. | ||
| + | # If playing a game that features a resource like spells, limit the number of spells on a sheet at any given time to as few as playable. Spells have a lot of data fields and bloat a sheet very quickly. So D&D 5E clerics and druids are recommended to not include all spells they have access to on their sheet, but limit them to the once they use frequently, especially at higher levels. | ||
| + | # Use short lines for [[DL]]. Keep them simple. They are easier to edit in case of error or change, and are less mathematically demanding. And use the Poly line tool. Avoid curves and circles unless necessary. They work now, but can still lead to unexpected results in high numbers. | ||
| + | # It's better to divide very large maps into different pages, when possible. | ||
| + | # '''Look into automation.''' As a {{Pro}} user, you have access to [[API]] scripts, which can automate many mundane tasks and mitigate the experience of lag. | ||
| + | # '''Turn off vision for all the NPCs and monsters on your maps.''' The more tokens with 'vision' the greater the demand on the system to make all those calculations/lighting adjustments. As DM, I can turn on any token 'vision' to check line of sight or any other vision parameter before turning it back off. My games all picked up smoothness of operation and reduction of lags (despite being on weekend nights) when I made this change. | ||
| + | |||
| + | =See Also= | ||
| + | * [[Browser]] | ||
| + | * [[Best Practices for Files on Roll20]] | ||
| + | * [[Library Campaign]] - A good idea for storing unused maps & characters in large campaigns | ||
| + | * [[Dynamic Lighting Examples#Best Performance Guide|Dynamic Lightning - Best Performance Guide]] | ||
| + | * [[Community FAQ]] | ||
| + | <br /> | ||
[[Category:Guides]] | [[Category:Guides]] | ||
| + | [[Category:Game Management]] | ||
| + | [[Category:Web Browser]] | ||
Latest revision as of 04:23, 11 July 2023
 | Page Updated: 2023-07-11 |
Attention: This page is community-maintained. For the official Roll20 version of this article, see the Help Center for assistance: Here .
As far as most gaming-related applications go, Roll20 has very low network and graphical performance requirements. The vast majority of our users never need to worry about any of the following. However, if you(as GM), or one of your players, has a very slow Internet connection or a very old computer, these tips may help you have a smoother time playing.
Roll20 is a web-based application, and as such there are two primary performance considerations: the speed of the network connection, and the speed of the graphics rendering on the client's computer.
Note: Your own individual results may (and probably will) vary from other people playing in your game. If you're the GM designing the Roll20 Game, you'll want to keep the worst performing client (which may not be you) in mind. Just because a 500 unit by 500 unit map scrolls smoothly on your computer doesn't mean it will work well for your player with a 4-year-old machine.
TL;DR: Slow network connection? Your biggest hit is going to come in the video chat department. Try switching your game to broadcast audio-only. Have a player with a really old computer? Try limiting the number of objects on-screen.
Contents |
[edit] Graphics Rendering
The graphics rendering performance of your computer is determined by several things, including having an up-to-date browser, your CPU speed, amount of available system memory, and your graphics card. While you certainly don't need a high-end gaming PC to use Roll20, playing on an underpowered netbook computer may cause you to experience jerky or unresponsive performance. For best results, consider using a mid-range computer (one built in the last 3 or 4 years should be more than sufficient, and old computers may be fine as well) with a dedicated graphics card and a screen resolution of at least 1280x1024.
The graphics rendering of your computer directly affects how quickly things can be drawn on your screen as the scene changes. So when a token is moved or added, or you zoom, or scroll/pan around the map, the screen is being constantly redrawn. The better your graphics rendering performance, the smoother those operations will "feel".
Pro
info users: Creating a Library Campaign for storing unused maps & characters for large campaigns is a good idea, so you can use the Transmogrifier to retrive content to the active game campaign from your Library Campaign.
[edit] Optimize Campaign
- Figure out how large your campaign is: Campaign Survey(Forum) - helps you inventory the size of your campaign, by listing how many pages/characters/handouts/graphics/etc it has, how often each are used, etc.
A few tips for getting the most out of Roll20 with a low-performance PC (sorted by "most likely to help" to "least likely"):
- Limit the number of PC and NPC N Journal Entries in each game. A vast majority of users that report issues have games that contain entries for several hundreds or thousands of Characters and Creatures.
- (fairly certain) Having a large number of Handouts makes a neglect-able difference, it's the large number of character sheets that slows down Roll20.
- Limit the number of images that you use. For example, try to use only a single image on the Map layer, instead of a large number of map tiles, furniture, etc. Instead, create the map in an external program and then import it as one JPG or PNG file. The fewer objects that Roll20 has to render individually, the better your performance will be.
- Keep map sizes small. (The default size of 20x20 is a good bet.) Divide larger maps encounters across several pages if need be.
- Turn off Dynamic Lighting. Larger maps takes a larger performance hit than smaller ones. Applies both for LDL and UDL
- reduce number of light sources
- reduce number of tokens that have vision
- While players need to see, NPCs managed by the GM seldom have use for vision as the GM sees the whole map and can somewhat judge if individual NPCs have Line of Sight or not.
- reduce amount of DL lines
- if you have many shorter segments draw on the map, they might take more processing than fewer, but larger segments covering the same area
- Turn off the grid and/or Fog of War mechanics -- both of these require extra graphics processing on each new frame draw to use, slowing down your computer.
- Limit your use of the Drawing Tools
- Proinfo users can move unused content to a Library Campaign with the Transmogrifier, and later copy things back if those things are again needed.
Note: Archiving characters/handouts/maps does not improve performance, only hides them from your direct access, and don't improve game performance
[edit] Browser
Main Page: Browser
Roll20 officially only supports the Firefox & Google Chrome browsers, so if you encounter a problem using other browsers, it's recommended to switch to either of these. And no, using any Chromium-based browser like Microsoft Edge is not the same thing as using Chrome. Roll20 often works well on other browsers, but your mileage may vary.
There is no consensus on which browser works best for Roll20, as it seems to vary based on things like what operating system you use(Windows/Mac/Linux), your hardware(physical computer), your ISP, what browser plugins you use, and even what version of the browser you have.
Some have claimed Chrome is faster, others swear by Firefox. It can be a good idea to try out the other (Firefox/Chrome) in case things are more smooth with it.
It's possible some Stylus-scripts can hide or adjust how roll20 looks, in a way that improves performance, but not guaranteed.
[edit] Chrome
 | This section is outdated, or could otherwise do with some cleanup. |
Chrome has adjustable flags that may improve performance on some systems. However please note that these are advanced settings and in certain cases can cause degradation or unexpected behaviors. To view the Flags section browse to chrome://flags/ in the address field.
Flags that may help with performance:
- Override software rendering list: This allows GPU acceleration on unsupported configurations. Useful if you tend to run experimental GPU drivers or if you think your GPU is not being recognized for some reason.
- GPU Accelerated SVG Filters: This lets the GPU do work for some type of SVG filters.
- Threaded compositing: This will allow secondary threads to be dedicated to page compositing.
- Disable GPU VSync: Removes Vsync with your monitor's refresh rate.
- GPU compositing on all pages: Force GPU compositing on all pages, not just those with GPU features.
[edit] Firefox
Main Page: Browser#Firefox
- turning off "form autofill" · Sometimes Firefox mistakes Roll20 character sheets for web form to be filled out, and then processes all the suggestions it can figure out for each field, for each character sheet.
- turn on Performance Settings · turning on hardware acceleration ensures your firefox uses as much of your computer's processing power as possible
[edit] Network Connection
| This section is outdated, or could otherwise do with some cleanup. |
Network connection refers to two things: the amount of information your connection can carry at once ("bandwidth") and the speed at which it can make a round-trip to the Roll20 servers ("latency").
The virtual tabletop itself is very lightweight from a bandwidth perspective. Common actions such as sending a chat message or moving a token require very little data. In fact, you and your players will spend much more time downloading image files for tokens and maps included in the game, than you will due to performing actions in the interface. For example, you would need to move 1,000 tokens at the same time to generate as much data as it takes to download one small 7 KB token image. This means that even if you have a "slow" connection (e.g. 768 Kb/s, a common low-end DSL speed), your use of the Roll20 tabletop should not be very affected. A slow bandwidth will mostly cause you to have a long initial load time, and you may see images loading in slowly if your GM adds more throughout the game.
Latency, on the other hand, determines how quickly you'll receive changes during gameplay. If you have a very unreliable connection (such as via a 3G cellular signal or satellite Internet service), you may experience high latency. Roll20 is designed to be fairly fault-tolerant, so you'll still be able to participate, but you may experience delays of several seconds between someone moving a token piece and it appearing to move on your screen.
[edit] Video Chat
Main Page: Video Chat
By far, the part of Roll20 most-affected by your network connection is the integrated voice and video chat. It is recommended that you have at least 250 Kb/s of downstream bandwidth for each member of your group, as well as at least 250 Kb/s of upload bandwidth for broadcasting a video stream from your computer to the group. High latency will also affect your video chat performance, causing there to be delays or even dropped/skipped frames (resulting in "jerky" video).
If you are using the built-in Roll20 video chat and it's not working well for you, and especially if you are located outside of the United States, you could consider using another voice/video service. Many use Discord for voice/video, instead of Roll20's built-in options.
Using a separate service for voice, while using Roll20 for the tabletop and video only, might make for a more stable Roll20 experience. That way, if your video/voice service or Roll20 have issues, you have the other one to rely on. If Discord is acting up, you can then switch to use Roll20 again for voice.
[edit] Common Issues
Below are a few common performance issues seen by Roll20 users, and their cause:
- The map and sidebar are compressed into the top of my browser. This is usually caused by an extension or plugin. Try deactivating your extensions and plugins until you find the one causing the problem.
- Jerky/slow scrolling/panning/zooming. This is caused by low graphical rendering performance. See the section above for tips on improving graphic performance.
- Fog of War and/or grid completely disappears on the map. This is caused by your graphics card running out of video memory. You'll need to use smaller maps.
- When scrolling/panning, the grid or fog of war "lags behind", revealing parts of the map. This is caused by low graphical rendering performance. Your best bet is to use a smaller map, or not use the fog of war feature.
- Jerky video chat, skipping, dropped frames, "laggy". Could be caused by either network or graphical performance issues. Try using voice-only chat, using a dedicated video chat service, or disabling Roll20 video/voice chat entirely.
- There is a delay between when I see a text chat message appear and when someone says something about it in the video chat. There is a standard delay of a second or two in the video chat -- a lot of data has to make a trip to a server and then to your other group members, and the connection speeds and latency of the hops in between slow things down. If you're seeing a larger delay than that, it's most likely a latency issue.
[edit] Mobile
Offloading some tasks from the computer to a tablet or smartphone, such as character sheets with the Mobile app, could help your computer keep up.
[edit] Additional Suggestions from the Forums
Optimization Tips/Suggestions copied from the forum post: Lag(Forum)
- Uninstall the very questionable third party tools and use the scripts made here in their place.
- If you have Door Knocker API installed, make sure any other non door maps are not accidentally drawn in the colors for doorknockers color codes. If they are, that’s a TON of doorknocker api auras drawn on the page and will lag you to all hell. (Additional Comment: If you are careful with your DL line colors, Doorknocker shouldn't be an issue. I use it all the time.)
- Health auras looks so cool, but the more auras on tokens, the “laggier” the game gets. Keep an eye on various API's cause some use invisible auras like doorknocker.
- Turn off Dynamic Lighting completely. If you use Dynamic Lighting, do not use Freehand mode for your barriers (lines and shapes are much faster to load).
- If you are using dynamic lighting and have twilight clerics, try to get away with only doing 120ft DV on their tokens, until they ask for full visibility.
- Host on Dev Server on weekends.
- Don't share sessions to non paying users. You are contributing to the congestion when you give folks pro sessions to host with. (Additional Comment: I do host games for my friends to run, but only games for which I am a player. If that's the use case, it won't impact the number of games being run.)
- Try to offload assets to other sessions and run a very narrow live session for the players. Pro users have the Transmogrifier that lets you move virtually everything between your live campaign and a Library Campaign. Its at the very bottom of the settings tab on the right side. Its hidden if you have the third party tools installed. (Additional Comment: Heavy agreement with the use of Transmogrifier to maintain a Library Campaign. This and the API are the biggest draws to a Pro account.)
- If you use Torch API, try to limit the use of flicker to just player tokens and use stationary lights for environmentals.
- Keep players sheet access to less then 5 total sheets, keep yours as low as possible, drag out from monster manual or create a bestiary and transmog creatures as you need them.
- If playing a game that features a resource like spells, limit the number of spells on a sheet at any given time to as few as playable. Spells have a lot of data fields and bloat a sheet very quickly. So D&D 5E clerics and druids are recommended to not include all spells they have access to on their sheet, but limit them to the once they use frequently, especially at higher levels.
- Use short lines for DL. Keep them simple. They are easier to edit in case of error or change, and are less mathematically demanding. And use the Poly line tool. Avoid curves and circles unless necessary. They work now, but can still lead to unexpected results in high numbers.
- It's better to divide very large maps into different pages, when possible.
- Look into automation. As a Proinfo user, you have access to API scripts, which can automate many mundane tasks and mitigate the experience of lag.
- Turn off vision for all the NPCs and monsters on your maps. The more tokens with 'vision' the greater the demand on the system to make all those calculations/lighting adjustments. As DM, I can turn on any token 'vision' to check line of sight or any other vision parameter before turning it back off. My games all picked up smoothness of operation and reduction of lags (despite being on weekend nights) when I made this change.
[edit] See Also
- Browser
- Best Practices for Files on Roll20
- Library Campaign - A good idea for storing unused maps & characters in large campaigns
- Dynamic Lightning - Best Performance Guide
- Community FAQ
