Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

dpap

Slicing with Intersection Analysis SOP

Hi guys!

I want replace my old "slicer" that used a foreach and the Clip sop with the new intersection analysis sop. I almost made it but the problem is that the output of the old way was 10 primitives if the slices where 10.

If use the intersectionanalysis I get  huge amount of primitives that equals the amount of polygons and the produced curves are open (unrolled). What should I do to get 10 primitives (closed) like I had the old method?

I tried the End sop to close them but it doesn't work at all. The new polyfill kinda works but it leaves two out of ten slices "urolled"..

I want to use the intersectionanalysis sop cause it's really fast.

Any suggestions?

Slicer H16.hip

Slicer H16.jpg

Share this post


Link to post
Share on other sites

One way would be to group the patches coming out of your polyfill, and then delete everything outside of the patches group.

intersection.PNG

1 person likes this

Share this post


Link to post
Share on other sites

Thank you for your answer Gavin.

I am afraid it still doesn't work in my case. Turning on the "patch" option does help but I get 8 patches instead of 10.

If  I change the sphere from polygon mesh to primitive or even nurbs I do get 10 patches, so I guess the problem has to do with the initial geometry that one uses.

If there is no way around this problem there is always gonna be some kind of geo that will make the slicer fail.

Could this be a bug?

 

 

Slicer H16.001.jpg

Slicer H16.001.hip

Share this post


Link to post
Share on other sites

It could be. It seems to be creating degenerate geo in some cases, which causes the polyfill to error out.

If it helps, I got much better results out of the boolean node. I don't know how the speed stacks up against the intersection analysis sop, but it's certainly faster that going through a for each.

SlicerH16.002.hipnc

Share this post


Link to post
Share on other sites

thanks guys, the boolean works fine for this purpose!

By the way...what's the name of the the sop that can clean up excessive points without altering the shape. Kinda like polyreduce...

I am sure there is sop that removes points that are aligned. 

I can't remember the name..:unsure:

Untitled-1.jpg

Share this post


Link to post
Share on other sites

@dpap, try Facet SOP with Remove Inline Points checked or Refine SOP set up to Unrefine. Then adjust tolerance values. Both work same most of the time.

1 person likes this

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now