Beneos Battlemaps

Beneos FAQ - BLACK SCREEN / "!" ERROR

If you encounter a black screen on a map or a large triangle with an exclamation mark in Foundry VTT, this indicates that an asset (image, video, or token file) could not be loaded.

What causes this?

This issue occurs when Foundry VTT cannot find or access a file at the specified path. In most cases, the problem is not the scene itself, but a missing or inaccessible asset on the server.

The referenced file was deleted manually
The content was not fully installed
The download was interrupted or corrupted
The file path exists, but the server cannot access or serve the file

You can often confirm this by opening the browser console (F12) and checking for errors like:

404 (Not Found)

How to fix it (Step-by-step)

Delete the affected content
Remove the broken scene, tile, or token from your Scene Browser or Actor directory.
Re-download the content
Install the content again via Beneos Cloud or Moulinette.
Only missing content will be downloaded again.
Reload your world
After reinstalling, reload Foundry VTT to ensure all references are refreshed.

If the problem persists

If the same asset repeatedly fails, the cause is usually related to download quality, not download speed.

Unstable connection
Large ZIP files (especially those containing animated assets like WebM files) are sensitive to transmission errors. Even small data corruption can break entire files.
Wi-Fi issues
Wireless connections are more prone to packet loss and instability.

Recommended action:

Use a wired LAN connection instead of Wi-Fi
Re-download the affected content

Still broken on the same scene?

If the exact same scene consistently fails after multiple clean downloads, there is a small chance that the issue originates from our packaging.

In that case:

Report the issue to us
Include the name of the affected scene

We will investigate and fix it if necessary.

For self-hosted servers (VPS, Linux, AWS, etc.)

If you are running Foundry VTT on your own infrastructure, asset loading issues are often caused by server or network configuration, not the content itself.

Typical problem areas include:

Reverse proxy limits (nginx / Apache)
Timeouts on long downloads
Blocked HTTP range requests (required for large media files)
TLS / HTTP2 misconfiguration
Firewall or rate-limiting rules

Large animated assets (such as WebM files) require:

Support for persistent connections
Support for partial content (HTTP 206)
No premature termination of long-running downloads
No aggressive caching or rewriting of large binary files

We cannot provide a complete server configuration or checklist here, but make sure your server is capable of downloading, storing, and extracting individual files of up to 4 GB in size. The following formats are used in our releases: WebM, WebP, SVG, ZIP, OGG Vorbis, JSON, INFO, PNG.

Recommended troubleshooting:

Test the failing asset URL directly on the server using curl
Check server logs for rejected or interrupted connections
Review proxy configuration for size limits and timeouts

If the asset fails when accessed directly from your server, the issue lies within your infrastructure and must be resolved there.