- Frequently Asked Questions
- How Do I Access Foundry VTT?
- How Do I Link My Patreon to Discord?
- How do I enable WebGL?
- How Do I Connect to an IPv6 Address?
- How Do I Install Modules?
- I Forgot My Player Access Keys!
- Where Can I Place Content In Foundry?
- How Do I Apply Damage?
- How Do I Create a Custom Character Sheet
- How Do I Improve Performance?
- How Do Walls Affect Performance?
- Suggestions/Ideas/Issues
Access to FVTT is via a one-time purchase on https://foundryvtt.com. The license cost is $50 plus any available sales tax/VAT, and this license covers updates for the lifetime of the software. Only the host will need a license, everyone else can login via a webbrowser.
Refer to Patreon's instructions here.
Chrome - chrome://settings
-> "System" -> Toggle "Use hardware acceleration when available" to on
Firefox - about:preferences
-> Performance -> Uncheck "Use recommended performance settings" -> Check "Use hardware acceleration when available"
Open your browser of choice and enter the address like this: http://[IP:v6:AD:RE:SS]:PORTNUMBER
- Paste the full IPv6 Address between the
[
]
- Port number by default is 3000
Check out the Modules page for instructions.
Check /worlds/<worldname>/data/users.db
.
You can place anything you want in the public
folder located at resources/app/public
.
There is an option to apply damage from a roll. Right click on the damage and a context menu will show up that will apply that damage or healing to the select token.
Start by downloading the example HTML
and JS
files provided by Atropos:
- my-actor-sheet.js - This is the JavaScript that defines the sheet and registers it with the Foundry VTT system
- my-actor-sheet.html - This is the HTML template where you define the structure and templating for your sheet
NOTE - This does require knowledge of CSS
for styling.
One easy way to improve performance is by disabling soft shadows. You can do this in game by clicking Game Settings -> Configure Settings and uncheck Enable Soft Shadows.
You can also check what is affecting performance by opening the developer console (F12
) and running the following commands:
- Number of Walls:
console.log(canvas.walls.placeables.length);
- Number of Light Sources:
console.log(canvas.lighting.placeables.length);
- Number of Tokens:
console.log(canvas.tokens.placeables.length);
- Scene Dimensions:
console.log(canvas.dimensions);
Evaluate the results against the hardware of your machine on the client side
What matter for wall performance the the amount of unique wall endpoints, rather than the amount of walls themselves. In short longer walls are better than shorter walls.
- Terrain Walls have the same performance as a Regular Wall.
- One-Way Walls are more computationally intensive, as it has to check the orientation of the ray collision.
Check the official issue tracker first, and if it's not listed, jump on Discord and hit up the #vtt-suggestions or #vtt-testing channels (don't forget to search for your suggestion/idea/issue first before posting again!)