Sweep tool nightmare
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I've just spent two days beating the sweep tool into submission, and seem to have the results I want for the moment. But I have no confidence that I understand the matter and fear that I have merely stumbled upon a lucky combination. Please review my tale of woe, and give some guidelines on the use of the sweep tool.
I need to sweep a profile along a three-dimensional path. My path is an Archimedean spiral about the Z axis, but which also advances along the Z axis at a linear rate. Imagine a spiral climbing a cone. I've written an add-in to produce this path, and have versions that simulate it with arcs, line segments, and a single spline curve.
My profile is drawn on a construction plane made 'along the path' and set at the start of the path.
I can produce a 'single path' sweep using any of the three path types, but the profile twists as it proceeds, which is unacceptable.
So, using the same add-in, I produced a second curve to use as a 'guide rail'. I've tried arranging the guide in a parallel fashion (identical to the path, but offset in the Z dimension)...
...or a radial fashion (corresponding points have the same Z value, but are radially offset from the center axis by a fixed amount).
The arc and line segment versions simply fail with this error:
Error: The path is not smooth.
Try modifying the path so that all edges are connected with tangent continuity. To create a swept shape with a sharp edge, try using multiple sweeps.
I don't think it's possible to represent my path with 'tangent continuity' using line segments and arcs. Why is this restriction made only when using the 'guide rail' type? The single-path sweep worked fine (except for the twist).
While you're considering that question, let's move on to the spline path version, which provides a bit more entertainment:
If I use the 'radial' guide rail, I see the following error:
Error: The sweep would create an illegal surface.
Try changing the profile or path.
...which leaves me rather nonplussed. What law has this hapless surface broken? Can anyone explain this error message more clearly?
Undaunted, I discovered, quite by accident, that altering the 'Distance' parameter to something less than one often eliminates the error, and occasionally even produces the correct result as far as it goes. I experimentally found that the maximum distance is about 0.8461 in this particular case. Examining my model visually, we can see that this appears to be exactly one turn before the end of the path; precisely below (looking down the Z axis) the endpoints of the path and guide rail. Curious.
If I use the 'parallel' guide rail I get the same error, but must reduce the distance much further to eliminate it: .344 works; .41 fails with error; values in between give twisted results. Experimenting with these intermediate values seems to suggest that the sweep is trying to align with the _earlier_ portion of the guide rail instead of marching along the guide rail apace with the path:
Theorizing that it might have to do with the distance from the path to the guide rail, I tried using a very small parallel offset for the guide rail, with no significant change.
Then I tried a very large parallel offset. The error was eliminated, but the shape is clearly not what I want:
Again, this might be explained by the sweep choosing an arbitrary point on the guide rail instead of proceeding along the guide rail at the same rate as the path.
Finally, I tried a radially offset guide rail a with a very small offset, and got the result I want.
During the sweep operation, Fusion is choosing an alignment point on the guide rail that doesn't always match my expectations. My successful version seems to suggest that by making the guide rail extremely close to the path, Fusion will be more likely to choose an alignment point that makes sense. Although then I would think that the small parallel offset should have worked just as well as the radial offset--or perhaps even better since the parallel-offset paths are precisely the same length. In my case, only the radially-offset guide rail worked.
Can you (Autodesk) give us some clearer insight into how the guide rail is used during the sweep process?
Otherwise, I fear I'm doomed to re-live this nightmare time and time again, forever cursing day I met Fusion 360.
-Matt