Thank you for the video! It's easy to understand. I wonder if we can select multiple bodies in a single interface? So far I can only create interface for single body
You can achieve this by making a group that contains multiple bodies. You can then change your selection filter to Groups on Bodies in the product interface.
Isn't it the same , if in part 2 tree we directly use a interpart wave linking & linking the previous body ? [ no need to define product interface in part 1 ]
Do you mean by turning on Wave Mode? To some extent, yes, however, with Product Interface you can lock down the links people can use. I have seen so many parts made from WAVE links that are unnecessary. Using PI helps you with this. There are also some other benefits, such as enforcing mates with the interface, etc. Perhaps I will do another video showcasing these options.
Product interface only does one thing: it records geometry. Therefore, an assembly is not required for linking. WAVE Geometry linker does two: it records geometry (like the Product Interface) and it records assembly position. Therefore, WAVE geometry linker not only needs the geometry, but an assembly as well. In my experience, it is also easier to fix broken links that are Interfaced than just normal Wave Geometry Linking. It keeps things very organized.
@@Jive_Engineering Aren't you confusing context dependent vs context independent linking here? With the advanced assembly license (Mach 3), you don't need an assembly for geometry links either, if you make them context independent.
Thank you for the video! It's easy to understand. I wonder if we can select multiple bodies in a single interface? So far I can only create interface for single body
You can achieve this by making a group that contains multiple bodies. You can then change your selection filter to Groups on Bodies in the product interface.
Isn't it the same , if in part 2 tree we directly use a interpart wave linking & linking the previous body ? [ no need to define product interface in part 1 ]
Do you mean by turning on Wave Mode? To some extent, yes, however, with Product Interface you can lock down the links people can use. I have seen so many parts made from WAVE links that are unnecessary. Using PI helps you with this. There are also some other benefits, such as enforcing mates with the interface, etc. Perhaps I will do another video showcasing these options.
What's the difference between Product Interfaces and simply WAVE linking though?
Product interface only does one thing: it records geometry. Therefore, an assembly is not required for linking. WAVE Geometry linker does two: it records geometry (like the Product Interface) and it records assembly position. Therefore, WAVE geometry linker not only needs the geometry, but an assembly as well. In my experience, it is also easier to fix broken links that are Interfaced than just normal Wave Geometry Linking. It keeps things very organized.
@@Jive_Engineering Aren't you confusing context dependent vs context independent linking here? With the advanced assembly license (Mach 3), you don't need an assembly for geometry links either, if you make them context independent.