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.
Copying Parts Between Part Studios
Nate
Member Posts: 1 ✭
Answers
Copying just a part from one part studio to the other isn't possible yet.
Example: I have parts in doc 1 of which I have copied a tab to doc 2, I change the tab in doc 1 then copy the tab to doc 2 but I can not get it to replace the original tab with the updated tab.
Twitter: @onshapetricks & @babart1977
Twitter: @onshapetricks & @babart1977
- import all of your part files
- create an assembly using the least amount of mates. this is a temporary assembly.
- right click on your assembly, and translate it to a parasolid.
- translate your parasolid assembly to a flattened part studio.
At this point you should have a part studio with all required parts to "Use" your geometry any way you need. Hope this helps people as much as it helped me.Also you can not do a full part studio as a derived feature only parts, sketches and planes.
Twitter: @onshapetricks & @babart1977
Twitter: @onshapetricks & @babart1977
Twitter: @onshapetricks & @babart1977
Twitter: @onshapetricks & @babart1977
You could try using "Derive" to get a linked copy of your part from the 'new Part Studio' (in your post) to the one you're working in.
If you want to edit the derived part, you will have to do that to the master (in the 'new Part Studio')
I use it in the limited and specific sense that Onshape use it.
If my hunch is correct, you may find you actually can
"edit the (derived) part together with the others (some boolean operations etc...)"
I'm also importing geometry into Onshape using your technique. I have found that having one huge part studio isn't ideal and have been exporting bits and pieces into manageable partstudios. I'm using derived methods to re-assemble these bits into a larger partstudio. Now that we can position partstudios inside other partstudios, this approach kinda works. Forget about assemblies.
Other than the derived bugs well documented here in the forum, it seems to be a promising structure for larger projects.
I wish I could hide an inserted partstudio inside another partstudio. To me it's all about making things go away and bringing them back. I'm interested in working on 1000 component partstudios and setting up a structure that allows this operation. You can't pick the top level when importing a derived partstudio. The display tries to update when picking each derived component which is way too painful and slow. There are a lot things that are wrong with this approach, but if you can endure, what you end up with is nice. Maybe you could call it an engineering layout. Like Pete said, I'll I want to do is create a layout. I'm pushing it further than importing McMaster Carr parts, I'm building the entire structure this way. So far it's not bad.
Back to your huge partstudio. I Wish there was a way to divide a huge partstudio into manageable chunks. It would be nice to bring in a huge project into one large partstudio and break it up into manageable chunks inside OS. Having to break it down inside the sending system seems wrong, some one say unjustifiable. I think you'll end up with a better OS data structure if you try and break up your export and manage the import into OS.
I've also submitted an ticket to remove the import option that doesn't flatten the assembly. When you uncheck this option, the components in the partstudios are stacked about the origin and renders the partstudio useless. This shouldn't be possible, ever. Why does it exist?