Autodesk Materail

[hoppergrass]

Pretty pricey, however, it works for me all the time.

https://3dstudio.nl/webshop/product/...rial-converter

We have one license of that converter, so it means we have to interrupt that person to convert scenes for the rest of the team which is not ideal, so we only do it for large models. For simpler models its easier to do it manually.

[iancamarillo]

use corona converter, then vray converter

[hoppergrass]

giving it a try now thanks

[hoppergrass]

Nice, works quite well. Still would be good if Vray could do this in one step

[glorybound]

Well, at least we know that it can be done. I am sure the V-Ray guys can by a round a beer and get the code from the Carona guys.

[hoppergrass]

one more to add to the list, those god awful "Pro-materials" from Revit

[gandhics]

From that thread, it'd seem to me that the AD scene converter (ie. the one i linked above) should be able to convert AD materials into V-Ray ones.
Or am i wrong?

It is open framework which 3rd party can use.
Chaosgroup need to make 2vray portion.

[^Lele^]

Unless I am missing something, Vray materials are not listed

You can convert them to standard, then use the VRay Scene converter to convert to V-Ray ones, can you not?
Agreeably, is a two-step operation when it really ought to be one.
You can also convert them to AD Physical materials, and be done (we translate those internally).

[glorybound]

I received a large Revit model yesterday with a ton of Autodesk materials. The UMC converted the whole scene, with all it sub-materials in seconds.

[hoppergrass]

You can convert them to standard, then use the VRay Scene converter to convert to V-Ray ones, can you not?
Agreeably, is a two-step operation when it really ought to be one.
You can also convert them to AD Physical materials, and be done (we translate those internally).

This is the method I use already, its OK, in that it works to get a simple conversion.
There are a few catches though, when converting standard to vray, quite a few of the BDRF's are set to Phong, reflection HGlossiness is unlocked, Glossy Fresnel is off among others. So it requires a third step of using VMC to mass convert those settings.

Once again it would be so much easier if Vray could do this natively without relying on expensive plugings (UMC or Corona)

[hoppergrass]

Are all features of the AD Physical materials supported translated 1:1 by Vray?

[Nicinus]

I received a large Revit model yesterday with a ton of Autodesk materials. The UMC converted the whole scene, with all it sub-materials in seconds.

I can't seem to get UMC to work with 2020, has anyone tried? The latest version I have is June 28, 2018.

[^Lele^]

Are all features of the AD Physical materials supported translated 1:1 by Vray?

I missed this post, sorry.
No, the physical material has limitations we do not share, and it's different in a few areas.
You are right stating conversion works only for simple stuff, but there is no way V-Ray (or any other renderer) could get around all the issues.
There truly is no magic to this: it's a standard dictionary translation, be it done in scripting or at rendertime, with or without third-party standards as guideline.

[hoppergrass]

How does it work with Vray for Revit? the conversions seem to happen on the fly with out the user having to do manual conversions.

[^Lele^]

It's a dictionary conversion: they write "color" we read it as "diffuse" and so on.
It just happens implicitly.
I'm talking of not being able to match BRDF implementations exactly (some cap glossiness, some have a different gloss multiplier, others entirely different models, we support the whole of the GTR shading domain, most only GGX and on and on and on the list goes...), SSS models, and even volumetric features.
And by match, i mean per pixel, exact.
Some result is always somewhat available (i can plug a texture into the right slot n.p.), it's just what the result will look like which bothers us.
The exact same is valid for *any* conversion, thereby including Corona and the Physical Material Zap created for max.
Models can't be easily adapted, if at all, in between engines and we could be here until the cold death of the universe debating which implementation is the right one for some features (we do it right. no WE do it right!). ^^