Opacity doesn't work when using driven keys.

[B037973a]

CPU rendering doesn't seem to support driven keys (Only tested the opacity and refraction imports).

To re-produce:
1. Create an object and apply a Vray MTL.
2. Add a new attribute on the object
3. Set a driven key from the opacity (RGB) values to the new attribute created.

Your opacity controller is now set-up, and you should see it working in the viewport, as well as CPU rendering.

Switch to GPU and it seems to ignore this set-up and default to 100% opacity.

I've created an example file that you can download here: https://we.tl/t-jJVIEjHKhF

[vladimir_krastev]

Hi, thanks for posting. I will test your scene and get back to the thread.

[vladimir_krastev]

Hi the opacity control attribute does not work in GPU, you are right about that. I will log the issue but just wanted to know why do you need this workflow? As far as I understand it you are controlling the material's properties from the Sphere's attribute that you created for the case but why? Isn't it better to just use the VRayMtl properties?

[B037973a]

Hi Vladimir,

Thanks for looking into it, and logging the issue. The reason I want to create a control attribute is for two reasons:

1. Keyframed material attributes don't show up in the graph editor (when selecting geo/rig). I need to do a lot of animating to the opacity / refraction, and using the graph editor is pretty essential for this.

2. It improves a rig overall, with all controls being together, instead of having to go into the material attributes all the time.

In short, it just improves an animators workflow by quite a lot.

Thanks,

[vladimir_krastev]

Thanks for the details. The issue is logged under VMAYA-12114.