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: Cutting a section of an assembly to send to supplier
I'm curious too. I would usually just share the part model, and there'd be a section view option should he need one, or a tab with a section drawing.
Re: New Feature: Tween Curve (WIP)
See I feel like you're always the fastest gun in the west 🤠🌵
@Derek_Van_Allen_BD Can you just do your best and add a flip button for those cases? You may not really be able to cover them all. Maybe not though since you're using these functions as a backbone of other features.
As an aside, I could imagine cases for another mode to create a certain number of tween curves. Instead of a "tween fraction" the input is "steps".
Re: How can I merge two faces to become rounded? (more details in description).
Yes, thanks! A kind person on Reddit gave me a hand.
Re: Optics: Custom Feature
The roughness implementation could be better (see discussion of lambertian distributions above), but right now the maximum angle of a certain roughness value is kind of like a % of 180°.
roughness of 1 randomizes the ray direction up to ± 90° (180° total) like this
0.5 is up to to ± 45° (90° total)
and so on…
If you wanted to control it with an angular input, you could use the expression #roughness = (180 * deg) / #viewingAngle
Re: taper helix
- I appreciate the follow up and it was much simpler than I thought. Sorry for sounding frustrated!
Re: New Feature: Tween Curve (WIP)
Be warned: it's a little buggy. I'm currently reworking the orientation checks between input curves to handle orientation flipping between paths. Sometimes I'll still come across a zero-crossing case with one curve to another and haven't found a universally robust way to find path direction.
New Feature: Tween Curve (WIP)
This is a bit of work in progress at the moment but it's semi functional and I need to work on other tools that this tool is the backbone of. Posting now for public comment. Introducing Tween Curve
Simply select input curve A and input curve B and input a tween value between 0 and 1 and this tool outputs an approximate medial curve AB that is that percentage morphed between the two inputs.
Currently it's limited to single edges for each of the inputs because I'm still working out how to make piecewise segments work for continuous path geometry. This tool by itself is already useful for some workflows but the larger goal is to use this feature as a starting point for other features I've got planned like a frame unrolling script that can unfold frame geometry with a k factor specified by the tween, or other shape deformation scripts that I've got in the works.
Re: Fillet or Face Blend on Icosahedron
@l_m724 This is a challenging shape.
Fillet can struggle with intersections of a lot of edges. I was able to get it to fillet, though I'm not 100% happy with some of the artifacts (like the wavy surface break where the spout meets the body). To get this where I'd like it I think I'd end up doing a lot with surfacing tools and it would be a pretty different approach. Here's this one anyway. I was able to shorten the feature tree considerably. A few other notable things I did:
- For starters there's a Polyhedron custom feature already, which will save you making the icosahedron yourself. ( @_anton your WIP looks awesome too!)
- I used my custom feature Selection Fillet to batch some of the selections, but for that reason, I wanted to fillet before the Shell feature, but also not bother shelling with the fillets, so I made my own "shell core" using another method, which I later subtracted. You could also just use the native Fillet feature.
- Keeping some bodies separate to fillet first and boolean them together later can be a helpful strategy sometimes.
- I used a variable called #radius so that I only need to change it one place if I want to update the fillet radius. In your model, you had 40 fillet features, so this would be even more valuable if you're doing it that way.
Feel free to ask questions.
