Find travel moves that may contribute to stringing
Stringing happens on the physical print, but the file can reveal where the nozzle travels without extrusion and whether retraction commands or extrusion-only retract moves appear around those journeys.
Turn on travel moves, isolate the layer where strings appeared, and inspect paths crossing open space or moving between islands. Then check the nearby source for retraction evidence. This identifies candidates for comparison; it does not prove that a move caused stringing.
0101 / Inspection steps
Inspection steps
Use the views in this order so the broad shape, the layer detail, and the source line tell one consistent story.
- 01
Match the printed defect to a layer or region
Use the model height and visible string location to narrow the search. In 2D, move through nearby layers rather than examining every travel line in the full 3D stack.
- Look for separate islands or towers connected by non-printing motion.
- Note whether the same crossing repeats across many layers.
- 02
Show and compare travel paths
Enable non-printing travel and look for long crossings over open space or visible outer perimeters. Compare their route and frequency with nearby layers that printed cleanly.
- A travel line is planned nozzle motion, not deposited plastic.
- Shorter or internal travel may be less visible, but the file alone cannot rank actual ooze.
- 03
Read retraction evidence in context
Select a nearby path and inspect the original source. Retraction may appear as G10/G11 with firmware retraction, as extrusion-axis-only moves, or through slicer comments and state changes.
- Do not search only for G10: many slicers encode retract with E movement instead.
- Compare temperature, retraction settings, filament condition, and nozzle state back in the slicer and printer.
02 / What to look for
What to look for
These are observable clues in the file, not guarantees about the physical print.
Open-space crossing
Repeated non-extruding moves between separate features are useful candidates to investigate.
Perimeter crossing
A travel path that crosses visible outer regions may leave a more noticeable artifact if the nozzle oozes.
Retraction context
Nearby retract/recover evidence helps explain planned pressure management, but not whether the physical system performed it well.
03 / What this cannot prove
What this cannot prove
A G-code viewer reads planned commands. It does not see nozzle condition, wet filament, calibration, or how firmware and hardware execute the job.
- The preview cannot see wet filament, excessive temperature, a dirty nozzle, hotend assembly, pressure tuning, or mechanical retraction performance.
- No travel-pattern rule can label a print as 'will string.' Use the viewer to form a testable hypothesis, then compare controlled prints or slicer changes.
04 / Common questions
Common questions
Does every long travel move cause stringing?+
No. Stringing depends on material, temperature, retraction, pressure, nozzle condition, speed, and the machine. A long crossing is only a useful place to investigate.
Why can’t I find G10 and G11?+
Those commands are specific to firmware-retraction workflows. Many slicers encode retraction as extrusion-axis motion, so the same behavior can appear without G10/G11.
06 / Technical sources
Technical sources
The workflow is grounded in current viewer behavior and these official technical references.