Normal Direction for copy to points or copy stamp
11778 6 4
-
- ALMINA
- Member
- 154 posts
- Joined: March 2016
- Offline
-
- Simon van de Lagemaat2
- Member
- 116 posts
- Joined: April 2016
- Offline
-
- ALMINA
- Member
- 154 posts
- Joined: March 2016
- Offline
-
- ALMINA
- Member
- 154 posts
- Joined: March 2016
- Offline
-
- AkashModi
- Member
- 1 posts
- Joined: Dec. 2022
- Offline
-
- toadstorm
- Member
- 359 posts
- Joined: April 2017
- Offline
Copy to Points uses a number of different possible attributes to determine the orientation of copies. Those attributes include:
3@transform
p@orient
p@rot
v@N
v@up
v@v
At a minimum you need to provide an N attribute as the "forward" direction for each copy. That said, if you don't also provide an up attribute, Houdini is going to guess at the up direction, and it will often guess wrong. Create an up attribute in a Point Wrangle on the template points like this:
If you want a detailed breakdown of how these attributes are meant to work, look here [www.toadstorm.com].
3@transform
p@orient
p@rot
v@N
v@up
v@v
At a minimum you need to provide an N attribute as the "forward" direction for each copy. That said, if you don't also provide an up attribute, Houdini is going to guess at the up direction, and it will often guess wrong. Create an up attribute in a Point Wrangle on the template points like this:
v@up = {0,1,0};
If you want a detailed breakdown of how these attributes are meant to work, look here [www.toadstorm.com].
MOPs (Motion Operators for Houdini): http://www.motionoperators.com [www.motionoperators.com]
-
- Len
- Member
- 132 posts
- Joined: July 2007
- Offline
Another issue to watch out for is that @orient (and likely some other attributes that @toadstorm listed above) will override the use of @N and @up in Copy To Points.
I've unknowingly had garbage values for @orient being passed from previous nodes and they break the @N and @up behavior and leave me scratching my head until I notice. The lesson: Clean out old attributes and groups when you can!
I've unknowingly had garbage values for @orient being passed from previous nodes and they break the @N and @up behavior and leave me scratching my head until I notice. The lesson: Clean out old attributes and groups when you can!
-
- Quick Links