solid diff

Replies to This Discussion

Permalink Reply by Chris Tietjen on January 19, 2012 at 8:10am

What so you mean by 'not kill the memory'?

Permalink Reply by asaf yaacobi on January 19, 2012 at 8:15am

as a rhino user i know the difference of major Boolean and individual .  individual runs much faster, thats why im looking after the "one by one brep" method.

its a general issue

Permalink Reply by Danny Boyes on January 19, 2012 at 8:18am

I would imagine it wold be an easy thing to script, but not for native GH components

Select Objects to Boolean

Order Objects to Boolean

select first Object and second object

Boolean

Select Last object Created and Next Object in List

Boolean

Repeat until end of List

Permalink Reply by Yoann Mescam (Systemiq) on January 19, 2012 at 10:19am

My experimentations with Hoopsnake led me to the conclusion that it doesnt improve anything, because the object grows in complexity during the iteration.

Perhaps it would work better with scripting though.

Permalink Reply by David Rutten on January 19, 2012 at 10:58am

I sincerely doubt you'll be able to improve upon the native intersector by calling the native intersector from a loop in your own code.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Yoann Mescam (Systemiq) on January 19, 2012 at 11:06am

Do you mean that things work already the way Danny described above ?

Permalink Reply by asaf yaacobi on January 19, 2012 at 3:34pm

Permalink Reply by asaf yaacobi on January 19, 2012 at 3:38pm

here u can see application from rhino gold. its not that good as the one in rhinojewel5, but you can see the idea.

while brakeing the the breps into individual Brep and computing the boolean "one by one" the proces is faster and most of the time dosent reduces problems such as naked edges of surface or boolean error

maybe its a script issue after all