Why this matters

Before blaming kerf or machine motion, inspect the node geometry at high zoom and simplify a copy of the path.

How to think about it

Define the result you actually need, then confirm the active machine profile, units and operating mode before changing parameters.

Practical workflow

  1. Define the result you actually need, then confirm the active machine profile, units and operating mode before changing parameters.
  2. Change one meaningful variable at a time and use Preview/Frame or offline analysis before running a real job.
  3. If the issue repeats, keep evidence: Console output, a G-code sample, the exact settings used and material context. Evidence makes troubleshooting reproducible.

If the result is wrong

Before blaming kerf or machine motion, inspect the node geometry at high zoom and simplify a copy of the path.