The new Sweep2 has a bug？

Replies to This Discussion

Permalink Reply by David Rutten on May 12, 2013 at 5:30am

I can repeat that. I'm unable to make the new SDK Sweep method work as accurately as the old one. It's a Rhino SDK problem though but I'll see if someone in the Seattle office can fix it.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by rainake on May 12, 2013 at 7:06am

That is to say, it's indeed a bug?
I thought to upgrade my former definition(0.9.0014), the bug stopped me. Maybe I should stay with 0.9.0014 for the time being.

old Sweep2

new Sweep2

Permalink Reply by David Rutten on May 12, 2013 at 7:37am

It appears to be a bug. I thought that the new Sweep2 functionality in RhinoCommon used the same algorithm as the Sweep2 command, but I'm getting different results.

You can always use the old Sweep2 component though, even in the latest version. Either drag this text into the canvas:

{F2935F94-8E47-45df-919B-797044C1BACD}

or type a # in the pop-up window to see legacy components as well:

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by rainake on May 12, 2013 at 8:14am

Thanks David.

Will you fix it in the next release?