cookie error again
6295 7 1- oat
- Member
- 479 posts
- Joined: Dec. 2009
- Offline
Hi, guys,
I ran into cookie error again when trying to boolean a polygon using another geometry.
please refer to the images attached for the problematic result and the result I'm expecting.
can you help to take a look and advise me on how to solve this problem?
Thanks!
(the digital asset files used are also attached)
I ran into cookie error again when trying to boolean a polygon using another geometry.
please refer to the images attached for the problematic result and the result I'm expecting.
can you help to take a look and advise me on how to solve this problem?
Thanks!
(the digital asset files used are also attached)
- LFX
- Member
- 67 posts
- Joined: Jan. 2009
- Offline
- tamte
- Member
- 8785 posts
- Joined: July 2007
- Online
- oat
- Member
- 479 posts
- Joined: Dec. 2009
- Offline
Hi, tamti, I've added a fuse node before the 2nd input of the problematic cookie node, but this still doesn't solve the problem.
I've also tried some of the options of the fuse node, but still can't get the cookie node to produce the right result I want.
Can you help to take a look of the hip I uploaded above and advise me on how to get the cookie node works?
Thank you!
I've also tried some of the options of the fuse node, but still can't get the cookie node to produce the right result I want.
Can you help to take a look of the hip I uploaded above and advise me on how to get the cookie node works?
Thank you!
- oat
- Member
- 479 posts
- Joined: Dec. 2009
- Offline
- LFX
- Member
- 67 posts
- Joined: Jan. 2009
- Offline
- tamte
- Member
- 8785 posts
- Joined: July 2007
- Online
you are using difficult geometry for cookie, you have many indifidual closed objects, touching at some sides
it's usually better to use just one closed geometry for each input
what i've done here is simple foreach loop which will try to union all groups of the second input to get minimum number of closed geometries
then this cookie will behave more predictable
i've also slightly scaled first input geometry, because it is not for cookie if you are trying to cut along already existing edge (in your case boundaries)
it's usually better to use just one closed geometry for each input
what i've done here is simple foreach loop which will try to union all groups of the second input to get minimum number of closed geometries
then this cookie will behave more predictable
i've also slightly scaled first input geometry, because it is not for cookie if you are trying to cut along already existing edge (in your case boundaries)
Tomas Slancik
FX Supervisor
Method Studios, NY
FX Supervisor
Method Studios, NY
- oat
- Member
- 479 posts
- Joined: Dec. 2009
- Offline
-
- Quick Links