On the other hand, depending on how your screws and rings are designed, it can be easy or difficult to exclude.
And moreover for everything that moves, it will detect a collision only in the position when you launch the function.
So unless you run the function in all possible and imaginable positions, it doesn't work.
Having tested it, I find that we detect much more false interference (like H7 bore, or screws...) and than real interference. And that the real interference when you move something and in a well-defined position a piece collides, in general you miss it.
Unless I missed something, I'm not a fan of this interference detection.
There is a function that prohibits the interpenetration of parts when moving but: - I don't remember where it's hidden (but it must be in the same tab as the interference detection); - you must not go too fast during the movement otherwise the software will not follow; - Corrollary/cause of the previous one: you need machine resources...
I'm surprised that the H7 type rings cause interference, do you model them to the real size?
For the screws (and other parts to exclude), you can, I think, play with the "IsFastener" property.
@Stefbeno I'm going to take a close look at "IsFastener" (because I totally missed this feature) because if I eliminate all the screws, bolts and washers, it will already clear the landscape. Indeed I don't even know how he knows that it's screws and bolts because these are parts downloaded from suppliers that I rename so that it fits into a logic of codif to us. Agree with you on the fact that you have to go slowly for moving collisions I know that ;-) I have a velvet glove for that ;-) Yes, I model at full size because I set the tolerances from the creation which makes the MEP faster.
@Sbadenis agree with you that it's a hassle but I have no other solution if I want to make zero defects the first time. In general, I set myself the goal of having only one or two minor errors on complex assemblies and always articulated in all directions, this is the advantage of modern software like SW which allows you a lot of control before machining any part.
@Ac cobra yes it's the interference tool I use but there's something wrong. But with "IsFastener" it should improve things. Since this is a feature I don't use often, I have to do something incorrectly.
Good! thank you I will keep you informed of the rest ;-)
YOU say ((( There is a function that prohibits the interpenetration of parts when moving but: - I don't remember where it's hidden (but it must be in the same tab as the interference detection); )))
In fact, they must be a little weird in their reasoning at SW! They put this in "Problem detection" and then in collision detection but you have to use the
Move the component or Rotate Component
In addition, it is not possible to use IsFeature, which neutralizes collisions due to screws and tight bores. As a result, it always starts with a message that stops everything since it considers that there is already a collision at the start. However, it removes the "stop on collision" choice by authority, so it also removes the sound. But fortunately , it continues to highlight the dynamically colliding part. On collision (the part changes color).
Good ! I admit that as I only use it in the final phase I couldn't remember where it was ;-) Thank you!