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: Custom Feature: Triad Transform
@james_cooney812 done. V6 supports mate connector transforming
Re: Mesh imports but doesn't show up in parts studio
It's right there in front of you…Actually its super tiny…LOL Just update the units of the import and it'll rescale appropriately.
MDesign
Re: Best performance method to make or use parts with hundreds of grid holes
Face pattern will probably be the fastest if you need all the holes.
S1mon
Re: Lofting between circle extrude and square extrude.
Found an old one and bumped it. 10 year anniversary on the request it looks like, but I see people ask about this kind of thing all the time both on the forums and the discord so it's weird there isn't more traffic for this request.
Re: Why wont this Boolean?
There's the careful approach and the aggressive approach, and I almost always default to the aggressive approach. In the past I would have conceptualized chunks of related geometry to carve out of the part studio and then duplicated the tab into that many chunks, then in each of the new studios start deleting features irrelevant to any of the smaller geometric assemblies to try to focus in on whatever matters to just that subset of geometry. In practice the issue with this approach is the modeling architecture is usually not clean to commit surgery on and you end up with less than ideal build time and waste a lot of potential progress hours fighting with features that break when you chop their legs out from under them, so the faster approach is to pull up a second monitor and draw the chunks from scratch and perform a full refactor with good architecture. It always sounds like the longer way around and it never ends up being that way because a clean document is so much faster to work on and you've already got a good reference for the target final product so it doesn't take as much time as you'd expect. Even starting "from zero"
Re: Classify Onshape Standard Content in FS?
I'm not sure I understand the ask here. Are you trying to make sure that you use Onshape Standard Content where available, and only use imports if not? Onshape Standard Content only exists in assemblies, where featurescript can't get at them.
