Couldn't find by searching, so I hope a new topic is OK. I suspect this has a short answer.
We don't use the content center, so All our rivets etc. are in a linked library. I have an assy with 100 rivets.
Is the best practice to use the rigid joint now? Have previously used insert constrain. the difference is that the rivet doesn't rotate with joint.
with constrain, it rotates, but cannot be seen, unless I use a textured appearance.
Are there advantages to loading and processing the model with rigid, as it doesn't rotate?
The odds for this model to ever enter dynamic simulation is low.
Are you using imates
imates still wont support joints
rigid joints are much easier
As you reduce degrees of freedom the model seems to respond faster, at least to me.
You can understand joints as next step in constraints evolution. Lets say joints are "smarter" constraints. Each joint is constraining two origins where each origin represents a coordinate system defined by pick point, Gap direction(Z axis) and Alignment selection(X axis). Y axis can be easily calculated by right hand rule from Z and X. Joint provides more precise control over positioning of constrained instances.
For your case, Insert constraint can be replaced by Rotational joint which allows rotation around Z axis like an Insert. Rotational joint additonally provides control over rotation angle which can be measured or limited based on Alignment direction. You can specify angular data on Limits tab of Joint dialog box.
Access a broad range of knowledge to help get the most out of your products and services.