[BUG] <Seam transition catastrophic>

[mozgy]

Printer type - [MK4]

Printer firmware version - [5.0.0]

Original or Custom firmware - [Original]

Optional upgrades - []

USB drive or USB/Octoprint - USB flash drive

Describe the bug
Seam transition is catastrophic, way too late start of extrusion so huge gaps -

How to reproduce
Probably any combination of multiple objects with only one perimeter (like vase mode).

Expected behavior
Perfect print

G-code
Crash dump file
Video

[murk-sy]

This is likely not a firmware issue, but more related to gcode generation and material tuning.

You should provide a sample project so it's easier to check if it's actually reproducible on other machines (and ideally with a known material, specifically prusament).

[mozgy]

@murk-sy You might be right, resliced it with nonIS profile and quite a bit better but still not perfect

IssueWithMK4.zip
Should I reopen this issue in PrusaSlicer section ?

[darraghbr]

At least some of these parts appear to be a single perimeter thick, if that is the case you should be using spiral vase mode instead of a conventional print.

[murk-sy]

As a side note since you didn't mention the manufacturer, some white filaments can be more problematic to print than others. If other filaments print fine, it's just the white filament that may require some extra tuning.

[mozgy]

At least some of these parts appear to be a single perimeter thick, if that is the case you should be using spiral vase mode instead of a conventional print.

In case you did not notice, there are several models together on the plate as that combination shows the problem. Spiral vase mode works fine for single model. Since it works fine for nonIS sliced it is huge regression.

[mozgy]

As a side note since you didn't mention the manufacturer, some white filaments can be more problematic to print than others. If other filaments print fine, it's just the white filament that may require some extra tuning.

Apologies, it's Devil Design PETG (profile is in the zip in 3mf form). Nevertheless it's the very same issue with Prusament PETG Jet Black as well as Prusament PLA Jet Black. Only MK4IS profile shows it and exactly at the point where tool starts extruding after a long model to model travel.

[darraghbr]

At least some of these parts appear to be a single perimeter thick, if that is the case you should be using spiral vase mode instead of a conventional print.

In case you did not notice, there are several models together on the plate as that combination shows the problem. Spiral vase mode works fine for single model. Since it works fine for nonIS sliced it is huge regression.

I did notice that there is more than one part on the build plate. What you might not realise is that you can use sequential printing to print multiple objects in vase mode on a single build plate.

[mozgy]

At least some of these parts appear to be a single perimeter thick, if that is the case you should be using spiral vase mode instead of a conventional print.

In case you did not notice, there are several models together on the plate as that combination shows the problem. Spiral vase mode works fine for single model. Since it works fine for nonIS sliced it is huge regression.

I did notice that there is more than one part on the build plate. What you might not realise is that you can use sequential printing to print multiple objects in vase mode on a single build plate.

You're right, I could've, but 'Issues' section is about bugs and regressions not walkarounds hence specific setup ..

[FutureSharks]

I opened this issue for PrusaSlicer: prusa3d/PrusaSlicer#11914

Maybe it's the same issue? Not sure if it's a Slicer or firmware problem because they were both released and updated together in order to get the input shaper feature.

[GithubUser99999999]

still not fixed by Prusa

[github-actions]

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

[danopernis]

This is not a firmware bug. As already suggested, this could relate either to slicer or the material settings.

You can read more about this issue at prusa3d/PrusaSlicer#11914 (comment)