Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Tronotrond

  • Rank

Personal Information

  • Name
  • Location
    Houston, TX

Recent Profile Visitors

397 profile views
  1. Houdini 18 Wishlist

    In general very happy in the direction everything is going. As a generalist that moved 100% over to Houdini I would love to see working in the viewport keep being improved. Shift drag to clone/instance objects. Same with modelling. Select edges, shift click drag to pull out new polys etc. Thumbnails on all nodes in the material networks would be great, especially on composite, color corrects etc.
  2. Parent local axis constraint?

    And no.. I thought it was fixed, but it wasn't.. I recreated my setup in a simplified scene. Would any experts mind taking a look? I would be forever grateful I should think this is a very simple setup, but I'm definitively having some problems wrapping my head around CHOPS still. The rig is fine as long as the "engine object" itself is not rotated in any way. But once rotated things explode. I believe my problem is that I cannot link the piston to the piston arm directly without getting a dependency loop from the LookAt constraint. And then in CHOPS having the piston itself just follow the Local Y-axis of the piston arm. Works fine in world space, but once things are rotated things are not so happy anymore.. engine_rig.hip
  3. Parent local axis constraint?

    Was able to solve this in the end. Had to modify the constraint CHOP a bit; Use constraint get local space, blend the parent movement, then add in world space position at the end. Seems to be working!
  4. Hi, I'm currently rigging the internals of a traditional engine, and I'm a bit stuck. I have the main crank rotating, the connecting rod attached with a look-at constraint towards the piston. The piston only moves up and down in the Y-axis. So far I've done a Parent Blend constraint from the Piston to the connecting rod, masking everything but TY. But it's using world Y axis. If I go and rotate the engine at the object level, the rig breaks. The piston does not translate to the new local Y axis. I'm very new to Houdini rigging, so I'm just wondering either how I can set it to use local axis constraints, or what other ways I can/should solve this? Thanks!
  5. Houdini 18 Wishlist

    I think I'd be handy if you had like a viewport equivalent to the CTRL+Left click in the render view. Basically to click a primitive to see it's groups, attributes, materials etc. Further improving viewport interactivity would be nice in general. Still would like to see some easier ways to display textures in the viewport across different render engines, and preview thumbnails in the material networks.
  6. Hi all, I hope this is not a dumb question, but I'm trying to find out if it's possible to preserve object pivot points on models exported from other packages. I work a lot with high poly CAD models, mechanical moving parts. Often including parts with offset rotation etc. I'm exporting these from 3dsMax. Are there any ways to preserve the pivot point location and rotation per (packed) object so I can animate them correctly in Houdini? Also, I'm trying to avoid animating inside SOP since it's a real performance hog and not really ideal if I need to use the models for simulation collisions etc. Moving the pivot transform out on to the object level would be ideal. I recorded a video, trying to show exactly my workflow issue here. Just curious if there are any good workflows to handle these kinds of scenarios? https://vimeo.com/294855489
  7. Bubble particles from mesh

    If I understand you correctly, you just want to map the distance from the surface, right? This can be accomplished easily with VEX, even outside the pop net. I'd try a wrangle on all the particles, using the minpos function. It'll give you the closest position to the input geometry. Won't be perfect in all scenarios, but in the same way you can mix it with the particle age for more control etc. I attached a quick demonstrating driving the pscale and the color from the distance. Using a ramp gives you even more control. Regarding Q2 you can probably use similar functions to add more or less velocities. I.e. you can multiply a force by the distance. MinposDistance.hiplc
  8. Placing objects on a surface

    One other way you can do this is setting normals on the instance points (attribute transfer from the mountain geo). It doesn't give you full control, but your scatter objects Z-direction will always point in the direction of the normal - so you can achieve this by giving your scatter object the right orientation first. To have full control of all three axes you need to combine three vectors into an orient attribute matrix. You can do this with playing around with cross products, but might be overkill for what you're trying to achieve
  9. Geometry particles PopSpin

    Great! Thanks a lot! I didn't know the primitive node could be used like this. I was on to the idea of copying the transform back to the pieces, but wasn't sure how to approach it and match it up piece by piece. Reason I'm staying away from RBDs is the main scene I'm working on have massive amounts of pieces set up. I needed something that gives quick feedback, and collisions isn't an issue. Thanks again!
  10. Geometry particles PopSpin

    Hi all! I hope this isn't a dumb question, but I'm stuck getting my particle shapes to spin. I might be approaching this wrong... I've fractured and packed an object. I bring the pieces into the POP network, instancing each piece with source emission type set to All Geometry - each particle is a piece from the fractured geo. Now I just want these pieces to spin. I do get the w attribute set, but, the pieces themselves are just translating with the particles, not rotating. A simple scene with the setup is attached. Can anyone point me in the right direction here, and perhaps explain why this approach doesn't seem to be working? Thanks! popSpin.hip
  11. Slow network hip save

    Thank you so much! Worked like a charm. Phew! With autosave on this was driving me mad Luke: Thanks for the explanation. That makes sense, and I'll bring it up to the IT guys.
  12. Hi all, we recently purchased Houdini at my workplace, and I'm noticing a slight issue when saving my scenes to our network drive. Right now I'm working on a .hip file that's about 20MB. Saving it to any of my local disks is done in seconds. Copying the same file from my local drive to the network only takes a second as well. Saving it to our network drive directly, on the other hand, I can watch the file size slowly grow and it takes about 60 seconds to complete! So I am guessing it has something to do with how Houdini does the file writing. I don't see this happen to any file caches etc. Only when saving the scene file. Unfortunately for us, our data center is not in-house. It's located a few blocks away. So I am guessing it has something to do with how network traffic is routed over - and that a lot of small writes (compared to a large file copy) is slow. Has anyone else experienced this? Are there any workaround. I.e. forcing Houdini to save locally and copy the file? I know 3dsMax and other software normally handles files this way.