TrossPlan / field manual

Version 1.0.1 · Local rigging route planner for scale ship models.

Start with Mira

On Linux desktop Chrome, extract the buyer ZIP and open index.html. No installation or network is needed. The fictional Mira training layout opens automatically. The side and deck views show six named model-space points and three routes. Its entered stock total is 538 mm. Select R2 to see only the port route; change its allowance from 15 to 20, choose Apply edits, and the total becomes 543 mm.

Mira overview with three routes and 538 mm
1. The complete Mira sample and its measured total.
Selected R2 port route
2. R2 selected. Port uses negative Y and a dashed route.
R2 allowance changed and total 543 mm
3. The changed allowance updates the material total.

In a narrow window, the Routes, Points, Materials and Project tabs wrap onto another line so every tab remains available. Use Tab to focus a tab and Enter or Space to select it. Linux desktop Chrome remains the intended working environment.

Make your own plan

  1. Choose New plan. In Points, add at least two named attachment points. Enter model-size X fore/aft, Y negative port or positive starboard, and Z upward in millimetres.
  2. In Materials, add the stock family and its measured diameter. In Routes, list point IDs in travel order, choose a family and side, enter the physically measured run and allowance, then any prerequisite route IDs.
  3. Choose Apply edits to update the preview immediately. Valid form drafts also apply when you switch items or tabs, save, or export; invalid drafts, including blank numeric fields, remain visible with an error until corrected. Enter 0 explicitly when zero is intended. Review both schematic views, the pass order and the material total. Choose Save project for editable JSON and Export work pack for a ZIP containing JSON, SVG views, CSV schedules and a PDF packet.

Use Open JSON to reopen a saved schema-1 TrossPlan project. Opening a file preserves it on disk. Save and export always download new files. Unsaved applied edits and pending form drafts trigger a warning before New plan, Load Mira or Open JSON replaces the project; cancelling retains the draft. There is no autosave.

Review and use exports

The diagrams auto-fit and are not full-size templates. Crossings do not imply connections. Read the route pass list and coordinate table for exact IDs. Length totals use entered measured run plus allowance; TrossPlan never calculates physical line length from straight-line geometry. The PDF is A4 or Letter according to the Project tab. Its pass lists use ASCII -> separators for reliable PDF rendering and text extraction. Read it in a PDF viewer and inspect fit on the physical model before cutting stock.

CSV is UTF-8 with quoted fields. Text beginning with spreadsheet formula characters is prefixed with an apostrophe in CSV only; project JSON retains the original text. If importing CSV into a spreadsheet, inspect its text-import settings.

Limits and troubleshooting

JSON import is limited to 2 MiB, 48 points, 48 routes, 8 families and 160 route segments. Coordinates and lengths allow up to three decimals. Routes need 2–24 passes. Adjacent duplicate points are rejected; nonadjacent repeats make return passes. Unknown IDs, self prerequisites and cycles block work-pack export, but you can correct the plan and save JSON. The PDF pack is limited to 100 pages. This version accepts printable ASCII for PDF text; replace non-ASCII project text before export. The source JSON remains editable. No raster plan import is provided.

For a blank number or failed ID edit, correct the visible draft and choose Apply edits again; the prior plan stays intact. For an export error, read the message above the drawings. Check family and point IDs, route dependencies and paper choice. Test by loading Mira again; save your current project first. All processing stays in the local browser; no account or upload is used. To uninstall, delete the extracted folder. Downloads and saved projects remain wherever your browser placed them.

Tested: Linux desktop Google Chrome, local file:// context. Physical fit, historic accuracy and other browsers are unverified.

Safe file changes and downloads

While Open JSON reads and checks a file, the workspace pauses editing, navigation and exports. This prevents a late file read from replacing edits made in the meantime. Once checked, the file replaces the current plan. If reading or validation fails, the current plan remains and controls become available for retry. Back up unsaved work with Save project before opening another file.

Export work pack applies valid pending edits, then pauses controls until ZIP preparation finishes. If preparation fails, correct the reported problem and retry. A download is a snapshot of the visible plan; continue editing after it is ready. No autosave or background upload is added.

Opening a JSON file with disabled editor and explicit waiting status
File reading pauses the workspace until validation finishes. Screenshot uses a deliberately delayed local read.
R2 allowance changed to 20 millimetres and total 543 millimetres
Save applies the visible R2 draft. The total is 196 + 176 + 171 = 543 mm.