Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


markinglevfx last won the day on February 13

markinglevfx had the most liked content!

Community Reputation

46 Excellent

1 Follower

About markinglevfx

  • Rank

Contact Methods

  • Website URL

Personal Information

  • Name
  • Location
    New York

Recent Profile Visitors

1,501 profile views
  1. Python - Integer to String

    Bingo. Thanks for the help guys!
  2. Python - Integer to String

    I did have 'str' set as a variable elsewhere in the code. But even after I got rid of it, the error persisted. But I have managed to get it working now. I solved it by making a new Python SOP and using the same code - initially I was copy/pasting lines and seeing where it broke. Weird how I now have two python nodes side by side with the same inputs, the old one errors and the new one is fine.
  3. Python - Integer to String

    In the Python SOP, I've run into a wall trying to get an integer converted to a string. In the larger picture, I'm trying to subtract 1 from a value which is currently part of a string. There are probably neater ways to write these steps, but I'm fairly new to Python so I'm writing it all out to make things easier to follow. I start with a string such as: string = "f27" Then remove the 'f' like so: string = string[1:] Convert it to an integer: integer = int(string) Subtract 1 from the value: integer -= 1 set new string string_new = "f" + str(integer) The last line returns an error on the Python SOP: TypeError: str() object is not callable. This is confusing because these same steps work just fine in the Python shell. Is there an alternative to str(), or am I using it wrong?
  4. Solids from Gases

    Converting your volume to VDB (class: SDF), followed by a VDB smooth and a convert to polys should do the trick pyro_to_poly_v001.hip
  5. Replicating Coins

    I did a little breakdown of the replicating effect in a blog post - check it out if you like! There's a free .hip to download included. https://www.markinglevfx.com/post/replicating-coins-hip-breakdown
  6. Replicating Coins

    A little experiment I like to nickname: 'Life as a VFX Artist'
  7. You can use this code in your switch. Currently you're using the loop iteration in the switch, but the point/loop order changes as new points come in so it's different each frame. By referencing each point's id attribute when selecting the object it instances you can keep them constant throughout. Hope it this makes sense. Adjust the max fit value (currently 1) to account for more instance objects fit01(rand(point("../foreach_begin1/", 0, "id", 0)), 0, 1)
  8. Bake parameters into render or flipbook?

    The vm_image_comment is on the mantra node by default so technically it belongs there. You have to render from the mantra node (not just flipbook) to display the comment.
  9. Pivot at the bottom of an object

    Write this into your pivot translate to get the minimum y position of the input geo: bbox(opinputpath(".", 0), D_YMIN) opinputpath(".", 0) gets the path of the first input of the current node. https://www.sidefx.com/docs/houdini/expressions/opinputpath.html bbox() returns the bounding box info of a node, in this case we want to use "D_YMIN" to get the minimum y position. https://www.sidefx.com/docs/houdini/expressions/bbox.html edit: forgot to add the centroid expressions for the x and z values, see Tomas' reply below
  10. Modify an existing group

    Does this help? Click the arrow next to the base group parameter deselect the edges using ctrl hit enter (in viewport) when done
  11. Unbound particles to velocity field ?

    The air resistance on the advect by volume pop was turned up to 150. This acts as a drag to keep the particles within the velocity field and prevent them from flying off. You'd have to turn this down for the particles to break free from the vel field - it's a balancing act to keep them revolving around the torus. Also this air resistance acts on the particles regardless of if they're inheriting any velocity from the volume. So you'll need to remove this air resistance force on any particles which are not within reach of the velocity field. I've done this by using a pop group and a bounding box area. velField_gravity_fix.hipnc
  12. Import Records into PopNet

    Seems like you can. By setting the pop solver to add 'impact data' instead of hit attributes. And set the Data Path and Record on the Dop Import Records node to 'Impacts'. When you're working with a new node and you're not sure exactly how to use it, always check the help documentation. In this case there was an example scene which helped a lot. https://www.sidefx.com/docs/houdini/nodes/sop/dopimportrecords.html dop_import_records.hipnc
  13. Import Records into PopNet

    Enable hit attributes in the pop solver, and isolate the points with collision data at SOP level? impact_records_fix.hipnc
  14. Particles not emitting along vector attribute ?

    To have them flowing around the torus you'd be better off using 'advect from volume'. This way your particle's velocities are constantly being updated, rather than just inherited at the start like in your previous setup. particles_advect_by_volume.hipnc
  15. Bake parameters into render or flipbook?

    This should be what you're looking for. Add the viewport comment render parameter to a camera, and flipbook as you would normally. Channel reference the attribute(s) you want displayed within backticks. Example file of mine attached! flipbook_comment_v001.hip