The VRay Object Properties tag doesn't work on a hierarchy (GPU Renderer)

[Berndimator]

A Null object with a Objects Properties Tag on it black's out all objects (inside the hierarchy) when rendering. This problem occurs only when using the GPU Renderer. Workaround is to have the Objects Properties Tag directly on the meshes, which makes the scene quiet messy. Would be nice to have this fixed in a future release?

[aleksandar.kasabov]

Hello Berndimator ,

Upon testing this on my end I didn’t manage to reproduce this issue. Could you please share some more information about your system such as V-Ray and Cinema4D versions, GPU, GPU driver, OS? Also, please send us a test scene where the issue is reproducible.

Thank you.

[Berndimator]

Hi aleksandar.kasabov ,

I found a way to reproduce it. The main problem is actually if you have an object with a polyselection and NO second material OR even another material on it. See screenshot. If you have this setup in an hierarchy with an Object Properties tag it causes this black look. It is a problem because it's a common way in Cinema to drop a main material (in this case purple) on the object and use a polyselection (green) for particular parts on the object. Hope this helps!






The spec's are R23.008, Latest VRay 5 (hotfix 1), 2x GeForce GTX 1080Ti (Cuda), GPU Driver 27.21.145638, Win 10

[Berndimator]

Here's the hierarchy...

[aleksandar.kasabov]

Hello Berndimator ,

Thank you for providing those details. I managed to reproduce this issue and I logged it in our system (bug ID: VC4D-882). I will let you know once we have any updates on the matter.

[daniele_nicolaci]

Hello.
Just to highlight (if not already known) that in GPU mode and with Object Properties tag on a null, another strange thing occurring to me, is that children's applied material are ignored and just one among the materials assigned to them is applied to all. Objects out of null hierarchy work fine.

V-Ray 5 for Cinema 4D, hotfix 2 (v5.00.44 from Apr 9 2021)
C4D R23, Windows 10

[aleksandar.kasabov]

Hello daniele_nicolaci,

Thank you for highlighting this. We are aware of this issue and it has also been reported for fixing. I will let you know once we have more information.

[steilvorlage.de]

Hi, is there something new about this topic? I have the same issue - strange shaderassignements.

Cheers
Tobi

[aleksandar.kasabov]

Hello steilvorlage.de,

We don't have anything new to share at this point. I will let you know as soon as we have any updates on the matter.

Thank you for your patience and understanding.

[office_360360]

Hello steilvorlage.de,

We don't have anything new to share at this point. I will let you know as soon as we have any updates on the matter.

Thank you for your patience and understanding.

Hi, this is important issue for rendering workflow. Is it going to be fixed for next update?

[aleksandar.kasabov]

Hello office_360360,

I am afraid that I cannot provide any specific timeframes for fixing this issue. I have additionally bumped the priority and I will let you know once we have more information. Thank you.

[aleksandar.kasabov]

Hello all,

Just to let you know that this issue was recently fixed and the fix is available in the latest stable build. You can download and install the build from here.

Thank you.