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.
"Group" while in Parts Studio?
christopher_owens
Member Posts: 235 ✭✭
Hello! I have a Pattern of a part (35 instances) in Part Studio that I wanted to make a Group. I read that I have to put all the copies in an Assembly and then create the Group? Seems it would be more efficient to have the option to create the Group where the Pattern was created.
ps There is no 'Group' in "Tags"
ps There is no 'Group' in "Tags"
Tagged:
0
Answers
In an assembly, doing a shift + select should select everything between it in the assembly tree. If possible, can you share the document?
The other thing that you can try, is with the group dialog open, cross-select all of your parts. If you click+drag from right to left, anything that touches that window will be selected.
The way Onshape workflow is, you can model up all your parts in one Parts Studio. I think it is the Pattern (Linear or Circular) of parts in a Parts Studio that the Group option may be needed. I see I can't make a Pattern in an Assembly, say for "Bolts-Washers-Nut" in a bolt circle? I can see where you could Group the components... now would that Group have its own Mate Connector?? So I could place the "Bolt-Washers-Nut" quickly on every hole in the bolt circle?
If you agree, please vote https://forum.onshape.com/discussion/6490/create-assembly-of-part-studio-using-rmb-menu-in-tab-explorer
@christopher_owens
You can also box select everything and then group (box select is faster in assy than in ps since it only searches for parts).
To copy assembly, select all lines in 'feature tree' - copy - begin new assy - paste (this could also have it's own feature, but let's first wait for assembly configurations)
We at Onshape believe that design multiple parts with one parametric history (aka in a Part Studio) is a major and unique benefit that greatly reduces the work required to design and edit parts with interrelated shapes.
But it can be easy also use part studios to construct full "assemblies", but this can have serious drawbacks if it is used to design multiple parts that are not very interrelated, or to "insert" and position read-only components (like fasteners). You can end up with one parametric history with many features doing many unrelated things - and this makes editing each of those unrelated things regenerate slower and less independently (and thus less can be harder to change one thing without changing another). What is powerful in one situation can be hard to manage in another.
Assemblies are optimized for a) reusing parts defined in part studios, defining the structure (hierarchy and sub-assemblies) and reusing them, and for defining physical behavior like movement, etc. Because assemblies do not have a parametric history, the bigger they get, the better the relative performance and common operations such as delete instance, add instance, reposition instance, replace instance, create a subassembly in place, reuse parts and subassemblies, etc., are natural and fast. All of these things are important to defining products, even if they have no or few moving parts.
If you find yourself doing a lot of insert parts features and transform features, or patterns where the results are meant to be instances of the same part, or with parts defined in one studio that are not meaningfully driven by shared sketches or edited by shared features, or with very long feature lists, then you may want to consider using more part studios to define your parts.
Parts Studios can be a good way to design "top-down" and so can in-context modeling in an assembly context. Both have strengths. In-context scales well to nay size assembly and is often the only choice if the assembly is already built.
There is no simple one size fits all answer to when it is better to design multiple parts in one part studio vs multiple. Onshape provides powerful tools, and usually when that is the case, different approaches can be used to solve the same problem. The user is in the best position to decide what is optimal for his specific design situation. Our customer success team, our support team, and users on this forum are good sources for advice and best practices if needed.