modo procedural support

[vladimir.nedev]

What I mean by this is that on the primary workstation (and the OpenGL viewport) the artist is working with native procedurals. But as soon as they fire off a render, the C4D native procedurals are baked to textures on the fly (and I would suppose cached somewhere). If the camera view is changed the procedurals are re-baked and sent to the DR nodes. I'm working from memory here, so I'm sure Stefan can provide more info if he's still reading this thread.

That would be quite impressive, if the baking of the procedural textures somehow takes into account what part of them is currently visible.

Greetings,
Vladimir Nedev

[jonmoore]

Yes, it will read it.
If you want to see the scene that V-Ray for MODO creates internally, you can go to File -> Export As and choose the "VRay (.vrscene)" format.
This is pretty much what gets sent to the DR slaves and also what V-Ray for MODO renders internally.

The MODO gradient is actually converted to two V-Ray standalone plug-ins : TexColorCurve (which we wrote for XSI initially) and TexModoSampler (which I added),
which implements the different "inputs" of the gradient texture (like incidence or thickness).
TexModoSampler is part of the V-Ray standalone that comes with V-Ray for MODO. It is not yet added to the standalone that comes with V-Ray for Maya, for example.

Greetings,
Vladimir Nedev

Yet more useful info. Cheers.

[lllab]

no atm it just bakes all procedural shaders which are set to be baked on the fly (one can set that global or per shader), so also the one that might not be direct visible(but maybe in reflections,gi etc so not quite sure how to recognize fast enough if the shader is seen or not in that frame).
they can be baked into memory or into a file.

[vladimir.nedev]

Very useful information Vladimir. It's easy enough to change the config file to read the 701 Substance plugin in 801+.

For tomorrow's build (the one from 2015-07-21) I have updated my code to work with the final version of the MODO 801/901 Substance plug-in for MODO.
RT updates on the Substance tweaks will now work. Also the Substance item will be correctly recognized as a material, and its properties used by V-Ray.

Note that animating tweaks and then rendering with "production animation" doesn't work, but this seems to be a Substance bug, as it doesn't work in MODO's renderer either.

Greetings,
Vladimir Nedev

[jonmoore]

Splendid news Vladimir. Thanks for the update.

[danielz]

For tomorrow's build (the one from 2015-07-21) I have updated my code to work with the final version of the MODO 801/901 Substance plug-in for MODO.
RT updates on the Substance tweaks will now work. Also the Substance item will be correctly recognized as a material, and its properties used by V-Ray.

Note that animating tweaks and then rendering with "production animation" doesn't work, but this seems to be a Substance bug, as it doesn't work in MODO's renderer either.

Greetings,
Vladimir Nedev

Substances are not working here on V-Ray with Modo 902. Have to bake them to the filesystem to get them rendered. Is this expected behaviour for 902? The substance plugin is version 2.1.0, vray 3.1.1.

[vladimir.nedev]

Substances are not working here on V-Ray with Modo 902. Have to bake them to the filesystem to get them rendered. Is this expected behaviour for 902? The substance plugin is version 2.1.0, vray 3.1.1.

The problem is the 2.1.0 version of the Substance plug-in. It adds some changes (compared to the 2.0.1 version) that broke my export code, which is somewhat my fault.
I've fixed it for tomorrow's nightly build ( the one from 2016.01.05 ).
Thank you for finding this.

The good news is that the 2.1.0 version fixes tweak animation not working.

Greetings,
Vladimir Nedev