Only following your description, I could not reproduce that here. Was your rectangle rounded by any chance and do you have the SplitAtTangents set to No in the Revolve command? If not, please post your 3dm file.
Only following your description, I could not reproduce that here. Was your rectangle rounded by any chance and do you have the SplitAtTangents set to No in the Revolve command? If not, please post your 3dm file.
I’ll attach a 3dm file, but it is easy to reproduce the problem.
Create a closed rectangle (no rounded corners, SplitAtTangents set to No) offset from the CPlane’s Y axis.
Revolve the rectangle around the Y axis.
Create a cutting plane through the revolved surface object.
Do a “BooleanSplit” on the revolved object with the cutting plane. The command fails with “Boolean split failed.”
Is a “Surface of Revolution” a new object type?
No, these exist in RH5 as well.
I’m sure you’re right, but something is different:
The same procedure in V5 produces a “Closed solid polysurface”, while V6 produces a “Surface of Revolution”.
These “Surface of Revolution” objects are a pain to work with. My work-around is the explode the rectangle before the revolve and then join the resulting 4 surfaces.
You’re right! Thanks. I had CreaseSplitting disabled in V6. That explains why V5 generated a polysurface (CreaseSplitting was on) while V6 generated a “Surface of Revolution”
However, I still think there is a problem in V6. If I generate a “Surface of Revolution” in V5, it will split with the BooleanSplit command where in V6 it will fail.
RichardZ
different tolerance settings in 5 and 6 maybe.
I did a few tests, and tolerance doesn’t seem to affect the problem.
John_Brock:
Do you have a specific example that works in V5 but fails in V6?
Everything works in V5, but I stumbled on a case (in V6) where splitting the Surface of Revolution object succeeds or fails depending on where the cut plane passes.
BooleanSpit seems to always fail if the cut plane passes through the center of the ring while it succeeds if the cut plane is off center!?? (Sometimes it fails when the cut plane is just slightly off center).
I don’t use kinked surfaces myself but probably there is a use for it - even though downstream commands might fail (as reported several times in the past).
What is being reported in this thread is that if you turn off crease splitting in RH5 and then revolve a rectangle and boolean split that one, that will work fine. In RH6 it does not. Is that as-designed and to be expected?
Since this has been happening for such a long time now without anyone knowing what happened, wouldn’t it be easier to set some flag on the code that changes this and warn the user when it happens?
