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.
Parts library that provides for each part a simplified and full model version
maftei_albert_alexandru
Member Posts: 4 EDU
I'm trying to make a parts library that provides for each part a simplified and full model version(configured via a configuration checkbox), since these parts get used in assemblies with up to 2000 parts and subassemblies so the primitive count is really high and some computers struggle. However I've encountered the problem of ensuring consistency between the two models, since for example in an assembly, when switching between the models, the mates get suppressed.
Is there any way to mantain consistentcy when switching the models(without providing explicit mate connectors the user has to use), any featurescript hack or something?
Best Answers
-
jelte_steur814
Member Posts: 428 PRO
why without the explicit mate connectors? that's definitely the best way.
otherwise the 'simplification' has to be done in such a way that it will not affect faces that may be used for mates in an assembly. but that may be difficult or impossible and is definitely hard to predict.
2 -
eric_pesty
Member Posts: 2,125 PRO
The explicit mate connector is the best option for sure… But if you have "undisciplined" users, you might be able to use the "assign identity" FS to provide a matching face ID between the two configs (at least my understanding is that it should be able to do this…)
https://cad.onshape.com/documents/fcf31e8bc171b06037008400/v/7e1b5b2304e2bd6d9223a41a/e/e076332e1669ea9babcaf65b1 -
scarlet_john
Member Posts: 4 ✭
You're hitting a classic tradeoff—performance vs. parametric consistency. Sadly, without explicit mate connectors, Featurescript doesn't offer a built-in way to auto-sync mates between simplified and full configs. One workaround is embedding consistent reference geometry (like named sketch points or planes) in both versions, hidden from users but stable for mates. It’s not as clean as auto-mapping, but it avoids user-facing connectors and keeps mates alive across configs. Bit of a hack, but it works.
0
Answers
why without the explicit mate connectors? that's definitely the best way.
otherwise the 'simplification' has to be done in such a way that it will not affect faces that may be used for mates in an assembly. but that may be difficult or impossible and is definitely hard to predict.
The explicit mate connector is the best option for sure… But if you have "undisciplined" users, you might be able to use the "assign identity" FS to provide a matching face ID between the two configs (at least my understanding is that it should be able to do this…)
https://cad.onshape.com/documents/fcf31e8bc171b06037008400/v/7e1b5b2304e2bd6d9223a41a/e/e076332e1669ea9babcaf65b
You're hitting a classic tradeoff—performance vs. parametric consistency. Sadly, without explicit mate connectors, Featurescript doesn't offer a built-in way to auto-sync mates between simplified and full configs. One workaround is embedding consistent reference geometry (like named sketch points or planes) in both versions, hidden from users but stable for mates. It’s not as clean as auto-mapping, but it avoids user-facing connectors and keeps mates alive across configs. Bit of a hack, but it works.
I agree that the current methods to achieve such simplifcation is extremely flawed, perhaps a feature request to add a feature that enables models to either have a non simplified topology or a feature to simplify a model unless you're adding mates to it is in order.