MMU Usefulness killing modifier bug in Slicer
 
Notifications
Clear all

MMU Usefulness killing modifier bug in Slicer  

  RSS
LewnWorx
(@lewnworx)
Active Member
MMU Usefulness killing modifier bug in Slicer

Modifiers are forcing unwanted color changes on geometry in Slicer 2.3.x (and likely most versions prior).

Any geometry either manually added in slicer, or brought in with the model import, when changed to type modifier, forces a color change on the rest of the model for the area it occupies, even though it's no longer a "printing" object.  This utterly destroys the ability to use the MMU's multi material capability if you have to have modifiers for any reason.   See Below:

So here's a model brought in via 3MF, manually renamed item by painful item (as Slicer utterly ignores whatever parts model names that had been assigned in the modeler before exporting to 3MF, another PITA Bug).   Note the two green blocks that were built in the modeler, had type changed to Modifier.

And here we can see the two blocks have had speed modifiers added.

And here we can see it's for the most part having the intended effect on the speed locally around the logo artwork.

However when I switch to Color  Print we see this:

The modifier has stomped on the real geometry's color assignment.   This is also viewable in tool view as well:

Is this just a slicer bug or does it actually force MMU filament changes in those areas as well in the GCode?  

I've opened a bug report on this 2 weeks ago but it hasn't even had a single look.   I was told filing bug reports in GitHub was the way to get stuff in the queue for fixes, but maybe not.  

Github Bug Report

Is there a workaround for this?   I'm using modeled in modifiers more and more to solve various printing issues so I don't have to baby-sit the prints by hand, but this kinna wrecks' havoc on the ability to use an MMU.

Posted : 03/03/2021 10:51 pm
LewnWorx
(@lewnworx)
Active Member
Topic starter answered:
RE: MMU Usefulness killing modifier bug in Slicer

Crickets...   Both here and on GitHub.

Anybody?

Posted : 05/03/2021 6:33 pm
LewnWorx
(@lewnworx)
Active Member
Topic starter answered:
RE: MMU Usefulness killing modifier bug in Slicer

Crickets still..

Can't believe I'm the only one who's ran into this.

Posted : 13/04/2021 10:23 pm
Neophyl
(@neophyl)
Famed Member
RE: MMU Usefulness killing modifier bug in Slicer

Don't have an MMU so don't have any input into your issue.  The only comment I will make is that many people don't seem to realise there is a specific Slicer section down here at the bottom of the forum, you know below the MMU specific forums further up lol.  While I'm not a big fan of posting in multiple places, in this case it might make sense to post in the MMU section.  It stands to reason the people who frequent those sections are far more likely to have an MMU.

Posted : 14/04/2021 6:58 am
LewnWorx
(@lewnworx)
Active Member
Topic starter answered:
RE: MMU Usefulness killing modifier bug in Slicer

@neophyl

FWIW, after I originally posted this, and realized I’d put it in the wrong place, I reposted it IN the slicer sub forum and tried to delete this one as I didn’t want to do the multiple post thing,  and couldn’t.   So I notified the mods to delete this one and they instead deleted the one in the slicer sub forum.

 

I also posted this as a bug report in the Github as well, and it’s had literally zero views.

I tried, I really did.

This post was modified 8 months ago 3 times by LewnWorx
Posted : 14/04/2021 1:56 pm
Share: