Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:

  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. 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 connectors created with opMateConnector are missing from rigid Part Studio inserts

ben_gibbs
ben_gibbs Member Posts: 2 ✭

Heads-up for anyone writing custom features that create mate connectors, and a question for anyone who's seen this.

A mate connector created in a custom feature with opMateConnector (owner set to a solid part) doesn't survive "Insert entire Part Studio as rigid". In the assembly the connector is still drawn and you can hover it, but it's missing from the instance's mate connector dropdown in the Instances list, and any mate to it fails with "Missing mate connector of ...". A native Mate Connector on the same part works fine.

With a standard (non-rigid) insert, or inserting the part on its own, both connectors are listed and both mate correctly.

What I've ruled out:

  • Same result whether the owner part was made by the custom feature or by a native Extrude.
  • Dissolving the rigid instance doesn't bring the connector back.
  • With standard inserts it worked in every case I tried: owner drilled or moved by the feature, owner changed by a later feature, connector placed off the owner, owner inside a composite.

Minimal public repro (one block, one opMateConnector, one native control connector, and an assembly with both a rigid and a standard insert side by side):

https://cad.onshape.com/documents/73dbda62ce1c16abcd115800/w/554c5d9254aa0835ddc5115d/e/388bd649c124d03c0ebba8b4?renderMode=0&uiState=6ae9e3e757ce4c7c11f891c2

I have reported this to support.

My workaround for now: the feature emits an ownerless mate connector as a snap target, and I add native Mate Connectors snapped to it by hand. It works, but it defeats much of the point of the feature, and I rely on rigid inserts for everything.

Has anyone else run into this? If you have custom features that emit mate connectors and you use rigid inserts, I'd be interested to hear whether you see the same thing.

Comments

  • NeilCooke
    NeilCooke Moderator, Onshape Employees Posts: 6,126 image

    It's a known problem, but thanks for highlighting it.

    Senior Director, Technical Services, EMEA