Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Sifis last won the day on April 2 2013

Sifis had the most liked content!

About Sifis

  • Birthday 02/07/1976

Contact Methods

  • Skype

Personal Information

  • Name
  • Location
    Thessaloniki, Greece
  • Interests
    Music, VFX, travels, tech & geeky stuff

Recent Profile Visitors

7,682 profile views

Sifis's Achievements


Newbie (1/14)



  1. Hi, I know this is an old thread but seems there's no solution to this issue. I can successfully use vertex attributes using PXR_primvar nodes but I still can't make motion blur work. Pixar doesn't provide any information about this specific issue and no information exist on the internet regarding this. Any idea?
  2. Thank you IhabAli, very useful piece of code. I was scratching my head with overlapping sticky collisions for a long time.
  3. Thank you Bunker, A simple hip would be great if it's possible.
  4. Hi Skybar, I have the same problem. Can you elaborate more on this method? Thanks in advance.
  5. Nice Stuff! and yes, a video recording would be great.
  6. Very good indeed. Thank you Tomas.
  7. I also wanna correct the previous posts I made. Thanks to Eric who pointed this out, the Transform vops (current space to NDC) are not needed (that's why it was exporting different values in X and Y). Houdini just converts everything in shaders to camera space by default. So, as NDC is normalised to the output frame ratio, it's not appropriate for exporting accurate motion vectors. Here I ' ve attached a hip with the fixed shader and a Nuke script with a direct comparison between the old shader and the new one without the space transform vops. moVecTests.rar
  8. Hey Eric, I don't have RSMB right now to test it, but given some previous experience with it and the math from the link above, this Hip should work. Let me know how it goes with RSMB. rsmb_moblur_fix.hip
  9. Bind vops introduced in H12 or H12.5 and they supposedly have a faster evaluation than the old Parameter node. Actually I've never compare them in such a way to notice any speed difference, but I like bind nodes because they are much faster to set up as there are 2 options to choose when you hit the tab key: Bind and Bind export (it's actually the same node with different settings for importing or exporting an attribute).
  10. Try this one, Actually for the fur to work, You need to increase the geo samples (as you already noticed) to something greater than the default value of 1. motionVectors_Fur.rar
  11. Hmm, actually the same settings I use for curve (fur) rendering with motion vectors and had no problem. Maybe for very fine hair you need more pixel samples and geo/xform samples or try exporting the motion vectors image plane with no filtering.
  12. This is a way of exporting motion Vectors to Nuke (vector blur node), at least it works for me. I've also attached a nuke script to get the whole picture of how it works. Just render the example sequence at the default folder and open Nuke. motionVectors.rar
  • Create New...