Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About skomdra

  • Rank

Personal Information

  • Name
    Drasko Ivezic
  • Location
  1. Hi Dan. Not a crowd guy, but just a question, why don't you split your fbx based on @shop_materialpath and make separate agents? Isn't agent just a packed primitive? Even if your geo is binded on the skeleton it should still respect your selection based on the primitive attribute. But probably someone with a crowd experience should offer some advice here.
  2. Can we achieve this effect in SOPs?

    This can be done in sops. I have to think exactly how, but my guess would be, try with bend sop which has direction driven by noise, or I would try to do some sort of 2D noise displacement with a falloff attribute to keep the bottom at place and top part movable. This can be with lines and sweep nodes turned into geometry. Plenty of ways. But you have to dig into sops and experiment, first. Try MOPs, cgwiki, there are plenty of resources out there.
  3. I have to check exactly what you want to do, maybe make a small prototype and upload a hip file? But if you need it to update during time, then I think you would need to use a sop solver, which I am not very familiar with but it seems very simple to setup.
  4. Maybe use a timeshift node and transfer velocities on the first frame of the sim, make a group by velocity and transfer the group to the moving points after? Though I don't see why wouldn't you select part of the sim with the group node, group by bound to select part of the sim which you already know it is more important for the final output? You can even animate bound if you need it to follow the steps and update it based on another sop which is in the second input, etc.
  5. hm, measure sop + switch? I guess there is no volume when the voxels are too big? Need to see the hip file to give the more precise answer.
  6. Procedural modeling & unwrapping

    Hi, there are few nodes for UV creation and tons of free resources on the net how to procedurally UV. The lazy way is to use Labs tools and find Auto UV node, and play with it. Since it is a hda, you can also unlock it and look inside how it is setup. For the second question, make lo poly and high poly part of the same network. Have the low poly Display tag on and on the high poly turn on the render tag. Use this to instance. https://www.sidefx.com/docs/houdini/nodes/sop/index.html
  7. Set and keep texture projection scale

    https://www.sidefx.com/docs/houdini/nodes/sop/uvproject.html and use example to understand how it works. Good luck!
  8. BIG FBX import problems

    Hi, did you try to use the file sop? Or how are you importing?
  9. Redshift totally failed

    PATH = "C:/ProgramData/Redshift/bin;$PATH"<font></font>" I am not sure this will work, are you sure this is the right setting? Syntax is wrong, you have unclosed quotation mark and why is this font even here? Maybe check at he redshift forum exact path and edit this. My guess is this line is bothering you.
  10. Do I understand right, you want to alternate between two objects? You can create a new integer point attribute on your curve sop and then use that to drive the value of the switch by taking a point function into the switch. To alternate between two values you can first create a group by range at the curve and that way select every second point, (check Group by Range in the documentation). Then either by Attribute Wrangle or some other way, create a new point attribute, best would be integer, and then assign the value 0 to one and 1 to another group. Go in the documentation check the point expression, for-loop examples, how to copy random geometry, etc, you will figure it out. Good luck !
  11. Offset time on Copy to Points

    Many ways to do this. My take: Put a timeshift node after the file node and add foreach point with the copy to points node second input in the loop coming from the line (look at the picture of the graph). Click on the Create Meta Input Node. When it creates the node, rename it to something shorter, which you can find later, for example, "shift_iteration". Go to your timeshift node and add a new integer parameter in your parameter interface (in my case I called it shift). Edit the Frame parameter in the timeshift node - the default is $F, but you can add data which comes from for-loop by using detail function and taking the value of the attribute "itteration" on the Meta Input Node (in this example: "shift_iteration"). You can check the detail function in documentation, but it is very simple - detail("addres_to_the_node", "attribute_name", index). Multiply this value to the offset parameter by using ch() function and delete it from the current frame ($F). The full expression in your timeshift frame parameter will be: $F-detail("../shift_iteration", "iteration", 0)*ch("shift"). By changing the value of the shift parameter on the timeshift node you are making the animation to delay number of frames you define it. If you want them to start at random times, you can either use the sort node at the line, to change the ptnum attribute. Or you can use another expression on the new parameter, by putting shift_iteration into rand function. Good luck
  12. thanatos_v4_share.hiplc