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 selecting patterned part as merge scope in intersection
alnis
Member, Developers Posts: 452 EDU
Currently, when using a pattern such as a linear pattern or circular pattern, it is possible to have the pattern add to the part being patterned. It would be useful in some cases to have this work with the "Intersect" option, too, since its behavior is not consistent with the "Add" option at the moment. Here's a simple example (link to document:https://cad.onshape.com/documents/0433b25fe5828cf767f0e8a6/w/33bb48c463a06e5a017cc7da/e/bec19ea901e71bc449c7a58c):
Using the "Add" type with the part selected as the merge scope, everything works as expected:
However, using the "Intersect" type with Part 1 selected as the merge scope, the feature fails and does not work how you would expect coming from the "Add" option:
Here is the expected result for the second input if the "Intersect" option were to behave the same as the "Add" option (the circular pattern produces new parts, and the boolean intersects them):
I know this has somewhat limited use cases, but it simplifies modeling geometric/mathematical shapes a bit, and I can also see how it would be useful for mechanical products. My guess is that it wouldn't be too difficult to implement since the "New" option plus an "Intersect" boolean already provides the desired outcome. This would help to increase the consistency and simplicity of the default Onshape feature set so that the sub-options work in the same way. Maybe it would be a good, small "first fix/improvement" for a new employee on the team?
Thank you for your consideration!
Using the "Add" type with the part selected as the merge scope, everything works as expected:
However, using the "Intersect" type with Part 1 selected as the merge scope, the feature fails and does not work how you would expect coming from the "Add" option:
Here is the expected result for the second input if the "Intersect" option were to behave the same as the "Add" option (the circular pattern produces new parts, and the boolean intersects them):
I know this has somewhat limited use cases, but it simplifies modeling geometric/mathematical shapes a bit, and I can also see how it would be useful for mechanical products. My guess is that it wouldn't be too difficult to implement since the "New" option plus an "Intersect" boolean already provides the desired outcome. This would help to increase the consistency and simplicity of the default Onshape feature set so that the sub-options work in the same way. Maybe it would be a good, small "first fix/improvement" for a new employee on the team?
Thank you for your consideration!
Get in touch: contact@alnis.dev | My personal site: https://alnis.dev
@alnis is my personal account. @alnis_ptc is my official PTC account.
@alnis is my personal account. @alnis_ptc is my official PTC account.
2
Comments
@alnis is my personal account. @alnis_ptc is my official PTC account.
Sorry about confusion.
@alnis is my personal account. @alnis_ptc is my official PTC account.