Search the Community
Showing results for tags 'AOVs'.
Found 4 results
-
Hello, I've got a question because I'm getting stuck on something while figuring out karma: I import a geo from SOP and with a render_geometry_settings node I set it to treat as light with a specific LPE to make it a geo-light, except that when I get to karma to make my aovs and split them by LPE, I realise that Karma only generates AOVs for "classic" lights (dome-light) and none for my geolights - here are two screenshots, if anyone has a solution or ideas I'd love to hear them, as I can't find much online at the moment on the subject of geolight LPE in karma.
-
Hello there, So I have a scene in Solaris, and I have set up velocity and depth AOVs. There are objects in the scene with transmissive materials applied to them, however these objects seem to block the AOVs, Is there any way to Let these AOVs pass through transmissive objects? Here are the passes: (Beauty Pass) (Depth Pass) (velocity pass) Thanks!
-
Hello! I am currently working on a project that has the majority of the image is refracted through a ocean spectrum surface. The problem being that I am unable to get AOVs such as point position, depth, and diffuse for the objects that are under the surface. I currently have a work around, where I have created utility shaders to enable control of the elements under the water surface. However, this has resulted in having a different render for each AOV needed! Does anyone have good approach to accessing the refracted objects AOVs? The current approach is a bit cumbersome and time consuming. Any advice would be much appreciated!!
-
Is there any way to create object-based mantra AOVs (for object ID mattes) instead of having to go through the shader, like how vray for maya handles it where you can create an object property with an override object ID and you can throw multiple objects in it that will all inherit the same object ID? I'm referring to would would be object RGB object mattes in other software I know you can export custom AOVs inside a shader but for my workflow I have three issues with that- 1) if you are doing quick look-dev and iterating through multiple different shaders and you export that variable in one but quickly shift gears to a different look and forgot to include it in the new shader it won't render 2) If you want multiple objects to share the same object ID matte rather than having to annoyingly shuffle copy everything together in nuke you have to duplicate the same variables for each shader 3) and most importantly, and I don't really see a way around this, you need to unlock every shader HDA which is, as I have read, extremely innefficient in H15 as their load time and memory footprint are greatly optimized in their VEX HDA definition state Ideally this would be something you could implement at the SOP level in a wrangle or something Is there any way to quickly enable/disable all extra image planes like you can in maya/max/cinema/every other software, without manually unchecking every box? Then finally, when you export a float AOV and bring it in to nuke it basically reads it as an alpha channel; it won't be visible to a shuffle node as most AOVs would, you need to use a copy node to extract it. That isn't a huge deal except for I use a lot of python scripts that automate a lot of this and that breaks my workflow a bit. Any way around this? Any insight on this is greatly appreciated!
