Milovan Mladenovic

We have project that is migrating from Houdini 19.0 to 20.0
In Houdini 20 way albedo pass is being rendered had changed. In change log found this:

20.0.548:Matches Albedo AOV between Karma CPU and XPU. The Albedo AOV now shows total albedo and not just diffuse albedo.

Is there way to get only diffuse albedo now? Looked up LPE expressions, but didn't figure out how to get albedo via LPE.
Thanks!

Here's image showing problem:

Jonathan de Blok
Thanks for the pointers, I actually did manage to find a way replace/delete/update branches.

Using a 'split' scene you can split of the part you don't want, then replace them with a new one, if paths/names match it will work as a replacement.

red: incoming scene with original /obj/plant/matnet1 content
green: by splitting off the /matnet1 branch, the left over is the scene excluding that part
blue: the matlib node inserting it's content at /obj/plant/matnet1 effectively replacing it.

Image Not Found

That being said, my Solaris adventures goes into the fridge for now, back to Redshift it is. I really wanted this to work, and i hope 20.5 brings some mayor overhaul in this area. Solaris has fundamental performance issues, Karma renders fine but the whole UX is flawed. Everything takes so much more time to setup, I'm sure there is a tipping point for Pixar sized studios where it's all worth it but for solo artist/small teams it's just not there. Working natively with USD is nice on paper but also very incompatible with the regular /obj workflow. That in itself is not that terrible was it not for the fact that Karma is USD only. So effectively Houdini does not have a way to render it's own native /obj content in a efficient way that makes it comfortable for animation and lookdev.

/rant

Even Sidefx doesn't recommend using karma in this way. Package your asset with component builder, then render it in proper stage environment.