Color Painting: weird spreading of colors

Let’s take a simple nameplate like this:

I’m using two colors here: the plate (6 Layers) should be black with only the top layer beeing red. So I use the color painter->select “Height Range”->Color red. Same for the “Fill” method btw.
After slicing the result, it looks like this:

Instead of just having one color change, I now got 6 changes in each layer with random color spreading in the object. There is no other object, so nothing related to some kind of “cleaning the nozzle inside the object” or so.
BS just doubles or triples the printing time without any need.

I know, that I can change the color on a specific layer, This is what I did to solve this particular problem. But I really want to be able to change the color in a way “I” want to.

Btw. for that special nameplate I need 2 color changes from black (2 layers black for the text), one white layer - to get a bright layer - before switching to 3 layers of the top color. Without that white layer, e.g. yellow went to a dirty dark yellow. So I need that color control!

The haphazard distribution of colors within the object simply makes no sense to me. Is that a bug or a weird feature, I didn’t understand?
Or is it possible to deactivate that?

Your model looks small.

Because of this, the slicing appears to blend the colours from black to the surrounding areas.

The “height range” doesn’t restrict the depth of the painting, it restricts the selection area it detects that you are about to fill.

There are a few ways you can try to get this better.

  1. Change the Wall Generator (in the global settings panel) to Archane mode

  2. If you made the design, create the red portion as a distinct object from the black portion.

    Import both at the same time (select both and drag them to the window)

    Say yes when you are asked if they are the same model and should be merged.

    Use the objects view in the settings panel, select the model’s black portion, and change the thumbnail swatch to black. Repeat for the red portion.

    Your model will now contain distinct colours.

Important

Only one single layer of 0.2mm tall red is not very much, the materials at that thickness are more translucent, and you will find 0.6-1mm will be needed dependant on your filament brand. to obtain an opaqueness.

1 Like

Hi @MalcTheOracle,

you missunderstood my request here :wink:
I don’t need a solution for my nameplates. I already found an easy way to reach my goal here, by also taking the translucent issue into account (described in my post).

20241227_085234

My question is only, if there is a way to disable that “feature” (I guess not).
Maybe a software developer will read this and creates a feature request for it? :wink: .

I did some tests with a 100x100 mm cube and yes, on the top side “only” 5 layers will be blended. If you color the front side, that blending goes thru the middle of the object. So it’s not even consistent.

I can’t see any sense in it. It contradicts exactly my goal to take the transparency of the filament into account. It leads to unneeded and unwanted color changes and increases the print time by factors.

You described a problem and wanted a solution.

I gave you solutions.

Turns out you didn’t want solutions, you think there is a problem with a feature you don’t understand.

I explained your misunderstanding with a feature isn’t a bug, it is you not understanding what it means.

You don’t care and want something that isn’t broken to be fixed.

Just because you don’t understand it, doesn’t mean it is wrong.

If you wanted to do it correctly, you would pick my second solution.

The problem you found isn’t a problem, you simply misunderstood the purpose thinking it does something else.

You described, what happened if I use the “Height Range” tool, that the “depth” will not be restricted. I understand that, but do you know, why it is working like this?

Don’t get me wrong, I like your second workaround. It’s time consuming but will work for simple objects. But my solution and yours have strict limitations.

I’m pretty sure (as a software developer), that the developer of that painting tool is “coloring” the whole layer and not only the surface.
You can verify it by entering holes in your model. That weird color spreading comes from the slicer.
I guess, that developer just failed in translating all the color information from the painting tool into the complex slicer code and just wanted to ensure, that the color is at least correct at the surface.
No blaming to that developer, it is complicated and I guess he or she didn’t get enough time for the perfect solution (unfortunately we developers never get enough time for perfect solutions). :wink:

But even if it somehow makes sense to do it the current way, I’d just like to suggest having a checkbox to deactivate it and do the coloring in a way that I (and I guess most of us) would expect here.

1 Like

Malc has kindly offered some possible solutions (workarounds). You’ve declined them, though you expressed some level of interest in the second. Perhaps it would be preferable for you to address your questions directly to Bambu, by opening a ticket?

I explained this.

It doesn’t do what you think it does, that doesn’t mean it is doing something wrong.

It is restricting the potential selection p, it doesn’t limit the amount of paint depth.

There are zero restrictions, this is the way you define the exact colour location at the design stage.

The painting tool takes a model without colour designed into and attempts to do a good job, it is guessing at best.

It is doing exactly as it is designed to do.

I am not part of “most of us” as I know how it is meant to work.

@MalcTheOracle
Let’s just say that I have other requirements and would like to have complete control over the color depth in the slicer. Just because I can’t control them in Fusion360 without binding the model to fix extrusion widths and heights. Not to mention complex shapes and angles.

@drakko
I’ll see if I can open a feature request for it.

Thank you both for the information!

1 Like

A half years ago, I adressed that issue at GitHub. Unfortunetaly without any reaction from Bambu side.
You can maybe upvote it.