Am still messing with data around houdini. In the file provided a simple technique is used, but achieves the bullet time or time freeze effect over the usual 10 sec houdini timeline(24 Fps).
have fun, let it sim/cache first Ok
Khermah.
3 part video:-
http://www.youtube.com/watch?v=Hi4LayiQrnQ [youtube.com]
————————————————————————
http://www.youtube.com/user/Khermah [youtube.com]
————————————————————————
Bullet Time Dynamics. Time freeze. ?Matrix?
7373 6 2-
- khermah
- Member
- 33 posts
- Joined: May 2006
- Offline
-
- Soothsayer
- Member
- 875 posts
- Joined: Oct. 2008
- Offline
-
- fsimerey
- Member
- 279 posts
- Joined: Dec. 2009
- Offline
-
- Soothsayer
- Member
- 875 posts
- Joined: Oct. 2008
- Offline
Old post, but I am working on something similar now and I wonder if this chop effect can be done when the pointcount of the original geometry changes?
I set up a testfile with a geometry that changes pointcount.
Is there a technique with chops that takes this into account?
I suppose the organize by attribute option in the geometry chop would be useful, but how can I give a unique and unchanching id attribute to every point?
I set up a testfile with a geometry that changes pointcount.
Is there a technique with chops that takes this into account?
I suppose the organize by attribute option in the geometry chop would be useful, but how can I give a unique and unchanching id attribute to every point?
Edited by - Oct. 7, 2010 04:05:15
--
Jobless
Jobless
-
- Soothsayer
- Member
- 875 posts
- Joined: Oct. 2008
- Offline
-
- Soothsayer
- Member
- 875 posts
- Joined: Oct. 2008
- Offline
One I idea I have is this:
If the total point count remains constant the points retain the same id. A change in point count tells us that we require to re-assign a new id to points. If the point count was to strictly increase or decrease and if we set this new id to something like:
rand($PT)*rand($NPT)
then we probably get a new id for every point, and for small geometries this should not repeat.
However, it is not a very good idea but perhaps somebody can elaborate it?
I am also not sure how to use the “Organize by Attributes” option in the geometry CHOP. If anybody knows of an example I'd be happy to learn from it.
If the total point count remains constant the points retain the same id. A change in point count tells us that we require to re-assign a new id to points. If the point count was to strictly increase or decrease and if we set this new id to something like:
rand($PT)*rand($NPT)
then we probably get a new id for every point, and for small geometries this should not repeat.
However, it is not a very good idea but perhaps somebody can elaborate it?
I am also not sure how to use the “Organize by Attributes” option in the geometry CHOP. If anybody knows of an example I'd be happy to learn from it.
--
Jobless
Jobless
-
- Soothsayer
- Member
- 875 posts
- Joined: Oct. 2008
- Offline
For the record: I have a half-baked solution for the case where the point count changes on known frames. In that case, the curve in the constant channel that feeds the lookup chop can be keyed on that very frame and altered afterwards.
There is some relationship between the slope of the retiming curve and the change in pointcounts but I don't understand it well enough.
There is some relationship between the slope of the retiming curve and the change in pointcounts but I don't understand it well enough.
--
Jobless
Jobless
-
- Quick Links


