Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Allow an override to the Sweep intersects itself error.
t_cary
Member Posts: 9 ✭✭
When sweeping a spline that curves in and out there are times when creating a solid it is irrelevant that the same volume of space is redundantly defined.
I'm trying to sweep a coping around an irregular shaped pool. When I sweep the perimeter every place it turns outwards causes the sweep to intersect itself. I want to disregard this. I can work around it and make multiple paths and then do the boolean, but... a check box to allow it... or why not simply allow it and give a warning?
I'm trying to sweep a coping around an irregular shaped pool. When I sweep the perimeter every place it turns outwards causes the sweep to intersect itself. I want to disregard this. I can work around it and make multiple paths and then do the boolean, but... a check box to allow it... or why not simply allow it and give a warning?
Tagged:
1
Comments
One common case I find quite a bit is trying to model a routed cut along a curved edge that has some radii/details that are smaller than the routed shape. I think it's a reasonable thing to _want_ to do, because it's pretty trivial to describe and manufacture.
Here on the right is a chamfer that's easy for onshape to handle. On the left the chamfer is at the edge of what is currently valid. I _often_ find myself wanting to go further than this. It seems easy to imagine a part that has been chamfered with a larger distance, and while there may be obvious mathematical/modelling reasons that this is difficult, as a user it _seems_ arbitrary that onshape rejects it.