Skip to content

Troubleshooting

Daniel edited this page Sep 1, 2026 · 1 revision

Troubleshooting

It takes a while to load

The file is about 20 MB — 186 plate images, the traced outlines and the skull mesh, all inside one HTML file. That is the price of it working offline with no server. It is cached after the first load.

The 3D view says it could not start

The 3D view needs WebGL 2. If it is unavailable the view says so rather than showing a blank canvas.

  • Check chrome://gpu (or the equivalent) — hardware acceleration may be off.
  • Remote desktop and some VMs do not pass WebGL 2 through.
  • Update your graphics driver.

The Plate and Projection views need none of this and will keep working.

The 3D view is slow to appear the first time

It is built once, from the plate images already on the page. Nothing extra is downloaded. Subsequent switches are instant.

A structure has no coordinate

20 of the 723 structures have no located label, so there is genuinely no coordinate to give — the card omits the row rather than inventing one. See Accuracy and Caveats.

A structure I expected is not marked on a plate

Two possibilities:

  • A structure listed for a plate range is present at those levels but is not necessarily printed on every plate of the range.
  • Its label on that plate was not located automatically — coverage is 93%.

The coordinate looks off by a bit

A coordinate is the median of where the abbreviation is printed, not the structure's centroid. For thin or layered structures the atlas prints the label beside the region with a leader line. Read the plate.

A number moved the wrong way after I set a frame angle

Negate the angle. Nothing in the atlas records which way your frame is tilted, so the app cannot check a sign for you — that is what the Check the signs preview in the Frame dialog is for. See Working Frame.

The grid and the readout disagree while a frame is on

By design. With a rotated frame, the structure card, the pointer readout, the coordinate lookup and the CSV export are adjusted; the grid, the measure tool, the projections and the 3D view stay in atlas coordinates and each says so on screen.

An origin without a rotation has no such split — everything reads from your origin.

Copy link did nothing

Some browsers block clipboard access on a file:// page. The URL in your address bar is always up to date with the current view, so you can copy it from there instead.

Downloads are not appearing

PNG, SVG, CSV and the plan text are all generated in the browser and handed to its download mechanism. Check your browser's download settings and any "ask where to save" prompt.

Nothing here matches my problem

Raise an issue on GitHub — include the build hash from the app's footer, and a Copy link URL if the problem is about a particular view.

Clone this wiki locally