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.
Options
Closed shape does not produce face when offset is used
wito_roz137
Member Posts: 5 ✭✭
in General
https://cad.onshape.com/documents/5a79cd2f70dfdd34ab1bafcb/w/cf901ba41e8906d7a8939ce4/e/356c3b1f961f73023b6a6ab9
in sketch 3 if I use an offset of 8mm closed shape is turned into a selectable face, but if the offset is 7mm it does not. It also works for various other offset values but not for 7mm. Is this a bug or am I missing something?
in sketch 3 if I use an offset of 8mm closed shape is turned into a selectable face, but if the offset is 7mm it does not. It also works for various other offset values but not for 7mm. Is this a bug or am I missing something?
0
Comments
I extended both the vertical line and the offset curve and let the system find the intersection. No matter how I tried aligning the endpoints to the other curve or endpoint, it would break. This arrangement is robust through a range of values for the "7" dimension. It shouldn't really be necessary, but offset curves are fussy.
https://cad.onshape.com/documents/f7119b87f6cc00fd5093cbde/w/9237c2d125ae189ef5850296/e/186d3dbdf173cc4a950560bd
Things like this when you do everything correctly and follow a workflow that should work but doesn't are really annoying in Onshape. If there is a coincident constraint applied to 2 vertices they should be connected! We shouldn't need to find workarounds...
This issue of coincident constraint not closing the loop never happened to me before today, but today it happened twice in two different cases. Maybe this bug appeared recently? Maybe it was introduced in one of the updates?