Jump to content

Search the Community

Showing results for tags 'solaris'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Lounge/General chat
    • Education
    • Jobs
    • Marketplace
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering
    • Compositing
    • Games
    • Tools (HDA's etc.)
  • Coders Corner
    • HDK : Houdini Development Kit
    • Scripting
    • Shaders
  • Art and Challenges
    • Finished Work
    • Work in Progress
    • VFX Challenge
    • Effects Challenge Archive
  • Systems and Other Applications
    • Other 3d Packages
    • Operating Systems
    • Hardware
    • Pipeline
  • od|force
    • Feedback, Suggestions, Bugs

Found 5 results

  1. Hey hey there, I came across an issue and hope to find some help here once again I tried searching but didn't really know what to search for and then ended up unsuccessful. I am trying to create a Solaris/USD network with my python script but when I set the list parameters on the instancer node it only changes the choice visually but does not actually use it. As an example, when I set the "Prototype Index" to "Name Attribute" manually, the UI shows a new field to enter the name attribute. When I do this in Python: usd_instancer.parm('protoindexsrc').set("Name Attribute") usd_instancer.parm('nameattr').set("instancename") the "Prototype Index" gets set to "Name Attribute" but the extra field is not shown and the node behaves as if it's set to its default value. If I then open the list and click on "Name Attribute" myself again, it shows the new line with my correct name attribute. How would one go about solving this? Is there an extra function connected to this list choice that I have to trigger as well in Python? As always, I am very grateful for any pointers, ideas and help! Update: I noticed now that sometimes the script does not even set the list parameter. E.g. when I open a fresh scene, use my script, it creates the instancer with default values (no errors though). When I run my script again, it creates a new instancer with the list set to my values, but still having the initial issue mentioned above :/ Update2: I also posted over on the sidefx forums now and have a small screenshot to show what I mean:) I set the parameter in Python, it evaluates correctly in the shell but is neither shown in the interface nor actually used. Take care, Dziga
  2. Hey, I was wondering if I was the only one having this issue with Karma on H18 : I can't use geoLight or emissive Volume to light an other object. Any idea ? Maybe it's still impossible on the early beta version.. Sylbert. PS : I haven't find a way to setup the amount of ray limit in Karma setting as well..
  3. Hi all I've been looking at creating usd variants from the following, thinking on using this to create a model with variants from a piece of geometry that has a primitive attribute called "myattr" with 2 values (say half a sphere with myattr="left", and the other side called "right") 1- sopimport an object into LOPS with prim attributes. 2- create an add variant to existing primitive block 3- done Any ideas on how to iterate through each of the primitive attribute values to create this variants? adding a hip file for reference, maybe someone can help Thanks in advance! usdvariants_from_groups.hipnc
  4. https://www.sidefx.com/products/houdini/whats-new-in-18/ And to get your feet wet, Entagma release some H18 videos for the release. https://entagma.com/new-in-houdini-18/ Lops Tutorials and docs https://www.sidefx.com/docs/houdini/solaris/tutorials.html
  5. I know what Clarisse does, but I'm trying to understand Solaris. Is it SideFx "Clarisse"?
×