Benchy hull line: compare the print with its sliced layers
If your Benchy has a horizontal line near the deck, compare its position with the layers in the original print file before changing hardware. Prusa's explanation for this hull line centers on a model and layer-time transition. Repeated uneven bands across a wall need a different investigation; a photo alone cannot identify their cause.
Match the line to the model before touching the printer
Start with the finished print and the exact exported G-code that produced it. In the cited PrusaSlicer 2.9 workflow, File → G-code preview opens an exported file; the right-side layer slider lets you inspect a height range. If the original file is missing, record that. A new slice with changed settings or profiles cannot confirm the toolpath that printed.
For an upright Benchy printed directly on the bed, measure the line's approximate height from the bottom of the part, then inspect a small range around that height in Preview. A raft, raised support base, or changed orientation needs its own coordinate mapping; if the offset is uncertain, use the unknown branch below. A ruler reading does not identify one exact layer.
Check whether the Viewer can identify the relevant features. Prusa warns that feature information can be unknown or unreliable for some G-code. A loaded file with missing feature labels is not evidence that a transition is absent. This comparison is an inspection aid based on the documented Benchy explanation, not a manufacturer-validated diagnosis.
Scroll the table sideways to read every column.
| Evidence in the original print file | Classification | Next decision |
|---|---|---|
| The measured line range overlaps a visible sparse-infill/top-layer transition near the deck, with readable feature information. | Consistent with the Benchy hull-line explanation; not proof of its cause. | Read Prusa's Benchy explanation before changing hardware. It describes model-specific factors, not a universal fix. |
| The original file is interpretable, but no transition appears in the mapped height range. | This comparison does not support the deck-transition explanation. | Preserve the file and measured range. Use the printer's support diagnostics with that evidence; this result does not identify a faulty component. |
| The original file is missing, feature information is unknown, or physical height cannot be mapped confidently. | Cannot establish a match or mismatch. | Recover the original file or ask support to interpret it. Label a re-slice as an approximation; do not choose hardware adjustments from missing evidence. |
| Bands repeat over a plain wall, the contour steps sideways, or the defect is confined to the first layer. | A separate symptom that this Benchy comparison does not explain. | Describe the pattern and consult the exact model's diagnostics. Use the linked first-layer guide for that symptom; avoid a generic Z-axis repair recipe. |
Worked example: a supported match versus an unknown result
Hypothetical example, with illustrative measurements only: sample A is an upright Benchy printed directly on the bed without a raft. Its line is roughly 7.5–8.5 mm above the bottom. In the retained benchy-A.gcode, readable feature labels show sparse infill at 7.8 mm and solid top infill at 8.0 mm. That transition lies within the measured range, so classify the line as consistent with the documented Benchy explanation and review that explanation before touching hardware. These values are not thresholds or results from a physical test.
If only benchy-B.gcode from a changed profile remains, the same-looking preview cannot establish what happened in sample A. Record the comparison as unknown and recover A's file or seek support. Repeated bands elsewhere on the part also remain a separate observation.
Sample / original print-file identity: [ ]
Original exported file available? [yes / no; provenance]
Printer / firmware / slicer version / profile / material: [ ]
Orientation / raft or base offset: [ ]
Measurement reference and approximate line-height range: [ ]
Corresponding Preview range and mapping confidence: [ ]
Feature information: [readable / unknown; observed feature names]
Transition: [observed / absent in interpretable range / cannot establish]
Other symptoms, including repeated bands: [ ]
Decision and missing evidence: [ ]Use a photo only as supporting evidence
Inspect the file in the native Viewer first. For another person's help, attach a photo of the completed print and a screenshot or written description of the relevant Preview range; report your measurements separately. During repeated completed-print comparisons, an already connected MCP camera can provide a fresh still of each cooled sample from the same angle. LetItSee supplies requested images; it does not monitor the print, measure Z travel, diagnose a component, or adjust the printer.
Prompt to adapt
Use the attached photo and Preview screenshot or notes. If a current photo is needed and my MCP camera is already connected, request one still of the completed, cooled sample. Original exported file and provenance: [ ]. Printer / slicer / material: [ ]. Orientation and base offset: [ ]. Measured line-height range and reference: [ ]. Preview range and feature information: [ ]. Repeated bands or other symptoms: [ ]. Classify the comparison as a supported feature match, no match in interpretable evidence, or unknown. Explain the next decision and missing evidence. Do not infer a hardware cause or invent file contents, measurements, or a universal adjustment.
Source documentation
Set up without starting a capture
Set up your MCP client with the full tool reference. The separate capture page can replace the active capture page for your account. It does not take a photo by itself.