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: What is the best way to find what dimensions rely on a specific variable?
Say this variable #length is from a variable studio. If I use this variable in multiple different sketches across multiple part studios, how can you find what dimensions are driven by the #length variable?
Re: Cannot publish feature script
@jason_ryan337 looks like you found the solution already but for anyone coming after looking to publish and running into this issue, the "Description" field on the feature definition needs to be labelled "Feature Type Description" instead. It's a subtle thing I ran into when I was first publishing some of my scripts that isn't obvious from the notification alone because none of the standard library scripts have this field filled out for their feature definitions. It is documented in the UIspec page for featurescript though.
Re: Trouble with default values in feature script
@jnewth's resources are exactly what you need. Take the time to read through the FS documentation. If you look here:
You should be able to come up with the code you need. Something like:
annotation { "Name" : "My Length"}
isLength(definition.myLength, { (millimeter) : [0, 10, 1000] } as LengthBoundSpec);
annotation { "Name" : "My Integer"}
isInteger(definition.myInteger, { (unitless) : [0, 20, 1000] } as IntegerBoundSpec);
Re: Is there a way to edit or delete a "version"?
We should not mix up versions and variants. I've been trying to explain the concept to a colleague this week, and he said Onshape wasn't for him and insisted on the fact that he'd need to create 'versions' all the time just to try different approaches. What he really meant was 'variants' to try and then choose one to get on with the job and maybe make it a version.
That is where branching comes in, or configurations, or maybe suppressing certain features for a while, or deriving a basic part into other part studios and try different details there.
Anyway, I believe the trouble moste have with versions is a linguistic issue in the first place.
Re: a unique asymmetrical chamfer
another way would be to use the chamfer as designed like your first image and then use move face with the rotate option and rotate the whole face of that chamfer till you get the desired look that you want.
MDesign
Re: a unique asymmetrical chamfer
.
One way to do this is by creating a sketch profile on the left "Triangle A" and a sketch profile on the right "Triangle B" and using the Loft subtract to remove the lofted space between.
Another way would be to draw a sketch line on the top of the part, similar to your yellow line, then loft it to a line representing the end of the current chamfer. Then you can split the part using the lofted surface.
.
Re: External Editor
https://cad.onshape.com/glassworks/explorer/#/FeatureStudio/getFeatureStudioContents
and
https://cad.onshape.com/glassworks/explorer/#/FeatureStudio/updateFeatureStudioContents
I read in a thread from years past that the featurescript IDE is based on a generic web IDE (ace), so the features are likely what came out of the box. Actually, code folding is supported: on windows highlight a section and do alt-L. Wish I knew that earlier...
Re: 3D from Excel to Onshape
If still interested, I can give you a hand to do it. It will not be too difficult to automate.