Jump to content

bonassus

Members
  • Content count

    119
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

3 Neutral

About bonassus

  • Rank
    Initiate

Personal Information

  • Name
    bonassus
  • Location
    Chicago
  1. The openGL rop isn't rendering mantra materials in my linux install. The materials are displayed in the view port. When i render an image with the openGL rop, no materials. It works fine with windows but not linux. any ideas? thanks
  2. Houdini 18 Wishlist

    Here's an idea. a workflow convenience that would save me clicks would be an option to open containing folder from the file cache Geometry File field. Or even better would be a delete cache button on the File cash node. I often find myself needing to clean up intermediate simulation files from my file system. And i think to myself i with there was a delete button.
  3. I updated to today's Daily Build and the problem when away.
  4. I have a Top net with a ropfetch node pointing at an opengl rop. When i render the opengl by cooking the ropfetch it renders the reference plane/ortho grid into the image. Even though i have turnned off its display in the view port. However if i render the opengl directly the grid doesn't render. Not sure if this is a bug. anyone have a solution? thanks.
  5. I'm getting started with htoa and volume rendering. i would like to link the Arnold volume node directly to the vdb convert and render volumes without saving out the .vdb files. i tried: op:/obj/smoke/OUT_vdb This didn't work. Is there a way to get this working or are we just stuck saving out .vdb files with Arnold? thanks.
  6. mix vellum and bullet

    thanks for the response.
  7. I'm trying to mix vellum and bullet in the same sim using the multi solver and i'm getting a confusing error. the vellum object is asking for a constraint_name. which I assume has to do with the bullet solver somehow as vellum constraints don't have a constraint_name attribute. attached are screenshots of my network if anyone wants to take a look. any ideas how to make this work?
  8. Houdini 18 Wishlist

  9. Houdini 18 Wishlist

    I wish I could bind the range filed of a parameter of an hda with expressions. Currently the range field of the type properties window only accepts numbers.
  10. relative reference in parameter range

    Ok I see. Thanks for the file it helped me see another way to control the parameter . In practice however i think this is equivalent to just clamping the value at sop level. As the sliders range isn't updated and can exceed the clamped value. I wish I could enter the expression into the range filed itself. thanks again.
  11. relative reference in parameter range

    thanks for your reply. in this case you cannot enter an expression into the range filed. it only accepts numbers. i think the best non pyton script solution can be found here: https://www.sidefx.com/forum/topic/11209/?page=1#post-53490
  12. relative reference in parameter range

    Hmm, maybe my question was confusing. Is there a way to set a type property parameter, the max range field for example to the value another parameter or variable using an expression? It appears that you cannot enter expression into type property parameter fields.
  13. I'm setting up type properties for an hda i'm working on. I would like to set the value of the range fields relative to the value of a different parameter. For instance set a window width parameter based on the wall width parameter. however the range fields in the operator type properties window only allows me to type in integer values. It wont let me type relative reference to the other parameter. Is there a way to do this? thanks
  14. That was it! thank you very much!
  15. I sometimes use the bbox expression to reference the dimensions of an object in a group node to create a primitive group by bounding object. I'm trying to create a preset to speed up the process of creating this kind of group. So i'm trying the operator path parameter set to string. see below image. it seems like this should work the same as the above image but it Chanel expression returns the dimensions of input 0. not the bbox of the object in the path field. can someone enplane how this could work?
×