Search the Community

Hi admins, why not putting a Solaris section? There're so much questions about this new module.. Thank you.

This might be a super basic question, but for the life of me I cannot get an editmaterial node to work with Karma nodes (for redshift it works): Redshift: In a materiallibrary I create a rsMaterialBuilder and inside I create my node network, flowing into a redshift_usd_material node at the end. Then when I create an editmaterial node and load this material I get the complete tree of nodes to modify. With Karma this seems different. First I don't need to create a materialbuilder, I can create a principled shader for example right there (though I have also tried with a materialbuilder). I create my network with for example a texture (and I have tried with and without a collect node at the end) and after want to modify this in an editmaterial node. But if I do that the network inside is always broken and none of the additional nodes (texture) is there (see picture)? Has this ever happened to you? What am I doing wrong?

Wondering if there's a simple way to capture a buffer of the current rendered state of the Solaris Stage viewport. Given that the Hydra render delegate is specifically designed to be able to easily "bolt on" different renderers, I imagine it's exposed somewhere, but given that I'm new to both USD and the Houdini HDK I was hoping that someone would be able to point me in the right direction. In Maya I'd call, target = targetManager->acquireRenderTargetFromScreen(MString("viewport")); Is there an equivalent in Houdini, and more specifically the Solaris render viewport? Thanks.