Performance and Loading¶

Goal¶

Help you decide whether the app is still progressing normally or is actually stuck.

Supported Platforms¶

iOS
macOS

Intended Audience¶

Users waiting on import or scene preparation and unsure whether the app is still progressing
Testers triaging loading stalls, apparent hangs, or perceived performance regressions

Prerequisites¶

A document is currently importing, opening, or building a 3D scene
You can still observe the visible progress state, stage text, or UI responsiveness

Steps¶

Check whether the stage text, percentage, or loading card is still changing.
Confirm whether the UI still responds to basic interaction.
Record the exact stage and how long the app remains there before deciding that it is stuck.
Compare the behavior against the known normal-wait and suspicious-stall patterns below.

Result¶

You can distinguish between normal staged progress, a protective stop, and a likely real loading problem.

Common Waiting Stages in the Current Version¶

Import to 2D preparation¶

the top of the library shows an import banner
the workspace may temporarily switch to Data
the 2D viewer may remain blocked until the first projected frame is published

3D scene construction¶

3D shows explicit stage and progress text, such as:

Prepare
Metadata
Scene
Meshes

How to Tell That Progress Is Still Normal¶

Focus on these signals:

the progress number or stage text is changing
the UI still responds to basic interaction
the import banner or 3D loading card keeps updating

If all three are true, the app is usually still progressing normally.

When to Suspect an Actual Problem¶

the app remains on the same stage for a long time with no text change
the UI becomes unresponsive
the same input repeatedly stalls at the same point on the same device
the behavior only appears in this version and not in previous stable ones

A Few Current Implementation Facts¶

During import, the viewer may automatically switch to Data; this is a normal transition and does not mean opening failed.
3D only applies to KiCad. If the source is not KiCad, an unsupported message is not a performance problem.
If a huge IPC-2581 input is blocked by preflight, that is a protective stop, not a loading slowdown.

What to Record¶

device and platform
input type and size
which stage the app stops at
how long it stays there
whether the UI still responds
whether the issue only appears in one view

Common Questions¶

If it waits for a long time, does that always mean something is wrong?¶

No. Large boards, first-time 3D scene construction, and manufacturing-package recognition can all produce noticeable wait time. What matters is whether the state is still advancing.

Why is it important to record the exact stage?¶

Because the current implementation already breaks import and 3D loading into explicit stages. Recording the stage makes reproduction and diagnosis much faster.

Last Verified¶

2026-04-17