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: Need help with copying scanned shape
Evan's surfacing tools are what you will need.
As far as the right direction:
- Start by completing the Learning Pathways. This is essential for having a good understanding of Onshape before you do advanced surfacing.
- Once you complete the learning pathways, then move on to Evan's features and videos:
- Surfacing Deep Dive
- Here is a list of Evan's Surface Mesh Features
.
Re: New Feature: Tween Curve (WIP)
There was a similar request for multiple tween curves, which ended up being a really simple implementation since Derek did all the hard work: Multi-Tween. On the other hand, peaking under the hood of this🤯, I'm not touching any of that.
ry_gb
Re: Feature Script 2025
@Caden_Armstrong to think I hadn't even put out Tween Surfaces at the time of this comment. We're playing in a whole other dimension now.
Query Variables and QV+ have completely changed the way I approach development because it's much easier to build concepts of a script in a bunch of part studios before ever writing a single line of code. Somewhere in my pile of demo studios there's a version of Tweep that started as me mashing together existing scripts and basic features with queries passed between them to see if the theory of the feature would work.
Re: Feature Script 2025
I will say that I started using the official improvement requests page as my own personal featurescript bounty board recently for kicks. But in defense of the developers over at headquarters, a lot of the features I've been cooking from that list have landed in the camp of easy-to-describe but nontrivial to execute. And I get to benefit from being able to produce a broken tweep feature and debugging live with forum feedback instead of the normal software development requirements of not pushing busted products to main.
I'll shout out @Caden_Armstrong for a feature he actually didn't release publicly. His panelization script he posted to LinkedIn pushed me into working more with manipulators and editing logic and led to the direct development of Better Than Boolean.
Re: Feature Script 2025
You know, I'm not 100% sure if other systems can do exactly what you've done with loft fillet. Some quick ChatGPT research says NX, Catia, Alias and ICEM do - but take that with a grain of salt. I thought I had seen feature in other tools that could handle some sort of tubular offset/width constraint and then do a blend of some sort regardless of the dihedral. I almost thought that Onshape's own face blend tool could handle the dihedral going to zero or going from concave to convex, but it can't.
S1mon
Re: New Feature: Tween Curve (WIP)
Here's some early access to the Twurface sandbox. (I probably will not call it that) Lots of demo cases that don't work at the moment because B spline surfaces are a beast of calculus and I'm a college dropout who failed math 3 times, but also lots of demo cases that DO work and that's promising.
Re: Feature Script 2025
If only liveworx was still a thing.
I really wish the featurescript environment was closer to github where public features could be maintained like open source software. I'd love to be able to put in a pull request to someones feature. Make community contributions instead of having to fracture features off (or give people permissions to my documents).
Re: Texture (New Custom Feature!)
Ok, I was just saying I've seen that behavior elsewhere. I was wondering if they were related.
Re: About configurted parts
I think you might be misunderstanding the function of configurations and versions. The most common use case of configurations is to make a configured part, like you have, and then just choose what configuration you want when you insert the part into an assembly. I can't think of a reason to make dozens of copies of the part in separate part studios. Please check out the following courses in the Learning Center.
https://learn.onshape.com/courses/introduction-to-part-configurations
https://learn.onshape.com/courses/fundamentals-document-history-and-versions
Re: Does dynamic suppression support conditional logic
Got it, thanks. That clears things up. Using variables to share the logic across folders actually sounds pretty manageable. I was mostly wondering about assemblies, so I guess we'll see where Onshape takes that. We've hit similar consistency challenges working with distributed design teams through CrewBloom, so this approach definitely helps. Appreciate the response!
