Rougness is messing things up

When i put a map on the roughness in a vraytmtl it will connect the map. But from that moment all vray shaders get something connected to the roughness slot. When you follow the link you won’t get the node. I am not able to disconnect the node then.

We have it on several computers. Allready in Vray Next and also now in Vray 5.

Anyone noticed this problem ?

Hello there,
Is it possible for you you sent us a scene, with which you are able to reproduce the problem and also a video file where you reproduce it?
Also can you provide your specs (such as OS, Maya version, etc.)

Best Regards,
Dimitrina

Hi Dimitrina,

I attached a Maya file in which the problem happened. I also made a video. You can find it here: https://www.i2.nl/temp/roughness.mp4

We use Windows 10 with Maya 2019.2 with Vray 5.

Thank you.
roughness.zip (9.23 KB)

Hello again,

I looked into this issue and managed to reproduce it. I have logged at issue, which you can track with this internal bug issue ID number: VMAYA-10067.

Best Regards,
Dimitrina

Fine you logged this issue, tnx.

Hello again,

The problem with the Roughness Amount being applied to multiple VRaytMtl materials is supposed to be fixed with the V-Ray nightly build (30582) from today 09/02/2021.
Can you please check with the build mentioned and if there are any further issues don’t hesistate to message us.

Kind Regards,
Dimitrina

Thank you for solving this problem!
How can i download the last build ?

Hello again,

You can download the recent V-Ray nightly build from here: nightlies.chaosgroup.com

Kind Regards,
Dimitrina

It looks like the problem is not solved.
Maybe i am doing something wrong? I went to nightlies.chaosgroup.com and downloaded 20210311 11/03/20212. I could not find the exact one you pointed out.

I installed it and made 2 materials. On one i put a map on the roughness. Then the same map is also on the second material.

Hello,

The fix for this problem is now in the V-Ray stable builds, which you have access to. Please check if the problem is still reproducable with V-Ray stable build 5.0 form 13/03/2021.
If the problem is still reproducable please do not hesitate to message again.

Kind Regards,
Dimitrina