Object Intersection to Painting

So you can (currently)

  • Hand Paint on Objects
  • Pant an SVG onto an object (rarely works… Open Object errors in 90% of valid SVGs)
  • Add a Modifier object to an Assembly, with a Different Spool

These all work, and I use the Modifier object the most.

But I just got a set of 3, 0.2 HotEnd set, for more detailed prints… which are all multi-color

My normal Modifier object’s are embedded into the parent object by 1.2m on average to get three layers of color with my normal 0.8 HotEnds.

The problem is when I print this way with a 0.2 HotEnd, I get 17 layers of color. And thus x6 times the fillament changes… I.E. slow and waist full.

I could edit/move all the Modifiers to a lesser ‘depth’, but then they would not be correct for 0.8

The Proper solution seems to be “Paint Penetration Layers” if set to 3 would be three thick regardless of HotEnd, keeping the Filament Changes down.

The Problem there is no way to turn a Modifier-Body interaction to a paint on said body.

So my Request is for a Feature to do so

Much like the Join tool, you would select the two objects, and a ‘paint’ Spool. The Join’s mate-surface would be added to the current Assembly’s Paining setup, just as if you hand drew it.
Additionally an option to delete the Modifier after paint would be handy.

Like my other post, multiple Selection of Modifiers (in the same assembly) to do lots of painting at once would be appreciated.

OR :thinking:

Make another “Object Type” => “Paint”

This would retain the object, who’s only job is to paint surfaces it comes in contact with, and the same Join-Surface would be treated as a Paint, and thus following the paint settings.

Really just a “Modifier” object with the concept of Depth removed.

I like this one better as it would allow for latter easy movement/scaling/rotation of painted designs. And is much closer to how most people currently add colors to a project, just more powerfull, than a Modifier.

1 Like

You took the long route on that explanation (as I often do), but it landed.

Seems reasonable, but you should understand that it is unlikely to be a high priority, as the number of users needing it is likely less than other feature requests.