Search the Community
Showing results for tags 'clip'.
Found 5 results
-
Hi, I'm working on a multi-agent crowd setup and am wondering if anyone has any insight into how to properly alter clip settings when multiple agents have the same clip name? for example, I have AgentA --> walkClip AgentB --> walkClip Right now, if I add a crowd state called 'walkClip' to my crowd simulation both of the agent types work correctly with it. My issues is if I want to speed up the cycle for AgentA, and slow down the cycle for AgentB each in their own crowd state node how would I go about doing that? Currently I can only seem to change their properties together in the 'walkClip' agent state node. I've been reading through the docs, and it seems like houdini understands that they are different cycles by pairing them with their agentname attribute? On a previous project I worked on I noticed that one of my agents was importing it's cycle name using the full name of the bclip on disk - this would separate the cycles enough for me to modify their speeds independently, however with this new project I'm not sure how to get them to pick up the full bclip name at the agent load step - anyone have any ideas how you could trigger this? eg: 'AgentB_clip.walkClip.bclip' instead of 'walkClip' any help / insights much appreciated. Thanks!
-
Hello, I'm threading new ground here, trying to "get" crowd sims. I've done particles, fluids, FEM, and RBD so far and I aspire to orchestrate a whole horde of people running down the I was playing with the set up, but I couldn't find out how to add vertex animation into it. I have 2 fbxs that I prepared, of a simple vellum cloth ball that's been retimed to look like its bouncing and jiggling in place. I'll add them to the post. Now, my main question is about how I'd go about getting that info into the agent. Is it even possible? The whole crowds system seems to be awfully "bone centered". One solution I could think of was to use the game tools skinning converter, but that is absolutely sub optimal, as I'd lose the wrinkles of the ball. I saw this thread: https://forums.odforce.net/topic/32029-crowds-with-marvelous-designer/ In which user ATOM pointed out you can use MDD caches, but if that's the case, how do you generate a .mdd, and integrate it into the sim? I'm really curious as to what you guys have to say. I'm not afraid of VEX so don't hold back on that front haha -- ball_walking.fbx ball_idle.fbx
-
Hello, This is very strange behavior, wondering if someone knows whats going on or if this is a bug. So I have a simple cloth set up involving a rest shape and fracture. I noticed when I had both rest shape (or target deformation) and fracture enabled, my cloth would randomly move in strange patterns. I could not figure out what was causing this, it's almost like extra velocity is being added. I got lucky and decided to delete the bottom section of the sphere rather than use a clip node. For some reason, that fixed the problem. Why would using the clip node cause all this weirdness as opposed to deleting the geometry with blast. I added a switch node in my scene so you can see both variations. thanks in advance cloth.hip
-
I have some prims that I need to drive through a Clip SOP. Each prim has got its own clipping plane origin and direction, previously computed and stored in prim vector attributes, eg v@clipOrigin and v@clipDirection I would like to connect these attribute values to the inputs of a Clip SOP: Origin & Direction parameters but cannot figure out how to do it. I tried (just showing the Origin.x parameter of the Clip here, but the y/z and the Direction.x/y/z would be analogous: @clipOrigin.x no error, but wrong result (alway zero) v@clipOrigin.x error: unable to evaluate expression - extra tokens detected in expression ch("../nodeJustAboveClip/clipOrigin/x") error (bad parameter reference) hou.ch("../nodeJustAboveClip/clipOrigin/x") error (unknown function in expression) also tried with a spare parameter I realize the clipOrigin is not a parameter on my nodeJustAboveClip SOP, but rather an attribute on its prim output. So 3-5 are likely just plain wrong. Just in case Clip assumes it is running over points rather than prims, I also inserted a Attribute Promote SOP to copy the prim v@clipOrigin to each point. With version 1 above, the result is the same - no error but always zero. If you know how to do this, thank you in advance ! This is in Houdini 16.5 Indie -------- SOLVED: I was using the wrong syntax in the parameter expressions. You can pick up prim or detail attributes in SOP (not just Clip SOP) parameters like this: prim(surface_node, prim_num, attrib_name, attrib_index) detail(surface_node, attrib_name, attrib_index) details(surface_node, attribute) point(surface_node, point_number, attribute, index) Note these are VEX expression functions used in parameter expression one-liners, not regular VEX functions used in wrangles. The signatures of the functions are slightly different.
-
Hi everyone! I'm currently working on a fairly "illuminated" scene, where I use loads of dim instanced point lights. Normal lights provide the option of setting an attenuation radius, which usually speeds up rendertime a lot, but the "light template" does not provide that option. As shaders I use the asadlight and rayshadow. Asadlight has something similar, which is an attenuation ramp that gets multiplied with the attenuation, so you can set it to black after a certain distance. I know this should visually have the same effect, but is it as efficient as the radius option in the normal point light? Is there any other way to "clip" light? The reason I'm asking about this is because I set the attenuation radius to black after a certain distance. I set up a render and it takes ages, despite the fact, that its only in range of about 4 lights. Once I deactivate the other lights, the render goes super fast. Any advice, experience, wisdom or other info is much appreciated! Thanks a lot Sustaxata
