Not BadObject becomes "Bad" after Moving

Rhino Rhino for Windows
#1

Hi Guys,
I originally thought this was a problem with grasshopper but after repeating the grasshopper process in plain Rhino the same thing happens there:
I have a curve, positioned about 3600 mm from the origin which seems normal: When I run the SelBadObjects command it doesn’t get selected.

image
image.png1249×740 48.6 KB

Now, after I move the curve a bit in any direction and run the SelBadObjects command, it suddenly became a Bad object:
image
image.png1021×708 47.3 KB

This ruins the grasshopper definition I made. Is this a bug or what is it causing this?
191008 MoveBad.3dm (26.3 KB)

#2

How did you create this curve? It has two huge arc segments which i assume are the problem here:

image
image.png783×1216 222 KB

Also whenever you move an object via the gumball rhino deletes it and then adds it back to the document with the transform value from the gumball, so it seems your polycurve does not satisfy rhinos inner validity checks there.

#3

Interestingly exploding the polycurve gives arcs with sensible radii. But joining them back up gives a few with huge radii.

#4

Its the “lines” connecting the top and bottom half which are actually huge arcs even when exploding

image
image.png1732×1235 322 KB

Replacing those with actual lines gives a polycurve which plays nicely and is within reasonable tolerance

image
image.png1720×1094 167 KB

#5

@siemen,

Here is a naive ghpython component which checks arc segments inside polycurves if they are over a specified maximum radius and replace them with straight lines from the arc start to arc end points.

This should fix your gh file

image
image.png821×313 25.6 KB

fixArcs.gh (4.3 KB)

Also in my opinion is it good that rhino marks such polycurves is bad objects (although not consistently) since no CNC or LaserCutter will process arcs of such radii and angles.

1 Like
#6

Awesome bughunting! Thanks a lot for the help!
The curve was made by a client of mine, possibly using a script.