Found 680 posts.
Search results Show results as topic list.
Solaris and Karma » Authoring anim layers _without_ subdivisionScheme attributes
- goldleaf
- 4168 posts
- Offline
Where is the animation layer being authored from? On the SOP Import, if you don't enable "Treat Polygons as Subdivision Surfaces", the SOP Import shouldn't author a subdiv scheme opinion.
Solaris and Karma » Layout LOP suggestions
- goldleaf
- 4168 posts
- Offline
Thanks for taking the time to share this feedback. Could I ask you to please log these bugs/issues? Especially the ones that aren't behaving as expected, it helps to outline each step exactly in the form. I know it can feel tedious, but it's very, very important (especially for these interactive issues). A recorded video can help too, but writing up the steps is usually more valuable; even narrated videos sometimes gloss over some crucial step that explains why user A is having an issue, but user B is not.
https://www.sidefx.com/bugs/submit/ [www.sidefx.com]
Some quick thoughts (again, please log a ticket through the form):
We try to watch the forum, but things can get missed easily so in addition to posting here. We recommend requests or bugs get logged in the DB, to ensure they can get tracked/assigned.
Thank you!
https://www.sidefx.com/bugs/submit/ [www.sidefx.com]
Some quick thoughts (again, please log a ticket through the form):
- Great idea
- I totally understand; this is one of those things where it seems half the time you want the asset scale consistent, other times you don't...
- Seems like a bug
- Seems like a bug
- Seems like a bug
- Great idea; I thought there was snapping, I don't think it was only built into the individual brushes...
- Isn't this what the orient brush is meant for?
- Seems like a bug
We try to watch the forum, but things can get missed easily so in addition to posting here. We recommend requests or bugs get logged in the DB, to ensure they can get tracked/assigned.
Thank you!
Solaris and Karma » referencing interactive layer with Python Script LOP
- goldleaf
- 4168 posts
- Offline
Some important details that were highlighted after posted this suggestion, as there is currently no robust/trustworthy way in Python to reference nodes using Python. The Reference LOP works behind the scenes to make a locked stage, so it can reference the LOP node safely. The Python approach may never have any issues, but you could find yourself with strange behavior pretty easily too as you click around and display/recook different nodes.
So take the above suggestion with a healthy dose of "YMMV"
If you do end up with strange behavior that keeps breaking things, try using the LOP nodes to re-create layer setups in Solaris. It would probably mean you'd have to be creative to use your scripts and get equivalent behavior to the LOP layers as you get with file-based layers.
So take the above suggestion with a healthy dose of "YMMV"
If you do end up with strange behavior that keeps breaking things, try using the LOP nodes to re-create layer setups in Solaris. It would probably mean you'd have to be creative to use your scripts and get equivalent behavior to the LOP layers as you get with file-based layers.
Solaris and Karma » Solaris Motion Blur - Clip Value
- goldleaf
- 4168 posts
- Offline
Solaris and Karma » Houdini/Solaris lights color cycling
- goldleaf
- 4168 posts
- Offline
Light Filter support will need to be added to Redshift itself.
Animated color and light can be keyframed manually, or you can animated them with a VOP; attached are some suggestions. Hope this helps!
Animated color and light can be keyframed manually, or you can animated them with a VOP; attached are some suggestions. Hope this helps!
Solaris and Karma » Replace Materials
- goldleaf
- 4168 posts
- Offline
The %geofrommat autocollection (prim pattern) can be used to pick the primitives bound to the old material, and use them in a Material Assign to reassing a new material. See the hip/screenshot for an example.
Hope that helps!
Hope that helps!
Solaris and Karma » referencing interactive layer with Python Script LOP
- goldleaf
- 4168 posts
- Offline
You need to use the layer's identifier:
Unless there is a default prim designated, you'll also want to specify a prim path to reference from.
Hope that helps!
node = hou.pwd() input_node = node.node("../sphere1") ref_layer = input_node.stage().GetRootLayer() stage = node.editableStage() prim = stage.DefinePrim("/foo") prim.GetReferences().AddReference(ref_layer.identifier, "/sphere1")
Unless there is a default prim designated, you'll also want to specify a prim path to reference from.
Hope that helps!
Solaris and Karma » Husk Procedural hair example
- goldleaf
- 4168 posts
- Offline
Hamilton Meathouse
Also, is there any chance that the Hair Procedural could be back-ported to H19 if requested by a studio? Or is there too much 19.5 tech that would make that a non-starter (USD version for example)?
I doubt it, there would be an awful lot of work; the procedural relies on more than just USD/Solaris technology.
Solaris and Karma » Husk Procedural hair example
- goldleaf
- 4168 posts
- Offline
What timing; sorry for the long silence, there have been some tricky issues to navigate, but tomorrow's cut should have the following updates:
- The Capture and Deform parameters should be hooked up correctly.
- We've added a 'Skin' Deform Mode
- Generator mode should preserve N when copied from the guides onto the generated curves
Solaris and Karma » Rendering Karma Sequence in Solaris - Indie Steam Edition
- goldleaf
- 4168 posts
- Offline
Please submit this issue through support, to ensure the right people can take a look at it. Thanks!
Solaris and Karma » Save used usd assets from library to current project
- goldleaf
- 4168 posts
- Offline
There is not a way to do this currently, it's probably easiest to just copy the asset library into the project folder. H19.5 has a toggle that will copy external texture maps or other non-USD files, but we don't yet have a simple way to do what you're asking. USD has some functions in UsdUtils that can make these tasks, but pipelines generally handle this sort of dependency/insulation task. If you flatten a USD Stage to send to the farm, you are effectively locking everything into one file, but those files get super massive; stage flattening is rarely a good solution for submitting to a farm.
Solaris and Karma » Component Builder Variant Configurations
- goldleaf
- 4168 posts
- Offline
You would setup your custom variants as Add Variant blocks to the Component Geometry Variants node, or you can use Add Variant blocks to add your own variants. If you have multiple variant sets, generally in production and asset would have a "model" or other variant that just makes variant selections on the other variant sets.
So the "A" model variant might set armrests to type 1, and wheels to 4; then "B" model variant would set armrests to 2, wheels to 5; and so on...
Does that make sense? You could use the Component Geometry Variants as that top level control; each input to the Component Geometry Variants would be a Set Variant node, which makes the variant selections for the wheels, armrests, etc...
If you're finding the Component Builder nodes too restricting, you can switch the Component Output's mode to "Input Primitives". Input Primitives mode is meant to let you keep using the conveniences of the Output node, but have more control on what's going on inside.
So the "A" model variant might set armrests to type 1, and wheels to 4; then "B" model variant would set armrests to 2, wheels to 5; and so on...
Does that make sense? You could use the Component Geometry Variants as that top level control; each input to the Component Geometry Variants would be a Set Variant node, which makes the variant selections for the wheels, armrests, etc...
If you're finding the Component Builder nodes too restricting, you can switch the Component Output's mode to "Input Primitives". Input Primitives mode is meant to let you keep using the conveniences of the Output node, but have more control on what's going on inside.
Solaris and Karma » Husk Procedural hair example
- goldleaf
- 4168 posts
- Offline
We're working to resolve the deformation parameters having no effect, thank you for your patience.
For anyone with further issues that haven't already been logged, please submit bugs with example files, so we can be sure to address the issues you're seeing.
Thanks!
For anyone with further issues that haven't already been logged, please submit bugs with example files, so we can be sure to address the issues you're seeing.
Thanks!
Solaris and Karma » Understanding USD import/export in SOPS/LOPS
- goldleaf
- 4168 posts
- Offline
USD Import has unpacking options, but the low-level LOP Import SOP is meant to import USD Prims into SOPs as packed prims. This lets you apply simulations or other rigid transforms efficiently. It can also be the case that you want to import some models in a scene as SOP geometry, some as individual USD Prims, and perhaps import a big chunk of a scene as a single USD Packed Prim (either for crude collisions or just visual reference). If you are just doing rigid transforms, unpacking USD prims is usually just making Houdini do more work, when round-tripping between LOPs and SOPs.
@dhemberg, the USD Import/Export nodes are largely aimed at file-based USD workflows; you would want to just use a Reference LOP to read the exported USD assets from disk. USD Export can be useful, but if you need to do more USD-facing work on your asset, such as materials or other tweaks, the Component Builder [www.sidefx.com] nodes might be worth looking into.
@dhemberg, the USD Import/Export nodes are largely aimed at file-based USD workflows; you would want to just use a Reference LOP to read the exported USD assets from disk. USD Export can be useful, but if you need to do more USD-facing work on your asset, such as materials or other tweaks, the Component Builder [www.sidefx.com] nodes might be worth looking into.
Solaris and Karma » Sampling Behavior options on certain 19.5 LOPs
- goldleaf
- 4168 posts
- Offline
Just to add a bit more info, the animated nodes are actually only cooking once; the node internally authors multiple time samples, rather than just the current time sample. It can appear similar to a Cache LOP, but the Cache LOP causes upstream time-dependent nodes to re-cook, in order to author multiple time samples.
A node must be specifically written to support the new sampling behavior; any nodes based on Edit Properties support this, as well as the Transform and Volume LOPs (if you see the "Sampling Behavior" spare parms when you create a node, then it's supported).
More info can be found on the Edit Properties [www.sidefx.com] help card.
A node must be specifically written to support the new sampling behavior; any nodes based on Edit Properties support this, as well as the Transform and Volume LOPs (if you see the "Sampling Behavior" spare parms when you create a node, then it's supported).
More info can be found on the Edit Properties [www.sidefx.com] help card.
Edited by goldleaf - Aug. 9, 2022 14:27:48
Solaris and Karma » prerender vs preframe scripts
- goldleaf
- 4168 posts
- Offline
Solaris and Karma » What is different about Invisible and Hidden?
- goldleaf
- 4168 posts
- Offline
It's metadata hint on USD prims (and properties as well), to tell a GUI to not show a prim. This is separate from a prim's "visibility", which affects viewport drawing/rendering.
Solaris and Karma » MaterialX + String path attributes?
- goldleaf
- 4168 posts
- Offline
No problem; and I forgot to caveat, but mixing MtlX with USD Preview nodes will only work with Karma.
If you create a "Karma MaterialX Subnet" inside of Material Library, your tab menu will be filtered to nodes that work with together and are compatible with Karma CPU (Karma XPU being is in alpha still, of course ).
If you create a "Karma MaterialX Subnet" inside of Material Library, your tab menu will be filtered to nodes that work with together and are compatible with Karma CPU (Karma XPU being is in alpha still, of course ).
Solaris and Karma » MaterialX + String path attributes?
- goldleaf
- 4168 posts
- Offline
Here is an example. It also shows how you can index your string primvars, so they take up less space.
Solaris and Karma » How do I link geometry to a camera in solaris?
- goldleaf
- 4168 posts
- Offline
SOP Import/Create have a "Define Only Leaf Primitives" toggle, which will only create Gprims with overs on all of the ancestor prims. Alternatively there is an "Other Primitives" toggle to control things as well.
https://www.sidefx.com/docs/houdini/nodes/lop/sopimport.html#prim_def [www.sidefx.com]
https://www.sidefx.com/docs/houdini/nodes/lop/sopimport.html#prim_def [www.sidefx.com]
-
- Quick Links