Common Cura Slicing Errors: Missing Layers and Retraction Blobs

Issue #1: The Phantom Gap Missing Layers & Slicing Artifacts That Wreck Prints

You slice a part, preview looks fine, but when the print finishes there's a gap in a wall, or a shelf that didn't print. First reaction is always hardware loose belts, z-hop, nozzle clog. Half the time it's not. It's the mesh.

STL files from CAD often have non‑manifold edges, inverted normals, or tiny holes that Cura's "Union Overlapping Volumes" just doesn't catch. I've seen this on parts from beginners and pros alike a complex bracket from SolidWorks that looked perfect in the preview, but sliced into a Swiss cheese bottom layer.

My workflow for fixing this:

• Run the STL through Netfabb or Microsoft 3D Builder first. I don't trust Cura's built‑in fixer for complex geometries. 3D Builder's "Import" + "Save as STL" often cleans up hanging vertices without destroying dimensions.
• Enable "Remove All Holes" in Cura's Mesh Fixes tab but only if the object is supposed to be solid. For thin‑wall parts, use "Keep None" and then manually add holes later.
• Set "Max Triangle Count" to 0 (unlimited) and lower "Mesh Fix" to a low resolution like 0.1 mm for the first pass. This makes Cura spend more time on edge analysis, but it catches more errors.

One trick I learned the hard way: if the gap appears on the same height every time, export the STL again with a different tolerance in CAD. A 0.01 mm shift in a vertex can cause the slicer to treat a surface as two separate planes. I had a production run of twenty parts that all failed at 14.5 mm height. Re‑export with "angular tolerance" set to 15 degrees instead of 10 fixed it immediately.

Issue #2: Retraction Madness Stringing, Blobs, and the Profile That Won't Calibrate

Cura's default retraction settings are a gamble. For a Bowden tube printer like an Ender 3, they push 5 mm at 45 mm/s which might work for one filament and give a spiderweb for another. The real nightmare is people who tweak retraction without understanding the cooling interaction.

I once spent a week fighting a CR-10 that oozed during travel. The user had changed retraction distance from 4 to 6 mm, thinking further is better. What happened: the molten filament got sucked up into the heatbreak, cooled, and then blocked the nozzle. Next layer started with a huge blob. Cura doesn't warn you about over‑retraction.

My no‑nonsense calibration workflow:

• Start with a temperature tower. Stringing often disappears just by dropping temperature 5°C. Run the Teaching Tech stringing test g‑code (it's a simple 5 mm gap at different retractions).
• Use Cura's "Extruder Calibration" plugin only for flow. For retraction, I write my own g‑code snippet with M207, M208, and M209 (linear advance on Marlin). Manual control beats any slicer wizard.
• Set retraction prime speed to 20-30 mm/s Cura defaults to 45, which causes cavitation in the melt zone. Slower priming refills the nozzle chamber without bubbles.
• Enable "Wipe Before Retract" and "Retract After Wipe" these two options stop the hot end from pulling a string across the part. I set wipe to 0.5 mm offset.

One hack that saved me hours: for PETG, I use a retraction distance of only 1.5 mm on a direct‑drive toolhead. Cura's default profile would give 4 mm. I once ignored this and got a print with tiny blobs every 3 mm. Turned out the retraction was so aggressive it was pulling air into the nozzle. Fixed by going to 1.2 mm and turning the speed down to 25 mm/s.

Issue #3: G‑Code Travel Paths That Collide The "Ghost Move" Nightmare

You watch the preview everything's fine. The print starts and the nozzle crashes into a printed feature during a travel move. Or it zig‑zags across the part, leaving a thin string of filament on the surface. This is Cura's travel optimization going stupid.

The worst case I saw: a large vase with a spiral outer wall. Cura decided to add a travel lift every layer inside the vase, dragging the nozzle across 20 mm of open space. On the first layer the nozzle caught the edge and pulled the whole print off the bed. Took me three prints to figure out it was the "Z Hop When Retracted" setting combined with "Combing Mode: Not In Skin".

My field fixes:

• Set "Combing Mode" to "Infilled Layers Only" this keeps the nozzle inside solid infill but prevents it from flying over open gaps. For cosmetic parts, use "No Combing" and accept a little stringing.
• Increase "Max Comb Distance With No Retract" to 20 mm forces Cura to plan longer combing moves without retraction, reducing the number of lifts.
• Disable "Z Hop When Retracted" for prints with overhangs. The hop often clips the previous layer. I only enable it for very tall, skinny parts where a jam is more likely than a collision.
• Use "Avoid Printed Parts When Traveling" this does exactly what it says. The trade‑off is slightly longer travel time, but I've never had a crash with it on.

One more thing: Cura's "Maximum Resolution" setting. If you set it too low (e.g., 0.5 mm), the slicer simplifies the travel path and may drop the combing constraints. I keep it at 0.25 mm for most parts. Higher values produce smoother moves but more aggressive travel cuts.

Community Solutions That Actually Work Not the Forums' Favorites

I've seen people recommend "just re‑install Cura" for every problem. That rarely helps. Instead, here's what I've seen fix real headaches:

• Disable "Enable Acceleration" and "Enable Jerk Control" if you have a Marlin board that doesn't support M204/M205 properly. Cura writes values that can cause step skipping.
• Lower "Build Plate Adhesion" type to "None" for mirror‑like first layers. The skirt often interferes with the purge line and causes a partial clog.
• Use "Relative Extrusion" (M83) in the start g‑code absolute extrusion (M82) can cause drift over long prints because of rounding errors in integer g‑code. I've tested both on a 48‑hour print; relative gave consistent flow, absolute drifted by 0.3% over the run.

The biggest myth I see: "Cura's default profiles are optimized for each printer." They are not. They're a starting point. The Ender 3 profile in Cura 5.7 had a jerk setting that caused layer shifts on a stock board. I had to reduce it from 20 to 8 mm/s to get clean corners. Don't trust the defaults.

When All Else Fails The Nuclear Option

If you've tried everything and Cura still produces bad g‑code, reset the application data folder. I don't mean re‑install I mean delete %APPDATA%\cura (Windows) or ~/Library/Application Support/cura (Mac). Corrupted material profiles or a bad plugin can screw the slicing engine silently. I've done this twice in five years, and both times it fixed weird extruder temperature fluctuations and invisible layer shifts.

Back up your custom profiles first. And accept that Cura, like any tool, has its limits. For production work, I now keep a copy of Simplify3D on a virtual machine for those complex parts that Cura just can't slice correctly especially with variable layer height across curved surfaces. Cura's adaptive layer height is getting better, but it still over‑segments on steep slopes.