displacement node in shader loses local override when assigned with material node

[LeoYfver]

displacement node in shader loses local override when assigned with material node inside the geo level instead of assigned on the shader parameter on the obj node

https://drive.google.com/file/d/1XUI...ew?usp=sharing

[bdancer]

Material path is wrong "/obj/subnet1/matnet1/vrayMaterialBuilder", but should be "/obj/matnet1/vrayMaterialBuilder".

[LeoYfver]

Accidentally assigned the wrong path before i sent the file. The problem still stands. The local displacement settings wont override the global.

[bdancer]

1. There is warning in console especially for displacement assigned by material SOP.
2. There are no object properties on OBJ.
3. Which OBJ properties should be overridden? Texture? Type? Amount? All properties? First 10? I'm not joking just really want to understand how do u expect this to work...

[Gosho.Genchev]

Just to clarify Andrei's message:

When you render packed primitives, we export in a different way than when you render regular meshes. Simply put, we generate a separate node for each packed primitive. Because the Displacement (with all of its settings) in V-Ray is applied to an entire mesh, when rendering packed primitives, we can separate each primitive to a different mesh, and apply the displacement settings individually, if you assign the materials with displacement to the packed primitives themselves.
If you render a regular mesh and you assign different materials to subsets of its faces, with different Displacement VOPs inside, we can't really tell which one to use. There is some magic happening in the background (blending of the textures used, etc) but as to the settings themselves - we can't know which to use. Again, this is because displacement is applied to the entire mesh.
So, the solution is to add Displacement Properties to the node holding the geometry, and to do your overrides there.

Here is the warning Andrei is talking about:

VFH [Warning] * "/obj/grid_object1" contains per-primitive displacement assignments, but doesn't provide displacement object properties. Automatically generated settings will used.

If you guys think a change to any of this could be beneficial to you and make your workflow simpler, please do share your ideas.

[LeoYfver]

Thanks both for claryfing!

bdancer

1. didnt even think to look there, thanks
2. no. But i added them and nothing changed, tried with displacement too but then the vop displacement is obsolete
3. all displacement properties

Gosho.Genchev

I can explain how I would want it to work from an artist perspective and I understand if thats not possible.

Its enough being able to control displacement on packed primitive/packed alembics, we never assign these kind of properties to particular face of a mesh so erroring in that case is fine.

the lower in the hierarchy the settings are the stronger the opinion, so vop in this case would be the strongest


This is beneficial for but i understand if its too much changes that has too happen and confusing people with an already set worklfow. If people can add a +1 or -1 on this it would be nice


Regards Alexis

[LeoYfver]

Ok. Im a bit slow here. Now i realised that with packed it works correctly. This workflow with packed is fine for us. Sorry for the confusion

[Gosho.Genchev]

No worries, we need to document all of this - it's our fault you need to ask in the first place. We're working on it!

Cheers!