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.
When should a pattern use features instead of faces?
hank_debey
Member Posts: 31 ✭✭
Reference the tutorial at this link, https://learn.onshape.com/learn/course/fundamentals-part-design-using-part-studios/creating-patterns-and-mirrors-in-a-part-studio/mirror?page=1
There is a statement at 1:05 that says "There will be situations where a face or feature mirror will be preferred over the other."
Other tutorials suggest face are more performant than features. Does anyone know what types of situations will favor features over faces?
0
Best Answers
-
NeilCooke Moderator, Onshape Employees Posts: 5,723Face patterns are faster. Feature patterns will, if they can, select all the faces that belong to the feature and use a face pattern in the background. If this doesn't work, select "Apply per instance" to do a feature-by-feature pattern instance calculation (slower). Also consider using Part patterns if possible.Senior Director, Technical Services, EMEA0
-
EvanReese Member, Mentor Posts: 2,190 ✭✭✭✭✭Neil is right. The upshot of it for me is a preference hierarchy like this:
Part pattern > Feature pattern ("Apply per instance" NOT checked) > Face pattern > Feature pattern ("Apply per instance" checked).
Evan Reese0
Answers
Part pattern > Feature pattern ("Apply per instance" NOT checked) > Face pattern > Feature pattern ("Apply per instance" checked).