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.
Mate connector not showing up in assembly?
I have a weird problem, and I can't tell if it's a bug, or user error. I had a part with a mate connector as the third feature. It shows up just fine in the part, but in the assembly, it doesn't show. The owner part of the MC is the part that I'm inserting. I just tried moving the MC feature to the end of the tree, and now it shows up in the assembly as expected.
The part goes through some split and boolean add features along the way. Is this MC behavior because of the part IDs? Is this expected behavior?
[I can't share the document publicly]
The part goes through some split and boolean add features along the way. Is this MC behavior because of the part IDs? Is this expected behavior?
[I can't share the document publicly]
Tagged:
0
Best Answers
-
NeilCooke Moderator, Onshape Employees Posts: 5,714There is a determinism issue with part IDs when there are lots of splits and booleans. We are investigating how to make it more robust, but for now it is what it is.Senior Director, Technical Services, EMEAI2
-
eric_pesty Member Posts: 1,947 PROmartin_kopplow said:Saw the same occasionally, thought I was stupid, but at least I'm not alone. This is highly annoying in complex assemblies and very unlogical (even if it could be explained by entity IDs changing after certain operations, but hey, if it can be easily explaned, it could as well be caught!) If a mate connector is linked to a feature (like in above example), the correct owner part could be calculated or forwared even after a split operation or the like has been made.1
Answers
Perhaps having split create two parts with the same name is confusing for the user (i.e. me), since it's not clear which one has actually kept the internal ID from prior to the split. If I had a clear indication which one had inherited the ID, I could be more careful about downstream features.
In this example I am not sure why you would need to define an explicit mate connector at the center of the hex when there is an implicit MC right there always available...
This toally solved the problem for me. As soon as I changed the owner in the mate connector feature to the part, it showed up in the assembly.
THANKS!!!