Jump to content
  1. General

    1. 26.4k
      posts
    2. 2.1k
      posts
    3. 1.6k
      posts
    4. Marketplace

      For all commercial tools, HDA's etc.

      428
      posts
  2. Houdini

    1. 65.5k
      posts
    2. 49k
      posts
    3. 12.3k
      posts
    4. 5k
      posts
    5. 15.2k
      posts
    6. 1.1k
      posts
    7. 693
      posts
    8. 686
      posts
  3. Coders Corner

    1. 6.3k
      posts
    2. 13.2k
      posts
    3. 4.8k
      posts
  4. Art and Challenges

    1. 3.5k
      posts
    2. 9.8k
      posts
    3. 572
      posts
    4. Effects Challenge Archive

      This is where the cool unofficial challenges live on!

      296
      posts
  5. Systems and Other Applications

    1. Other 3d Packages

      Maya,XSI,Blender,etc

      1.6k
      posts
    2. 1.5k
      posts
    3. Hardware

      Graphics cards etc.

      2.1k
      posts
    4. 422
      posts
  6. od|force

    1. 1.5k
      posts
  • Who's Online   3 Members, 0 Anonymous, 279 Guests (See full list)

  • Member Statistics

    45,710
    Total Members
    10,714
    Most Online
    Kokles
    Newest Member
    Kokles
    Joined
  • Forum Statistics

    46.1k
    Total Topics
    230.8k
    Total Posts
  • Posts

    • Hey I have two buttons in hda's UI one to 'Start paint' and the other 'Done paint' I want each one to toggle the other visibility so they are not shown together, I been digging around with no success can someone point me for a good tip please thank you
    • I also don't like to export directly from SOPs. I tend to do all of my work in SOPCreate nodes so that I can see how my geo is being translated into USD before I cache. You should be able to specify the primitive path on the Geo Clip Sequence node. I don't have a hip file on hand but I have made a tutorial that covers a caching + referencing workflow that might be helpful. Scenes can get slow for loads of reasons, even when everything is cached. The main thing you can do to keep things as light as possible is make sure you have no time dependency badges and ideally have proxy geo for everything. If it's a big scene with lots of assets then unloading payloads can help too. Regarding the bgeo cache, you can use that directly in the Geometry Clip Sequence (as long as you're rendering in Houdini/husk). I do that for heavy fluid Sims as you're right it tends to be a smaller file size. I also cover this in the tutorial above. Alternatively for other things I'll treat the bgeo cache as a temporary cache to avoid having to recook things and then save my USD cache from there. You can of course save directly to USD instead of bgeo. Just use a USD Export in sops or USD ROP or File Cache in LOPs. Note that you should only need the Geometry Clip Sequence if you're caching really heavy geo to per frame USD or bgeo files. For most things you can save to a single USD file which is much easier to work with.  
    • Thank you very much, Matt, for your detailed response and explanation. I greatly appreciate your time and insight. I was hoping to understand more about how you structure your scene while keeping the pipeline in mind. I'm planning to use the Component Builder for asset creation, and I’d prefer not to export USD directly from SOPs. From what I’ve read in some forum discussions, exporting USD from SOPs can sometimes result in missing attributes. For that reason, I'm currently using the Geo Clip Sequence node. My goal is to bring all geometry into Solaris and cache it there. However, I’ve encountered an issue with the Geo Clip node: when I save the output, it alters the hierarchy names. I'm not sure how to prevent this so that it matches the hierarchy created by the Component Builder. Any guidance on how to resolve this would be very helpful. If possible, it would be incredibly helpful if you could provide an example file showing the correct workflow. I’ve looked through SideFX documentation and tutorials but haven’t found one that addresses this specific issue within Solaris. Without caching, I've also noticed the scene becomes quite slow during lighting — especially when working with fur or feathers. Additionally, I have a question about caching: after creating a .bgeo cache, is it necessary to generate a separate geometry cache? It seems to create redundant files, and in cases involving fur or feathers, the geometry cache tends to be significantly larger than the .bgeo. The only benefit I’ve seen is that the Geo Clip Sequence loads faster. As mentioned, is there a way to directly generate the final geometry cache without first creating a .bgeo cache? I’d like to avoid repeated caching steps if possible. Thanks again for your help and any advice you can offer!
    • FMX HIVE 2022 presentation by Simon Fiedler & Bastian Schiffer  
    • Here's a couple older links on the topic.    
  • Topics

×
×
  • Create New...