Tool to update old material libraries to v6 standards

[Pixelcon]

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.

I'm not sure I follow. Is the new anisotropy "replacing" the existing 'Microfacet GTR (GGX)' option?

[^Lele^]

Nope, it is new math to render anisotropic highlights for GTR (or GGX, which is a special case thereof.)

[Pixelcon]

Nope, it is new math to render anisotropic highlights for GTR (or GGX, which is a special case thereof.)

So where to find it (I'm a bit confused by you having said its UI-less)? Or is it not part of a stable-release yet?

[^Lele^]

When a new shader is made, the BRDF is GTR/GGX, and anisotropy amount is higher than 0.0, then the new math is used.
Old shaders keep using the old math for anisotropic highlights.

It's been surreptitiously introduced in v5.2.

Improved anisotropy for the V-Ray material;

[kosso_olli]

along with Energy conservation

Any ETA for the full energy conservation which also covers refraction? Would be really handy because it makes frosted materials so much more believable.
Also, can the script handle materials with different values for specular and reflection glossiness (yes, that was a thing back in the day, and some materials carried these over into our libraries, causing a warning when rendering).

[^Lele^]

EDIT: nevermind, multiple bounce still darkens.
No ETA, nope.

[indelague_sa]

Hi guys.
After using this script, whenever I save a new file and then open it, the preview of the material in the Material Editor disappears. See attached image.

Can you help, plz?

Best regards.
Joao Pinto

[^Lele^]

I can reproduce this, many thanks for the report, and very sorry for the inconvenience.

EDIT: it has nothing to do with the script, apparently.
Reset max, Save to a new file, reopen it, the material previews are gone.
Resetting the material editor doesn't help then.

[Vizioen]

It's a bug with 6.2 update.

[^Lele^]

It's a bug with 6.2 update.

correct, label is VMAX-13765

[glorybound]

Yes, a huge bug!

[dimitar_panayotov]

...But it's solved with today's build.
https://forums.chaos.com/forum/v-ray...53#post1196853