[Plugin] MaterialConsolidator

SirFievel33

Returned to these error messages within Ruby Console (I'm using Sketchup Pro 2019)

Material Consolidator: Tolerances: R=15 G=15 B=15 A=0
Material Consolidator: Making Material Lists
Material Consolidator: Making Entities List
Material Consolidator: Making Nested Entities List
Material Consolidator: Consolidating Materials
Error: #<NoMethodError: undefined method display_name' for nil:NilClass> C:/Users/###/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/materialconsolidator.rb:202:in block (3 levels) in new'
C:/Users/###/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/materialconsolidator.rb:195:in each' C:/Users/###/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/materialconsolidator.rb:195:in block (2 levels) in new'
C:/Users/###/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/materialconsolidator.rb:191:in each' C:/Users/###/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/materialconsolidator.rb:191:in block in new'
C:/Users/###/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/materialconsolidator.rb:189:in each' C:/Users/###/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/materialconsolidator.rb:189:in new'
C:/Users/###/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/materialconsolidator.rb:71:in `block in module:MaterialConsolidator'

TIG

I see the issue and will issue an update shortly...

TIG

Here's v4.0
https://sketchucation.com/pluginstore?pln=materialconsolidator
It should fix the display_name error for nil-materials...

valerostudio

Is it possible to get some kind of progress bar with this plugin? I usually use it toward the end of a project, where I have imported a bunch of components and have a lot of materials. I ran this yesterday and I wasn't sure if SketchUp had crashed or it was still working. I let it sit overnight and it was just working away. It would be nice to know how far it has to go. Thomthoms Cleanup does a great job of doing this.

TIG

The Ruby Console lists the key stage of its operation - open it before you start.
The bottom status_bar has a incrementing '...' to show it's doing something...
It also reports the key stages of operation...

melindasaur

First of all THANK YOU SO MUCH for this! This is saving me so much headache already.

It's not working for a couple of materials in one of my files. It WILL work in a new project if I apply those materials to surfaces and paste them in a new project... do you know why this might be? ie maybe it doesn't work with components?

2019 file attached

materialconsolidator-componentnotworking.skp

Tom0212

Hi TIG,
When I use the tool, it isn't doing anything..
Materials stay the same, and a consolided image is not added to my materials list.

Running Sketchup 2020.

TIG

Are you sure you understand its usage...
I just retested it in v2020 and it works fine.

When you run it it asks if you want to set RGBA 'tolerances'.
If 'No' then only materials which share the exact RGBA values are processed.
If 'Yes' then you can set a +- range of values - e.g. all materials sharing the same RGB but with a varied A[lpha] transparency will be consolidated.

Assuming some material matches are found, then it takes the first material in the list [alphanumerically] and makes that the 'base-material', then it replaces any other matching materials in the model's entities and within groups/components, with that 'base-material', and then it purges those now unused materials from the model...

Run it with the Ruby Console open to see the report...

Tom0212

Hi TIG,
I'm not quite sure I used the tool correct.
Please review my attached .skp file.

Not-consolidating.skp

TIG

In your example SKP the two materials use widely different RGB values, but these can be consolidated by giving a suitable range in the dialog.
However, they use different texture image files with different image-scaling etc, so they are seen as so different that they are not able to be processed...

Materials using textures can be consolidated, but only if the two materials use the same texture-file-name and they have the same image_height/width, and use the same texture-height/width settings.
Otherwise they are not merged into one, as they are too different...