Tool to update old material libraries to v6 standards

[kosso_olli]

What is the reason that the resulting .mat file is much smaller after running the script? (3.6mb vs. 2.4mb)

[^Lele^]

I don't quite know.
The methods i use are Max's own (i.e. saveMaterialLibrary).
If the materials are all there, then it's possibly because of versioning the file up (assuming the format got more efficient.).
If they aren't, then perhaps there is some error in my code, and i'd love to have said matlib (no textures needed).

[kosso_olli]

Is there a quick way to get the number of materials inside a mat file?

[^Lele^]

Run the attached script.

[kosso_olli]

The script says they're matching. So indeed the matlib files seem to have been modified to be smaller in size.

Regards and thanks again for both of the scripts.

Olvier

[Pixelcon]

Any chance of converting old normalmap maps to vraynormal maps too?
And perhaps setting the bump amount to 100, taking whatever that number was, dividing by 100, and using that as the normal map strength in the newly created vraynormal map?

Or are we getting a bit too involved here?

[^Lele^]

Eh, touching map influences and such gets sketchy quickly, but if it's the same thing the standard scene converter does (i.e. from legacy max to v-ray), i can likely add it in without too much worry.

I'll look into this in the coming week.

[Pixelcon]

Quick feedback: Seems to break when there's a map in a .mat

[^Lele^]

mh, thanks for the report, will fix this.

[^Lele^]

It's fixed, v006 has been updated in the OP.

[Pixelcon]

It's fixed, v006 has been updated in the OP.

Thank you

[^Lele^]

You're welcome.
Notice that lone bitmaps in material libraries will be skipped, however, for conversion to vrayBitmap.
I'm trying to think of a good way to process them, but hopefully skipping them isn't an issue.

[^Lele^]

Script version 0.07 adds the resetting of map coordinates' blur to 1.0 (only works on Max files treated as scenes. Won't touch matlibs.), and also turns on the new anisotropy model along with Energy conservation (the highlight will not turns into anisotropic, however.).
There is also a fix for a potential corner-case bug (that was not reported, however.).

Script and screenshots have been updated in the OP.

[Pixelcon]

Script version 0.07 adds the resetting of map coordinates' blur to 1.0 (only works on Max files treated as scenes. Won't touch matlibs.), and also turns on the new anisotropy model along with Energy conservation (the highlight will not turns into anisotropic, however.).
There is also a fix for a potential corner-case bug (that was not reported, however.).

Script and screenshots have been updated in the OP.

Thanks. Is the new anisotropy the new default? Also is there really any reason to use anything other than the default other than for legacy support?

[^Lele^]

It is the default for newly created vrayMtl, yes (that's why is UI-less).
It's superior to the old one (this one is physically accurate, and works for the whole GTR BRDF), for analogous performance, so i wouldn't bother with the old at all.