Seeking Advice on Optimizing Performance for Large Worlds in Forge VTT

[evans]

Hi everyone,

I’ve been using Forge VTT for a few months now and overall, the experience has been fantastic. The integration and hosting have made it so much easier for my group to stay connected and engaged. However, I’ve recently run into performance issues when managing larger worlds or scenes with heavy assets.

Specifically, I have a campaign that uses several high-resolution maps (sometimes 8K), dynamic lighting, and quite a few animated tiles. When running sessions, my players report lag when loading scenes or moving tokens, and some even experience freezing or long load times. I’ve tried reducing asset sizes and enabling lazy loading, but I’m not sure what else I should be doing.

Forge LiveKit integration

I’ve got two groups I’m playing with, both using Foundry on Forge with the Forge-hosted LiveKit integration. For the past couple of weeks, we’ve been having issues with some of the video freezing for a couple of seconds, and then catching back up. At the same time, the audio mutes, and then stutters for a couple of seconds when it catches back up. When it happens, multiple people can see if occurring, so it’s not isolated to one particular person. It also tends to happen about 5-7 times in a…

A few questions I’m hoping to get help with:

• What are the best practices for optimizing large scenes within Forge?
• Is there a recommended maximum file size or resolution for map assets?
• Should I consider breaking up my worlds into smaller modules or scenes to improve load times?
• Does the asset library configuration (e.g., using default vs premium hosting) have a noticeable impact on performance?

Also, if anyone has any tips for managing compendiums or journal entries of mulesoft course in hyderabad in large campaigns to keep things organized and efficient, I’d love to hear them.

Appreciate any guidance from folks who’ve handled similar setups! I want to make sure my players continue to have a smooth and immersive experience.

Thanks in advance.

[akifsm]

Hi Evans, late response I know, sorry… To make this visible for anyone seeking answers in the future, and you as well, here’s some tips for optimization.

@evans

• What are the best practices for optimizing large scenes within Forge?
• Is there a recommended maximum file size or resolution for map assets?
• Should I consider breaking up my worlds into smaller modules or scenes to improve load times?
• Does the asset library configuration (e.g., using default vs premium hosting) have a noticeable impact on performance?

• Generally .Webp and .WebM are best formats for assets, on larger maps having fewer wall segments helps, having fewer light sources helps as they are quite a resource hogs.
• Recommended file size is around 10mb for map assets, though this depends largely on the machine specs of your players, if you’re all on high end machines even 100mb assets are manageable.
• Breaking up scenes is possible but not advisable, try implementing optimizations first as mentioned above, and moving unused assets, actors and items to compendiums.
• If you mean do higher tiers of subscription offer better performances then the answer is no, all subscription tiers get same performance.

Now having too many active modules can also degrade performance, especially if they write into chat with images, clearing your chat history once in a while is advisable.

All in all, Forge/Foundry is capable of handling a lot of stuff at once, but if you or your players machines aren’t that good, performance will suffer.

Hope that helps.