Skip to content
PostRoll Help

Troubleshooting

The preview is blank or stuck on “Generating…”

Section titled “The preview is blank or stuck on “Generating…””
  • Hard refresh the page (Cmd / Ctrl + Shift + R). The Web Worker occasionally needs a clean reload after a deploy.
  • Pick a smaller Detail in the Build tool. High detail can take several seconds to generate the first preview; Medium is the safer default.

“Save scene” fails

Section titled ““Save scene” fails”
  • Sign in again. The save calls the server with your auth token; if your session expired the render request returns 401.
  • Check the worldId. If you picked a world that you’ve since archived or that no longer exists, the commit step returns 404.
  • Decoration upload failed. If you have a lot of custom-uploaded image decorations, a single failed upload can block the compositing step. Clear the failing decoration and retry.

The dialog names the current step — “Rendering…”, “Uploading decoration layer…”, “Compositing & creating scene…” — so you know where a failure happened.

The save uses a different style than the preview

Section titled “The save uses a different style than the preview”

This was a real bug that’s now fixed (the server render aesthetics were stripping chrome, kingdom, and coastlineFidelity from the settings before painting). If you still see a mismatch:

  • Hard refresh to make sure your client is on the current build.
  • Try a different style. If only one specific style is misbehaving, flag it — the PALETTE table is the canonical source of truth.

Settlements / labels look misplaced after saving

Section titled “Settlements / labels look misplaced after saving”

The save now applies the same Mountain obliqueness lift to every feature’s coords that the basemap shows, so settlements should sit on the lifted peaks. If you see settlements at the foot of a peak rather than on top:

  • Check the obliqueness slider. If it’s at 0 the basemap is flat and features should be at their pixel-accurate positions.
  • Hard refresh. The lift-on-export fix is recent; older saves from before the fix have flat feature coords baked in.

Custom palette tweaks don’t appear in the preview

Section titled “Custom palette tweaks don’t appear in the preview”
  • GPU painter cache. The GPU shader caches biome and ocean LUTs per style; the cache invalidates on style change OR override change. If you see stale colours, change any palette override slightly and back — the cache invalidates on the way out.
  • Clear the field. Empty the text input next to a colour picker to restore the palette default.

Kingdoms aren’t showing

Section titled “Kingdoms aren’t showing”
  • Check Render mode. If it’s “Off”, nothing renders. The default is “Border”.
  • Need at least two seats. If your map has only one capital / city and no towns, there’s no second seat to draw borders against. Bump Settlement density or set the kingdom Count higher.

The Foundry feels slow

Section titled “The Foundry feels slow”
  • Drop Detail to Low while exploring; bump to High before saving.
  • Turn off Coastal features in the Build tool if you don’t need the cliff / beach / cove tagging. It’s an extra pass on every rebuild.
  • Turn off Live brush if you’re not actively painting. The GPU overlay pre-warms in the background and can compete for resources with the worker render.

Decorations look right in the preview but missing in the export

Section titled “Decorations look right in the preview but missing in the export”

Make sure decorations aren’t hidden or locked in the Layers panel — hidden decorations aren’t rasterised into the chrome overlay. Lock state is preserved but doesn’t affect rendering.

If a decoration is still missing, try removing and re-adding it. Inline-SVG decorations occasionally lose their parsed source if the SVG was malformed — re-uploading often fixes it.

Section titled “Related”