V-Ray Falloff texture form not refreshing correctly when options are changed

[1funk]

The falloff form is not updating correctly when options are changed.

Modo 10.2v2 130270
V-Ray 3.40.03 27107

video: https://www.dropbox.com/s/psj1x3vb42...e_bug.mp4?dl=0

1. Add a V-Ray Falloff texture to the shader tree
2. Set Type = Fresnel
NOTE: The "fresnel IOR" field is not displayed

3. Force a form refresh by collapsing/expanding the "V-Ray Falloff"
NOTE: The "Fresnel IOR" field is now visible

4. Set Type = "Towards / Away"
NOTE: The "Fresnel IOR" field is still visible but should be hidden. If you try to edit it you get an error

5. Force a form refresh by collapsing/expanding the "V-Ray Falloff"
NOTE: The "Fresnel IOR" field is now gone

[boyan]

Merry Christmas to all

Hey, funk!

Thank you for the amazing feedbacks keep running man. It seems the issue is existing in a MODO new beta # 130270 as I could not reproduce with an official MODO 10.2.1 #126693 or beta MODO 10.2.2 126603 #. Keep you posted about this behavior.

Take 'er Boyan

[1funk]

Hi Boyan and Merry Christmas to you too

Yes, it's only happening in the latest beta, but since I can't find any other forms where the problem happens, I thought I'd post it here

[1funk]

I can no longer reproduce this in MODO 10.2v2 (RC3) 131034

Looks like TF fixed it

[1funk]

Scratch that... it still seems to happen, but I'm not sure of the exact steps

[vladimir.nedev]

Steps that will ALWAYS reproduce the issue in MODO 11.2v2. You must do them in the EXACT order with NOTHING in-between:

1. Start MODO
2. Create a V-Ray Material (Add Layer -> V-Ray Materials -> V-Ray Material)
3. Create a V-Ray Falloff texture (Add Layer -> V-Ray Textures -> V-Ray Falloff)
4. Change "Type" from Towards/Away to Fresnel -> The UI won't update and Fresnel IOR won't show up

Step 4. is now reproducible on every V-Ray Falloff texture, until MODO is closed and reopened.

Because the V-Ray Material and the V-Ray Falloff texture both have a channel named "vray_fresnel_ior", MODO somehow confuses them and uses the "enabled" dependencies on the wrong item (even though the V-Ray material is no longer selected !).

I've worked around this by specifying the item type as a prefix to the channel name in the "item.channel" command for all V-Ray materials/textures/items.
When that's done, MODO no longer confuses the channels.
So the bug should be fixed in the nightly build from 2018.02.07.

Greetings,
Vladimir Nedev

[1funk]

Thanks Vladimir