Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by edward

  1. If you mirror all the IK bones using the object viewport's Mirror tool, it should copy all the IK solver and goals for you.
  2. Hand-keyed is probably still "audio driven animation" albeit with a lot of manual work. The other aspect is that there's nothing wrong with manual tweaking on top of a procedural solution as well.
  3. How would $FD / $FFD behave differently to solve the issues?
  4. The traditional resource for this is the e-book "Simultaneous Music, Animation, and Sound with Houdini" by Andrew Lowell. However, his site is now down so I don't know if it's still available for purchase. However, I think Peter Quint's tutorials are still available: https://www.sidefx.com/tutorials/chops-and-music-driven-animation-i/ https://www.sidefx.com/tutorials/chops-and-music-driven-animation-ii/ https://www.sidefx.com/tutorials/chops-and-music-driven-animation-iii/
  5. What I was trying to say is that if it did get interpreted as $FF, then cases like the example I gave would get the $SHOT into the frame, thus breaking the workflow for the people using that convention.
  6. I'm pretty sure that this link error: undefined symbol: _ZN7openvdb11v3_3_0_sesi4math9TransformC1ERKSt10shared_ptrINS1_7MapBaseEE is caused by not compiling everything with -DOPENVDB_3_ABI_COMPATIBLE. One of the differences when this is defined is whether OpenVDB uses std::shared_ptr or boost::shared_ptr.
  7. I think the modern workflow is to use TopoBuild with something like the same geometry fed into both inputs.
  8. I pretty sure I've seen sequences from customers where they used conventions like: file.$SEQ.$SHOT.$F.bgeo ...
  9. In general, full round-tripping is not feasible because it won't work unless Houdini solved the HIK rig exactly the same (eg. use the same source code) as the other DCC packages.
  10. H16 requires gcc 4.8 or later. To be safe I think I would try gcc 4.8
  11. Try adding this to your Makefile THIRDPARTYDEFS += -DOPENVDB_3_ABI_COMPATIBLE
  12. You need to compile with -DOPENVDB_3_ABI_COMPATIBLE (ie. define OPENVDB_3_ABI_COMPATIBLE) when you build your HDK plugin. This was accidentally left out of hcustom in early builds and looks like it's missing in the shipped Makefiles still.
  13. What do you mean exactly by "properly" ?
  14. Why does that require full round-tripping? It requires that you round trip, sure. However, you don't need a working HIK rig back into Maya after you've processed it in Houdini. You just need something back into Maya that you can render as expected. ie. you can tolerate baking of information when exporting from Houdini.
  15. I'm not sure that your mentioned uses cases for the FBX really requires full round tripping, which is why I was asking what you what wanted to see in HIK import support. HIK is solver metadata in the FBX file, so I think the most feasible thing as an RFE would be to just ensure that Houdini can import animation from an HIK rig.
  16. VDB Combine can used to take the union of all merged VDB primitives from the second input, if you set the operation to "Flatten All B into A". So you can just use Merge for all your VDB primitives and pipe them into the second input of VDB Combine. For the first input, you can just use an empty VDB of the appropriate voxel size created using the VDB SOP.
  17. In Houdini, the segments between keys contain expressions that are evaluated. When you enter expressions in Houdini parameters, a key is created to contain the expression for evaluation. For bezier() keys, the bezier() expression just takes the values/slopes/accels of the adjacent keys and gives you the result of a bezier interpolation. See this post for a sample expression for linear(): https://www.sidefx.com/forum/topic/13381/?page=1#post-63380 So for something like your tween function, it would just live on the segment and know exactly the time range it needs. Maybe it just needs to passed "bounce", but then maybe you should have a class of tween functions like bounce(), etc.
  18. So it sounds like you're not interested in the full body IK aspect of it? If you just care to import HIK rigs via FBX, and then export then that probably works right now. On export, I think you'll lose the full body IK stuff though as Houdini doesn't know to import those.
  19. What do you want to do with the HIK rig in Houdini?
  20. Hey Alexey, love your videos! I just have to watch them on mute though.
  21. It's hard to tell from these pics and what you've told us ... But why can't you just smooth the spheres and tubes separately like in your first image, and then use vdbcombine to "merge" the spheres and tubes together? Only use Convert VDB *after* you've combined them.
  22. From the main menu, Edit > Preferences > General User Interface > Global UI Size. Change it to High DPI. http://www.sidefx.com/docs/houdini/ref/windows/mainprefs#ui
  23. I wonder if using VDBs and VDB Morph SDF would give nicer blending results than a Sequence Blend.
  24. Set the environment variable HOUDINI_OGL_FAST_BONES to 0
  25. Sounds sort of like the Partition SOP? http://www.sidefx.com/docs/houdini/nodes/sop/partition As for your last question, well, only you can tell us whether you're high.