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.

Sifis

Members
  • Content count

    108
  • Joined

  • Last visited

Community Reputation

26 Excellent

About Sifis

  • Rank
    Initiate
  • Birthday 02/07/1976

Contact Methods

  • Skype iosifkefalas

Personal Information

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

Recent Profile Visitors

6,015 profile views
  1. Nice Stuff! and yes, a video recording would be great.
  2. Top quality work Peter, Congrats!
  3. Amazing!
  4. Very good indeed. Thank you Tomas.
  5. 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
  6. 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
  7. 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).
  8. 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
  9. 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.
  10. 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
  11. Very nice R&D Nick, interesting approach to viscous liquid, I'd like to have a look at the inner workings of your solver if you'd like to share an example hip.
  12. Amazing work Christos, I also like the fact that everything was rendered with Mantra.
  13. Hi, I know that we can add rendering properties in several levels of houdini as in primitives, objects, cameras and output drivers. The thing I've noticed though, is that some rendering properties work well at object or primitive level and some don't. For example, when I tried to add "opacity limit" to two objects and set different values, it didn't override the opacity limit setting of the output driver. In another case though, when I added reflection limit in object level, it worked as it should which lead me to the conclusion that some rendering properties work well in object level and some are uniform. This makes sense for some properties but I don't see the reason why "opacity limit" shouldn't work at object level. Is this as it suppose to work or am I doing something completely wrong? Any advise could help.
  14. Excellent, It's always nice when new TD teaching coming up. Good luck Nick!