FilletEdge command fails to make a mesh

[Thiago_Tonaco]

Problem Description: When applying a FilletEdge to a closed polysurface generated via Sweep1, the command shows a perfect preview. However, upon pressing Enter to finish, the command closes and nothing happens. No geometry is created, and no error message is displayed. Curiously, if I press Ctrl+Z immediately after, the undo stack shows that it’s reverting a step before the command even started, as if the FilletEdge was never executed.

Model Specifications:

• Object: 1 Closed Polysurface.

• Integrity: ExtractBadSrf reports no bad surfaces; ShowEdges confirms zero naked edges.

• Units/Tolerance: Millimeters. Absolute Tolerance is set to 0.001.

• Dimensions: Attempting a 0.5mm radius on a face with approximately 1.3mm of clearance.

Troubleshooting already performed:

1. RailType: Tested both RollingBall and DistBetweenRails with the same result.

2. TrimAndJoin: When set to No, Rhino successfully generates the fillet surfaces as separate objects, but fails to automate the process when set to Yes.

3. Geometry Density: The Sweep1 result has a high density of isoparms. I suspect the intersection calculation might be collapsing due to the surface complexity.

[JimCarruthers]

Actually posting the file would be much more helpful than that wall of AI text.

[Thiago_Tonaco]

ring_test.3dm (265.9 KB)

[JimCarruthers]

Works here.

I would guess it’s something about your “History” settings, that you have “lock” set to Yes.

[Lagom]

No need to “join” or work with “solids” or “edge thinking”. A fillet surface is a surface between two surfaces. The surfaces fillet fine with fillet surface.
ring_test.3dm (2.5 MB)

[Thiago_Tonaco]

works here! Thanks JimCarruthers, i just needed to turn off the lock children on Record History