Weird wipe tower behavior for 0.3mm layer prints with supports
 
Notifications
Clear all

Weird wipe tower behavior for 0.3mm layer prints with supports  

  RSS
gnat
 gnat
(@gnat)
Noble Member
Weird wipe tower behavior for 0.3mm layer prints with supports

So I have a 0.2mm print that is going to take over 2 days to print and I figured that 0.3mm would be fine for this case to knock some time off. PrusaSlicer doesn't cooperate though.

When I slice for 0.3mm without supports, the wipe tower looks correct. If I add the supports (from build plate or just for support enforcers), however, the tower is suddenly about 10x the length of my Y axis and most of it is uncovered sparse layers. If I turn sparse layers off it is still just as long, but it's about half the height. If I switch back to 0.2mm layers, the wipe tower stays the same size with supports enabled or disabled.

I haven't done exhaustive testing on this yet, but it does happen with two similar (but different) models. Anyone else seen this? Know of a fix?

MMU tips and troubleshooting
Posted : 01/10/2020 2:57 pm
gnat
 gnat
(@gnat)
Noble Member
Topic starter answered:
RE: Weird wipe tower behavior for 0.3mm layer prints with supports

Now with pics

0.2mm with supports:

0.3mm with supports:

0.3mm without support:

MMU tips and troubleshooting
Posted : 02/10/2020 2:13 am
gnat
 gnat
(@gnat)
Noble Member
Topic starter answered:
RE: Weird wipe tower behavior for 0.3mm layer prints with supports

And here is what the wipe tower looks like zoomed out to see the whole thing.

MMU tips and troubleshooting
Posted : 02/10/2020 2:16 am
gnat
 gnat
(@gnat)
Noble Member
Topic starter answered:
RE: Weird wipe tower behavior for 0.3mm layer prints with supports

An entirely different model doing the same thing:

MMU tips and troubleshooting
Posted : 02/10/2020 2:22 am
gnat
 gnat
(@gnat)
Noble Member
Topic starter answered:
RE: Weird wipe tower behavior for 0.3mm layer prints with supports

Searched GitHub for a similar report, but didn't find anything so I submitted a new bug. Apparently there are already a handful of similar reports and the bug is supposed to already be fixed in 2.3.0.

MMU tips and troubleshooting
Posted : 02/10/2020 5:58 pm
Share: