In the name of usd and open source we thought to share our inhouse aov/rendervar hda. This is not sure something we will maintain but will try. Its more of an example of a setup and feel free to use as is or modify. Though im very happy for feedback if you guys come up with better solutions
GBK aovs:
- lpes for beauty
- industry standard naming (probably quite close to arnold most)
- beauty and cryptomattes works for both karma and vray (not utility passes)
- automatic creation of aov_bind rendervar
- automatic creation of lightselects (or only create lightselects base on lpe tag)
This is mostly production tested with vray. Karma probably needs some work.
lpe tag doesn’t support on build of vray52002 dec2021, i correct? im not success to do this on that build but when on aug2022 build and vray6 its can do. i want some suggestion will be much appreciated. i mean how i can do or anyway to do with old build.
Dont have to much information to go on but the lpe tag will be the same from the gbk_aovs node. It may be that the old build is old enough to not support it yet. I would recommend using as late build as possible because there is a tons of fixes the last year.
- totally rebuilt to python to be faster. Went from 20 to 0.1 in big production scene with every feature enabled.
- added metadata and a dropdown with some example. like gather lights and their position.
- added crypto for component kind (need latest vray nightly). adds a string primvar to the components with their corresponding names
- better karma and vray compatibility
- added an automatic assignment of renderproduct to incoming rendersettings so the gbk_aovs can be added last in line.
- added settings to choose compression and filtering type. unfiltered fragment closest to camera is on by default now
- automatic lightselect has changed a bit:
- - doesnt pickup deactivated lights
- - 2 settings of either choosing automatic naming or pickup already set lpe tag has changed. Its only 1 setting now and if lpe tag already exists it will group it to correct lightselect automatically and do automatic name only if no lpe tag is found.
- and other small fixes or settings that popped up under production
Hey
I was trying to use lpe per light on vray but when i add all my lights in comp it never looks like the beauty, i figure it out that was the light cache and if i use brute force it would be perfect, but brute force is very expensive, There is any othe way to have individual lights for compositing in nuke?
Sorry to bother you i searched all chaos forum and didnt found any workaround!
Could you provide us with a scene that shows the described behavior? You can either ZIP it and upload it here, or mail directly to team-dev-vray-houdini@chaos.com
@LeoYfver Hey Leo, thanks a tons for the help,i tried a retrace threshold of 25 and it didnt workerd, but with brute force was perfect the problem is that we cant afford to render everything with brute force. I was also trying to figure it out if light select work in vray for solaris i tried to search how to do it but didnt found it!
Having separate lights is an integral part of my compositing process, it would be great if i can have those with light select or light mix or any other way that i dont know. How do you go around this problems?
Hey @Gosho.Genchev i will upload the scene and send it to you, i will just have to colapese everything.
