Attribute Refresh Issues

[aweidenhammer]

So something has been bothering me about vray implementation in Maya. I did a search on this forum to see if there has been discussion on it, but didn't really come up with much. Sorry if my search wasn't thorough enough

As the subject mentions... is there any way to improve the refresh of the attributeEditor in general with regards to vray attribs? For example, the Physical Camera is clunky, and sometimes just not working in context. The attribs feed back to the maya camera? Not sure, but during playblasts, the physicalCamera settings don't update. Animate the focal length of a physical camera, and the playblast won't show it (or animate the focal distance, which effects the focal length). This is a workflow problem, as we can't use physical Camera in production, since clients rely on playblasts. There are lots of other little issues with the attribute editor not refreshing properly or at least not quickly. I am on the orig August release build, and have been testing various nightlys without seeing much change here.

Also with the physicalCamera, we often have to select/deselect/reselect the camera to even see the vrayAttributes at all. That is a very specific example of attrib refreshing. This is sometimes the case with many of the manually-assigned vrayAttributes (like displ/subd attributes).

Any info on this behavior? And if it is something that can be improved?

[vladimir.nedev]

About the animated physical camera and playblasts, I've tried to improve this and it should work much better in the latest build (or rather it should work, as it didn't before). I've done the improvements somewhere around the 8th of March, don't know if you have tried builds after that. I've also made some improvements to the update speed of the UI, this happened at the end of March. Can you test a latest nightly build and see if it improves things for you ?

Greetings,
Vladimir Nedev

[homeless3d]

same issue here with 1.50 / 1.90.03

[vladimir.nedev]

What nightly build are you using ? Those version numbers don't change very often.

Greetings,
Vladimir Nedev

[homeless3d]

mine is 20100407

[vladimir.nedev]

Hm, the 2010-04-07 should be working correctly. The next build though, the one from 2010-04-08 had a bug with the update of the physical camera. Can you still try the latest build and tell me if the problem persists ?

Also, you said, "same issue here", did you mean all of the problems aweidenhammer is having or some of them ?

Greetings,
Vladimir Nedev

[olivervfx]

We just made it refresh 3 times, to go around it

O.

[vladimir.nedev]

To go around what ?

Greetings,
Vladimir Nedev

[treyharrell]

Basically values in VRay-specific AETemplates haven't been updating properly... you have to toggle tabs a few times to get "current" values to populate (up to 11311).

Our workaround has been to make a copy of the stock updateAE.mel in our local scripts and append this at the bottom:

catch(`vrayUpdateAE`);
catch(`vrayUpdateAEJob`);
catch(`vrayUpdateAE`);
catch(`vrayUpdateAEJob`);

--Trey

[olivervfx]

Trey beat me to it

But yeah, the refresh in shaders and in render globals etc is a problem.
(linux , windows etc)

so if you "kickstart it" it works fine