PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?  

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

Expected. It’s been reported as a bug so many times on the Prusa slicer GitHub and every time it’s closed as it’s designed to do that. I’ll see if I can find the post later and link it here. 

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

FAQ here https://github.com/prusa3d/PrusaSlicer/wiki/Frequently-Asked-Questions-(FAQ)

https://github.com/prusa3d/PrusaSlicer/issues/1355   

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

That would be great if you can find it. The floating part ends up being extruded onto the top of the wipe tower like a messy little bird's nest. I'd love to hear the rationale for wasting filament... 😆 

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

The layer above the cleaning tower has been there for a long time. This is not a waste of filament, the same procedure is used to shape the tips of the filament when changing color before pulling back into the MMU and during lower layers of color change.And if there were color changes up to the total print height, you wouldn't even notice it. This is how it goes into the air, because the extruder cannot return to the last height of the cleaning tower.

RE:

If I'm reading the posts correctly, the extra filament purge is called 'ramming' and it's intended to shape the end of the filament prior to pulling the filament back into the mmu. Thanks for pointing me to the info, Neophyl and miroslav.h4

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

Why on Earth hasn't this been fixed? Bambu Labs' version of this slicer doesn't have this problem. Prusa needs to find out how Bambu fixed this.

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

Did you not read the earlier posts and links. It’s not been “fixed” because it is designed and supposed to do that. You may not agree with that decision but that’s the one PRUSA have made. You can always use Bambu slicer if you think it’s superior. 

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

Yes, I read all posts, but making spaghetti is not acceptable in 3D printing (unless you want to make spaghetti). Bambu's slicer and Prusa's slicer are both modified versions of the Slic3r slicer -- they are identical except for the GUI layout (and Bambu's doesn't make spaghetti after the final layer).
There's no good reason to dump filament into the air -- very bad practice! Easy fix would be to simply have it purge the last filament onto the purge tower during ramming, like it does on each filament change. That's what it's there for!

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

In your opinion.  And that's all it is, an opinion.  Everyone has them.   

Also your statement has at least one untruth in there.  Slic3r and PS are NOT the same.  The code base was completely re-written in a different language when prusa changed from Slic3r PE (Prusa Edition) to what they currently use now.  There's very little you can directly copy from one to the other.

Also the lineage is Slic3r>Prusa Slicer>Super Slicer.  After that Bambu Slicer forked PS and also used some of the Super Slicer code.  Then deliberately changed it so the files weren't compatible any more.  Orca did a similar thing and built upon Prusa, SuSi and Bambu. 

That's the great thing about open source.  If you don't like how it works you can modify it yourself and change it to make it just how YOU like it.  Put your money where your mouth is, or in this case your time and effort.  I don't know,  if you have enough money you could pay for someone to make the changes for you if you dont want to make the personal effort.  Guess that's what Jo Prusa has done. And we all benefit from it.  Including Bambu.

I'm sure Prusa will be heartbroken if you choose not to use their free software lol.

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

It can be fixed. I repeat my original question: Why on Earth hasn't Prusa fixed this MISTAKE? It IS a mistake. It's sloppy!

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

Prusa could easily solve this by continuing the Purge tower to the finishing height but normally the purge tower finishes before the model is full height  to save filament. most people would like to save filament and removing the small amount of poop, caused by the final tip forming actions before the MMU unloads the filament .

regards Joan

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

Again thats just your opinion.   Its working as Prusa want it to work.  Not an error, not a mistake.  By DESIGN.  Go open yet another duplicate issue on the Prusa Slicer github if you disagree with them.  I'm done with wasting time on people who wont accept that the world doesn't revolve around them.

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

Prusa Slicer generates and error message about the final layer (in screen capture the top layer is 220), so if Prusa Slicer says it's an error, and you say it's not, then who shall I believe?
Yeah, the world revolves around me! WTF? Not helpful!

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

I have MMU3 and I don't get that message for the post print purge, however if there are multiple STL's on the top layer, then that is a possibility, could you please provide the offending .3mp project file, for us to try?

regards Joan

RE: PrusaSlicer 2.9.0 multimaterial prints have an unattached layer floating above the wipe tower?

Provide me with a .3mf which exhibits this issue that I can replicate, and I Will escalate the issue

regards Joan