I would like to be able to view the velocity created by a trail SOP. I know you can map via point SOP > add velocity > $NX , $NY , $NZ but of course this is normalised.
any ideas ?
r
viewing velocity in SOPs
4862 7 1- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
- wolfwood
- Member
- 4261 posts
- Joined: July 2005
- Offline
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
- keyframe
- Member
- 1529 posts
- Joined: July 2005
- Offline
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
yeah sorry about that bit of confusion v is what I am talking about. I saw an interesting post where somebody wanted to take their animated geometry and use the v attribute from the geometry to drive the vel in a fluid sim. Hense my interest in seeing just how much velocity my geometry is creating
r
r
Gone fishing
- keyframe
- Member
- 1529 posts
- Joined: July 2005
- Offline
So I finally had a chance to take a look at your file…
What's happening there, is that the velocity is calculated BEFORE the world space xform is being applied. ie: the as far as the trail sop is concerned, your torus is completely static. The sop chain cooks, then the geometry is transformed.
Two ways around this:
(1) apply the transformation at the sop level (it becomes a deformation at this point) – then cook the trail sop.
(2) object_merge your world-space xform'ed into a new object, and cook the xform there. again, a deformation at this point.
Holler if you need a sample file.
G
ps: your OTHER sanity checker in situations like this is the spreadsheet. If you pop it open and look at the ‘v’ attribute in your existing file, you'll see that it's all 0's – which lead me to look elsewhere for why this velocity wasn't being calculated as expected.
What's happening there, is that the velocity is calculated BEFORE the world space xform is being applied. ie: the as far as the trail sop is concerned, your torus is completely static. The sop chain cooks, then the geometry is transformed.
Two ways around this:
(1) apply the transformation at the sop level (it becomes a deformation at this point) – then cook the trail sop.
(2) object_merge your world-space xform'ed into a new object, and cook the xform there. again, a deformation at this point.
Holler if you need a sample file.
G
ps: your OTHER sanity checker in situations like this is the spreadsheet. If you pop it open and look at the ‘v’ attribute in your existing file, you'll see that it's all 0's – which lead me to look elsewhere for why this velocity wasn't being calculated as expected.
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
- jesta
- Member
- 311 posts
- Joined: July 2005
- Offline
-
- Quick Links