One instance color change good. Three instances color change didn't happen.
 
Notifications
Clear all

One instance color change good. Three instances color change didn't happen.  

  RSS
scaldinghotcarl
(@scaldinghotcarl)
Active Member
One instance color change good. Three instances color change didn't happen.

I was printing some coasters out and the first one to check the layer-height-color-change. The color changed right where it was supposed to and everything went well.

However I went back in and added two more instances in slicer and the message at the layer change is: "Note! G-code associated to this tick mark is in a conflict with a print mode. Editing it will cause changes of Slider data.

So the problem is that even though it was rendered in two colors in slicer it never printed the second color on the machine. My question is how can I have several instances of the same object, each a different color, but topped off all with the same color?

Posted : 04/09/2021 4:42 pm
scaldinghotcarl
(@scaldinghotcarl)
Active Member
Topic starter answered:
What I've tried

I've tried slicing each coaster and setting the color change at the requested height, then saving that as a 3mf file, each with it's own base color and common top color. I opened a new project and imported all three 3mf files. It rendered them all correctly and then discarded the color change. I sliced that and saved it as gcode. I opened that gcode file to see if there was a color setting for all four colors, but alas, there was not. So why does slicer ignore my color changes in each object rather than treat them all as separate objects and leave the color change intact?

Posted : 04/09/2021 5:21 pm
PrintDaddy
(@printdaddy)
Active Member
RE: One instance color change good. Three instances color change didn't happen.

Did you ever figure this out?  I wonder why it is making this such a PITA.  I cannot believe I have to figure this out.

Posted : 06/11/2024 11:54 pm
Share: