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.

Skybar

Members
  • Content count

    943
  • Joined

  • Last visited

  • Days Won

    22

Community Reputation

233 Excellent

About Skybar

Personal Information

  • Name David
  • Location Sweden

Recent Profile Visitors

6,341 profile views
  1. The video says Houdini so yes, it is clearly possible. He even says in the comments how he did it, so yeah there you go.
  2. Yeah ok that I can understand. Maybe using $FF is used so rarely it doesnt really warrant its own solution. But fact is its still annoying
  3. Maybe try grains with constraints.
  4. Sure but thats not what I'm asking. If you have a sequence like: file.1.bgeo, file.1.5.bgeo, file.2.bgeo, file.2.5.bgeo - it wont interpret that as $FF, but it will make multiple sequences like file.1.$F.bgeo and file.2.$F.bgeo. But I want the whole thing to be file.$FF.bgeo. I'm doing this very rarely, but when I do its always annoying.
  5. It shows up like file.1.$F.bgeo, when it should be 1.2, file.$FF.bgeo. In other words I get tons of small $F sequences instead of one $FF - so you cant just select it without modifying the path afterwards.
  6. It happens to me all the time in soplevel though, and sometimes it's hard to know which node is stuck. But yes I've also noticed this seems to help.
  7. Pop Spin doesnt rotate the normals, it rotates the particles orient attribute. So turn on "display particle origins" in the viewport and you can see that yes, they do spin around the axis you specified - in this case Y.
  8. Depends what direction you want to go, you can script as much or as little as you want. Vex and houdini expressions usually come with the territory when learning and working with houdini. It might be worth looking into that a bit more if you are interested. Although python can be powerful, it is very rarely that I wish I knew it. Maybe once every few months I go "damn this would be easy in python". But I'd rather spend my time elsewhere because I dont particularily like coding. If all you know/want to know is some expressions and vops - you dont really need more if you feel comfortable. A few of the best FX artists I know are more artistic in nature and dont know much scripting at all. But the opposite is true as well, of course. Do you like coding? By all means go ahead, it will be fun. If you dont, dont worry and go make cool stuff all the same. It all comes down to doing what you like and giving it your best.
  9. Make $FF show up properly for sequences with substeps in file dialogs.
  10. http://www.sidefx.com/docs/houdini/nodes/dop/staticsolver
  11. No need for loops and stuff. Take one VDB and put it in the first input, merge all the others and put it in the second input. On the VDB Combine choose "Flatten All B into A" and choose the appropriate operation, like SDF Union for sdfs.
  12. You can create custom visualizers if you press D in the viewport -> Visualizers -> click the +.
  13. If you are using the default setup, it will use the surface field as well to fill in. Thats probably what you are seeing.
  14. Enable "Keep in Bounding Regions" and select Bounding Object in the menu.
  15. That sounds interesting :). I'd have to do some tests as well, cheers!