Simplify3D User Forum

I'm kind of at my wits end with this, I feel like I've perturbed just about every setting in the profile to see about changing this, I've changed the extrusion width, I've change the nozzle diameter, I've changed this, that, rafts, no rafts, temperature, thin walls, I've redownloaded the part, I've moved it places on the bed, I've restarted the computer, I've loaded different .fff presets I have, and I cannot figure out why this very straightforward calibration cube from thingiverse is not slicing correctly?

No model file to check, no factory file... so I'll have a guess based on the pictures:

Missing walls etc. can be caused by broken model files/errors within the model.
But looking at the perimeters I wonder if settings regarding coasting/wiping are causing this?

Missing walls usually don't result in things like the outer but not the inner perimeter
showing up in the sliced result. Things might be different with v5 and its different repair
algorithms, though. Not using v5, can't say much about that. Did you test the various modes
and if they make a difference?

Blue perimeters on the back in the pictures aren't deep blue as the single extrusions on the "X",
so I'd check for coasting/wipe etc. first.

Edit: Extreme coasting/wiping creates results not so far off, depending on start point location. I'd
recommend adding a factory file so others using v5 are able to have a look at the settings.

Yeah, this is almost certainly caused by a very large Coasting Distance value.

Could also be an issue with relative vs absolute E-values in the gcode. If the starting script accidentally puts things into absolute mode, but the process settings are set to use relative E values, you sometimes get missing segments like that. Checking the flow rate preview coloring mode should make it clear if this is what's happening.

S3D-Taylor wrote: ↑Fri Nov 01, 2024 3:21 pm Yeah, this is almost certainly caused by a very large Coasting Distance value.

This happens even with coasting disabled.

S3D-Jason wrote: ↑Mon Nov 04, 2024 9:18 am Could also be an issue with relative vs absolute E-values in the gcode. If the starting script accidentally puts things into absolute mode, but the process settings are set to use relative E values, you sometimes get missing segments like that. Checking the flow rate preview coloring mode should make it clear if this is what's happening.

Disabling the option Relative Extrusion Differences resolved the behavior of the slicer preview thank you. Will test these prints

In that case, you should check the Scripts tabs for G90/G91 or M82/M83 commands, since there was probably an errant G90 or something that was putting everything back into absolute mode even though the old process settings were configured to use relative extrusion distances.

having the same issue
No problems with CURA though!
WHY WHY
Please help, There must be something I'm missing

This looks more like an issue caused by a bad mesh. Try going to Edit Process Settings > Advanced > and set the Slicing Region Repair Mode to "Alternating Fill". Positive Fill works best for most models, but there is not a single setting that will work for all types of mesh issues. You can learn more here: https://www.simplify3d.com/resources/ar ... sh-errors/

gigiespresso wrote: ↑Fri Dec 13, 2024 1:02 pm having the same issue
No problems with CURA though!
WHY WHY
Please help, There must be something I'm missing
1.jpg
2.jpg
3.jpg

I had the issue crop up again on a new model and a different process and can reaffirm the solution here was to change the extrusion gcode

Go to the settings for the process and disable "Use Relative Extrusion Distances" in the Outputs tab, under the section 'General.'