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: Tweep
I know many of us were a little bit saddened to see Tweep retired when the devs brought the twist option to the native Sweep feature, but I never really let this one go in my heart.
Big update soon.
Re: Company wide labels
Actually documents should be autoshared among company if company is the owner.
3dcad
Re: is there a way to highlight what isn't contained in a sketch?
There should be a 'check geometry' tool to find unconstrained sketch entities AND also open gaps between curves. Would save very much time and nerves with imported geometry.
It's time to update how FeatureScript can control properties
With public MCP access we're about to hit a big wave of custom feature development. One of the most common limitations I hit is in using part properties to do things. I think the Support Team is about to have to field a ton of tickets on this, because the issue is non-obvious, and the thing people want to do (but can't) is reasonable. There are two main issues I see right now:
- If a user sets a property manually, we have to Reset All in order for a feature to set that property. A lightweight solution would be to allow us to reset only 1 property, without clearing them all. Even that could be better though. There's no notification that a feature-set property is being overwritten by a user-set one. It just doesn't work and people have to come to the forums or ask the AI advisor to figure it out. We need better discoverability here, and an easier way to get the Feature back in control.
- It would often be incredibly helpful to have a feature access and actually USE properties during feature regeneration. We could still solve most of the issue for me if these were only used to set other properties. For example, to name the part partNumber~partDescription or simply to write part numbers to a Cutlist Table. I understand that giving carte blanche on property access at runtime opens a pandora's box of edge cases, but I wonder if there is a limited solution that addresses a lot of the reasonable wants without doing that. For example, it would be nice to have a way to use Computed Properties for anything, like the Part Name. However, we'd only want it some of the time. A way to automatically toggle from user-set to computed, then set the computed property would go a long way.
Anyway, I'm sure a better solution than any of my ideas can be found. Devs, if this is on your mind already, let's have a call and I can share some of my experiences.
