Question: How to Prevent Imported Components From Adopting Material Changes to the Same Component Already in the Model?

Quick question. Is there a plugin/extension or script that can be run that can make all components/materials completely unique? I’ll break it down below:

What I mean by this is, when I import a model into an existing model, that imported model sometimes shares components with the existing model. However there will be material differences between the two (One component will be colored brown and the other gray, per the example below:

Now, so long as I do some due diligence, this isn’t much of a problem (Exploding and re-creating components to make them 100% unique despite sharing everything but materials). Sometimes I forget to do that, though. Even though the two models above look almost completely the same outside of color, if you take a deeper look, you can tell the imported model on the right shares components with the non-imported model on the left, even though the components of the imported model should match the gray color:

When I import the model, I want the imported model’s material/textures to be completely separate from the existing model in terms of materials used, if the RGB value or texture file differs.

Is there any lazy man’s way of doing this, or should I just nut up and be more diligent in recreating the components? I’m slowly trying to make my workflow more efficient.

Thanks for any help!

Open it in a separate file and change the components so they won’t match the ones in the destination file.

1 Like

Gotcha. They are separate files already, and that’s pretty much what I’ve been doing (As long as I remember to do so). So pretty much sounds like staying the course is the way to go.

Yes. It does sound that way. An alternative would be to use groups instead of components but that could introduce other unwanted problems.

Yeah. I primarily use groups already, in a format that is like Arm Inner Frame Group + Arm Outer Armor Group = Arm Component. Though, I’m currently trying to move towards all parts being a component, though I’ve noticed it’s kicked up the file size a bit doing this, but that’s going off topic.

I’ll continue as I’ve been doing, then. Thanks for the input!

1 Like

There is also the intended feature that the default color used is more of a variable color when it comes to components. Any faces painted with anything other than the default color keep that color no matter what, but when you paint the outside group level of a component, that color is applied to the default faces in that instance of the component. Works well with really simple components, but nested ones get complicated.

All four jar components are the same (not unique). Left most is unpainted while the other three are painted different colors at their top level.