Guide
A model you liked is worth keeping, and a finished job is a stack of files. This guide covers named setups and their history, moving them between machines, and writing a whole job's print files into one folder with the setup that made them.
The top bar holds one saved-setups control, labeled with whichever setup you last recalled. Open it and every saved setup has a row.
Below the list, Save current setup stores whatever the controls hold under a name you type. Typing an existing name overwrites that setup.
A setup carries the whole model: the place, the relief, every layer and color, the puzzle layout, the tray, the wall mount, and any trails you imported. It also carries a stable puzzle seed and signed tile coordinates, so a super-tile run months later can still make edges that match the tiles you already printed.
The recalled setup's row carries its own Save. It reads "Saved" while the model still matches what was stored, and offers to write the change back as soon as the model moves away from it.
It compares the model, not your keystrokes. Nudge a slider and put it back and the button returns to "Saved" — there is nothing to write. So the button offering itself means something really is different from what is stored.
Each row keeps a History: the last five specs that setup held before being saved over. Any of them can be rolled back to.
Rolling back does two things at once — it restores the stored setup and loads it, replacing the model on screen. Because that discards whatever you had in the controls, it asks first, with the same in-row confirm Delete uses.
A rollback can itself be rolled back. The spec it replaced becomes a version of its own, so going back one version too far is not a dead end.
Below the list, Export writes every saved setup to a toposaic-setups.json file and Import reads such a file back. That is the way to carry a library to another computer, keep a copy outside the app, or hand a setup to someone else.
A finished job also writes a single-setup file of its own — see below — and Import reads that same shape.
A finished job lists its files on the Output tab. There are more of them than most prints need, so it helps to know which is which.
| File | What it is |
|---|---|
| The color 3MF | Every puzzle piece as its own object in one file. For most prints this is the only model file you need. |
| Tray, tray segments, wall-mount hardware, flag templates | Separate 3MFs beside it, one per part. |
| STLs | A plain STL for every one of those, plus one per puzzle piece, for anyone who would rather print from STL. Single color, but the raised road geometry is still there. |
| The manifest | What the job was made from, including the data-source credits that publicly shared prints and files must keep. |
In the desktop app, Save all print files to a folder asks once for a folder and writes the 3MFs and the manifest into a new subfolder named after the place. The STL list has its own save, for the same reason. Single files still save one at a time from either list, and the browser build downloads them individually.
The setup travels with the files. Each saved folder also gets a toposaic-setup.json — the setup that made those exact files, in the shape Import reads. It is taken from the job's own manifest rather than from whatever the controls hold by the time you save, so it describes the model in the folder even if you have been fiddling since.
Saving the same job twice makes a second folder rather than writing over the first.
The desktop app keeps its database and generated jobs in the standard application-data directory, and every file it writes goes through a native save dialog — nothing lands in Downloads without asking.
The gear button beside the setups control opens the settings pane, which shows the map data cache: elevation tiles, land cover, OpenStreetMap, and place search, each with its size and entry count. Clearing is always manual — pick an age and clear older entries, or clear everything after a confirm click. Nothing expires on its own, and the next generation re-downloads what it needs.
To move any of it, set TOPOSAIC_DATA_DIR for the database and generated jobs, and TOPOSAIC_CACHE_DIR for the downloaded map cache.
Before you save a setup worth keeping: choosing what the map draws and the color printing guide.
More projects from theatr.us