Manual Troubleshooting

Troubleshooting

Symptoms, causes and fixes. If nothing here matches, open an issue.

The application will not start

If you are running an older version

These three are fixed. They are listed because an older build still shows them — check Help → Version first, and upgrade if you are behind.

A workspace saves but will not reopen (fixed in libplatemaker 0.2.1) — caused by non-ASCII characters in the path.

This looked like a Google Drive restriction, because Drive gives the folder a localised name — "Mój dysk" on a Polish account, for example. The cause was path encoding, not Drive. Non-ASCII paths have been supported since 0.2.1.

Inputs stay amber after a successful render (fixed in libplatemaker 0.2.1) — the same cause. Statuses failed to update, so every render redid all the work and overwrote the output, indefinitely.

Duplicate profile identifiers (handled since 1.1.0) — profiles created together in one pass of the manage dialog could end up sharing an internal identifier. Platemaker now detects this when loading a workspace, repairs it, and explains what changed. Afterwards some projects may show as out of sync; render them or press F6 to settle it.

Camera photos render sideways, upside-down, or with a black band (fixed in 1.4.2) — a rotated phone/camera photo used to ignore its rotation tag and render wrong, sometimes split across two files. Photos now render upright. See Rendering.

A render aborts when the folder mixes photos and screenshots (fixed in 1.4.2) — mixing plain photos (RGB) with images that carry transparency (RGBA) used to kill the whole render. Such a mix now renders through.

Re-rendering fails with "unable to open for write" (Windows) (fixed in 1.4.2) — an intermittent read/write race, most visible on the Webtoon profile, aborted a re-render. Fixed.

Windows 10: the window is a light/dark mix (fixed in 1.4.2) — the forced dark theme left the menu bar, docks and tabs light while dialogs stayed dark. The whole window now renders dark on Windows 10.

→ Workspaces

A canvas profile will not assign to a project

→ Canvas profiles

A page is missing from the finished chapter

Since 1.2.0 a size mismatch no longer drops a page, so a genuinely missing page means the file itself could not be used. The tile is violet ("Skipped") and the render finishes in Require action; the log names the file.

Check, in order:

1. Is the file still there? A Skipped tile means the file is missing or unreadable — moved, renamed, or not finished syncing from the cloud.
2. Did the drive letter change? If the workspace lives on Google Drive, a changed mount letter breaks every stored path at once — see Workspace on Drive.

If instead a page came out without its margins — tile cyan, "Processed (no canvas profile)" — that is not a missing page; it rendered, just uncropped. Assign a matching profile and re-render. See Canvas profiles.

→ File statuses

A render produces no output

Output looks stale after changing the format

→ File statuses

Files changed outside the application

Cloud-sync problems

→ Workspace on Drive

macOS

Not supported and not tested. Building from source may work but nothing is verified.

Reporting a bug

---

See also: File statuses · Rendering · Installation · About