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.
Best Of
Re: View small part larger
@david_mach581
If you change the size of the planes by dragging their corners (as shown above) or just hide the planes, the part will stay larger when you use the auto-rotation funtions on the view cube. Those functions just zoom to fit everything in the view, so if you make the planes smaller, it can zoom in closer.
If you change the size of the planes by dragging their corners (as shown above) or just hide the planes, the part will stay larger when you use the auto-rotation funtions on the view cube. Those functions just zoom to fit everything in the view, so if you make the planes smaller, it can zoom in closer.
F2 for rename
Please make the F2 button invoke Rename ... this is so universal, and it's driving me nuts I have to rt-clk or remember Shift+n.
Re: Circular pattern features not moving with original
That is pretty strange. But weirdness like that is why I usually suggest using part patterns instead of feature patterns. They both have their place, but for geometry that does not vary with each instance, part and face patterns are preferred. They rebuild faster and are generally easier to deal with. But I did get your pattern to work (see below). Looks like your clip_holder_drum and clip_hole_1.2mm sketches were not fully constrained.
https://cad.onshape.com/documents/8428ea7cd2e14b2670d5421a/w/e5b17404983b485ca64f1002/e/02558eeb5239cba3fe743fd6
https://cad.onshape.com/documents/8428ea7cd2e14b2670d5421a/w/e5b17404983b485ca64f1002/e/02558eeb5239cba3fe743fd6
mahir
5
Re: coincident vs. pierce
You need them to be separate functions. There are times where both will actually constrain.
Pierce will actually touch the line/curve where it intersects the sketch plane.
Coincident will project the constrained point along the entire line/curve as if it were projected onto your sketch as a vertical line (in the example I have shown)
https://www.youtube.com/watch?v=YbN9Oilv1AU
Pierce will actually touch the line/curve where it intersects the sketch plane.
Coincident will project the constrained point along the entire line/curve as if it were projected onto your sketch as a vertical line (in the example I have shown)
https://www.youtube.com/watch?v=YbN9Oilv1AU
Re: Select items to insert
Correct.rune_thorsen229 said:I have to manually go back to the assembly and insert it manually.
Re: copy mate features possible?
No, you can't edit a suppressed feature/mate because you wouldn't be able to preview your edits.
I never noticed the copy option in the mates menu so had to try it out. Seems it is a reorder function - select mate(s) then copy, then right-click somewhere in mates list in the same assembly and "move copied mates here". I think it is a throwback from before we were able to drag and drop reorder mates. Should go really.
I never noticed the copy option in the mates menu so had to try it out. Seems it is a reorder function - select mate(s) then copy, then right-click somewhere in mates list in the same assembly and "move copied mates here". I think it is a throwback from before we were able to drag and drop reorder mates. Should go really.
Re: Select items to insert
I removed it until I had chance to check something.
It works fine if the sketch has a "face" (i.e. it is an enclosed shape and is shaded) or you are using a face off the in-context assembly as the sketch plane. Looks like a bug - thanks for finding it.
It works fine if the sketch has a "face" (i.e. it is an enclosed shape and is shaded) or you are using a face off the in-context assembly as the sketch plane. Looks like a bug - thanks for finding it.
Re: Best modelling workflow for multi-part
Everything that is static (ie. no motion, they can be parametric) can be easily modeled into single part studio. Parts with motion I tend to have as subassembly so I can set limits etc. only once and just insert to any assy. When inserting whole part studio into assembly all static parts can be mated with one group mate which is a real time saver comparing to 3 mates per part system (Alibre).
3dcad
7
Re: Learning CAD for 3D Printing
Reading this thread, one would think there is a preferred knowledge for parametric modeling.
Parametric modeling is still in it's infancy so please understand that you'll get different answers from different experts.
So why bother with something not defined and difficult? Because there is no better way to control 3D geometry on a computer.
Basic Parametrics:
-it remembers everything you pick, so pick your references wisely
-your 1st feature is always the hardest feature to create
-keep sketches simple, more features fewer sketch entities
-declare your intentions, create features for the next guy that'll inherit your model
-parametric modeling is all about the references, learn about references
-for large assemblies, you have to have a plan, structure, drawing tree something to organize the project
You can always build a better model especially when you just finish a project. This is part of the learning process.
User's Parametric Progression:
1st year-Yeah I can spin it around and it looks right
2nd year-I can build it this way, or this way, or this way, this way is more robust
An expert-creates a robust model that other designers can follow and understand
Do you know CAD geometry?
-point
-line
-arc
-conic
-spline
-surface
-trimmed surface
Do you know about manifolds?
-vertices
-edges
-faces
Should an edge always have 2 face references?
I've always felt people have wanted to skip to the shade & spin and ignore the basic stuff. Yet, it's the basic stuff that gets me out of trouble and is the reason I get paid the big bucks when I'm asked to solve someone else's problems. How much do you want to learn about this?
Parametric modeling is still in it's infancy so please understand that you'll get different answers from different experts.
So why bother with something not defined and difficult? Because there is no better way to control 3D geometry on a computer.
Basic Parametrics:
-it remembers everything you pick, so pick your references wisely
-your 1st feature is always the hardest feature to create
-keep sketches simple, more features fewer sketch entities
-declare your intentions, create features for the next guy that'll inherit your model
-parametric modeling is all about the references, learn about references
-for large assemblies, you have to have a plan, structure, drawing tree something to organize the project
You can always build a better model especially when you just finish a project. This is part of the learning process.
User's Parametric Progression:
1st year-Yeah I can spin it around and it looks right
2nd year-I can build it this way, or this way, or this way, this way is more robust
An expert-creates a robust model that other designers can follow and understand
Do you know CAD geometry?
-point
-line
-arc
-conic
-spline
-surface
-trimmed surface
Do you know about manifolds?
-vertices
-edges
-faces
Should an edge always have 2 face references?
I've always felt people have wanted to skip to the shade & spin and ignore the basic stuff. Yet, it's the basic stuff that gets me out of trouble and is the reason I get paid the big bucks when I'm asked to solve someone else's problems. How much do you want to learn about this?
billy2
6
Re: Automation for assemblies
Hi @brooke_spreen
Check out our developer portal:
https://dev-portal.onshape.com/
There it lists the links for the documentation, some sample programs, and an email that you can reach out to with questions.
Check out our developer portal:
https://dev-portal.onshape.com/
There it lists the links for the documentation, some sample programs, and an email that you can reach out to with questions.