Ambar Singh
bloodhawk
About Me
EXPERTISE
Student
INDUSTRY
Film/TV
Connect
LOCATION
United States
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Make particles only attract towards specific curves in a Simulation with Particles flowing along input curves. Aug. 3, 2016, 7:09 p.m.
Here is a simplified version. Rather too simplified lol.
Make particles only attract towards specific curves in a Simulation with Particles flowing along input curves. Aug. 2, 2016, 8:43 p.m.
Hey guys,
Kinda Intermediate at Houdini and a recent full time convert from the 3DSMAX/TP world.
I have been working on a tool, where the user can easily plug-in curves and generate art direct able particle flow along the input curves.
Its about 90% done, and it works great with curves that are not too close to each other or don't intersect each other at too many points. How ever in certain scenarios. like multiple inward spiral curves intersecting each other, since the POPVOP system is based on Particle Cloud Search :
- PC Open to look for particles close to the curve points.
- Use those points and push them along the length of the curve using the curve tangents.
, the particles get attracted towards either curve based on the search radius and no. of search points. This is definitely understandable, on why its happening. But is there any way to lock/tie the particles to specific curves only?
The Radius and No. of Points parameters give it a lot of control for most scenarios, but the one mentioned above. Obviously there are a lot more parameters that i have added for dictating the flow behaviour.
But the main solution that i can think of is to have the “found” particle only follow the curve and be affected by the parameters along that curve ONLY.
Maybe have a POPVOP decide groups for the curves/particles?
I have never worked with groups in POPNET, so im pretty much lost.
Unfortunately because of my limited knowledge at Houdini i haven't been able to figure out how to achieve this. Would really appreciate some help on this.
Ill try to post a simplified version of my asset later tonight.
Kinda Intermediate at Houdini and a recent full time convert from the 3DSMAX/TP world.
I have been working on a tool, where the user can easily plug-in curves and generate art direct able particle flow along the input curves.
Its about 90% done, and it works great with curves that are not too close to each other or don't intersect each other at too many points. How ever in certain scenarios. like multiple inward spiral curves intersecting each other, since the POPVOP system is based on Particle Cloud Search :
- PC Open to look for particles close to the curve points.
- Use those points and push them along the length of the curve using the curve tangents.
, the particles get attracted towards either curve based on the search radius and no. of search points. This is definitely understandable, on why its happening. But is there any way to lock/tie the particles to specific curves only?
The Radius and No. of Points parameters give it a lot of control for most scenarios, but the one mentioned above. Obviously there are a lot more parameters that i have added for dictating the flow behaviour.
But the main solution that i can think of is to have the “found” particle only follow the curve and be affected by the parameters along that curve ONLY.
Maybe have a POPVOP decide groups for the curves/particles?
I have never worked with groups in POPNET, so im pretty much lost.
Unfortunately because of my limited knowledge at Houdini i haven't been able to figure out how to achieve this. Would really appreciate some help on this.
Ill try to post a simplified version of my asset later tonight.
How to extract imported Alembic file contents in Houdini? July 26, 2016, 2:43 p.m.
Drop a geo node on the obj level and pipe the Alembic node into it.
Then go into the geo node and drop in an Alembic SOP node and in the object patch add : `chs(opinputpath(“..”,0)+“/full_path”)`
This should get the Alembic Geo into the SOP level and then you can use a combination of Delete + Group nodes or just use multiple delete nodes to extract objects/meshes/groups. And then convert them.
Then go into the geo node and drop in an Alembic SOP node and in the object patch add : `chs(opinputpath(“..”,0)+“/full_path”)`
This should get the Alembic Geo into the SOP level and then you can use a combination of Delete + Group nodes or just use multiple delete nodes to extract objects/meshes/groups. And then convert them.