If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Exciting News: Chaos acquires EvolveLAB = AI-Powered Design.
To learn more, please visit this page!
New! You can now log in to the forums with your chaos.com account as well as your forum account.
Ah nice one stehrani3d, that takes care of the compression and the metadata. Because only the renderer knows the pixel bounds for computing the data window, I don’t know if there is a way for vray to communicate that to hydra to set that automatically? I’ll ask side effects.
1. Dwaa and dwab is set on the renderproduct. Though it does only filter the beauty and no other aov for me. I have asked sidefx and no response so if anybody has managed please enlighten me . I want to do it on all except data passes.
A week ago i sent them a bug report that seems to be fixed now. I havent tried it out yet though
Basically the rules are based on openEXR recommendation. So when the channel names are uppercase it gets compressed and lowercase they dont.
So after this bugfix when you export a color rendervar it will be layer.RGBA (compressed) and if you export rendervar as point or vector it will be layer.xyz (not compressed).
what code did you use exactly to write the camera xForm into the metadata. Not seeing anything in your HDA besides a field to add metadata… maybe that’s what you meant?
There should be a drodown next to the parameter field. There you can select cameras. It will create a python if script that takes all the cameras and list them. Are we talking about the gbk_aovs?
ah, yes. The position was only done for the lights i think. We export cameras as alembic so the compositors have access to the position but not for the lights so that probably why.
Comment