Duplicate Paths Can Add Heat and Time: Make File Preflight a Release Gate
Duplicate paths can add travel, processing time, and heat to affected regions. Use detection and slow preview as evidence, then prove the cleaned file under active supervision.
Duplicates change the path, not just the screen
Current LightBurn discussions show duplicate geometry extending some jobs from about one minute to 15–20 minutes and rerunning affected paths. That constraint appears in the LightBurn workflow discussion.
Count and isolate overlapping geometry
| Check | Old file evidence | Clean file evidence | Limit |
|---|---|---|---|
| object/path count | record value | record new value | count alone is not correctness |
| duplicate selection | move aside for inspection | approved removals only | near-overlaps may remain |
| slow preview | repeat travel visible | expected order | preview is not physical proof |
| supervised coupon | eligible material only | accepted observation | not a safety guarantee |
Why one minute can become much longer
A purchased shape appears single at normal zoom, yet preview pauses and traverses the same region repeatedly. Moving the selected duplicates aside exposes narrow rectangles. The operator cleans only confirmed redundant geometry and retains both file counts.
Compare the old and cleaned previews
- Duplicate the source file before deleting anything.
- Use the software's detection, then move selected geometry aside temporarily to see what remains.
- Review near-overlaps and tiny rectangles that exact duplicate tools may not identify.
- Save a new release, invalidate the old one, and supervise an eligible-material proof.
X1S Pro file-release boundaries
Duplicate detection and checksums are file evidence, not automatic approval. Eligible material, an attended proof, exhaust, fixture state, and stop readiness still govern physical release. Review the current X1S Pro configuration separately from the file-identity and supervised-release evidence.
Return unresolved warnings to the attended popup handoff, and do not release a cleaned wide fill until the real scan-width comparison is accepted.
Duplicate-path questions
Will removing every selected path fix the design?
Not necessarily. Some overlaps may be intentional, and some problematic shapes are not exact duplicates.
Can duplicates exactly double time?
No universal multiplier applies. Complexity and path order determine the impact.
Does a checksum prove the file will engrave correctly?
It proves identity, not suitability, setup, or outcome.