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: Improvements to Onshape - January 31st, 2025
Can someone double check my Math, but isn't today the 3 week mark since the last update? 😀
Re: Change part ID to be the same for all configurations
lol, no problem! I've done the same before. Glad its working!
Re: Lid for Bowl
MDesign is right, design style is up to you. Meantime here are some tools to use for your design including move face for clearance.
Re: Change part ID to be the same for all configurations
@MichaelPascoe I replied too soon, it does work!! This eliminates loads of downstream configurations and duplicate features. I wish I could change my answer from no to yes above. This certainly answered it. Thanks again!
Re: Change part ID to be the same for all configurations
Not sure this will work for your case but it may. @lana made a FeatureScript Assign Identity for manually assigning ID's. Pretty awesome:
Re: NOOB at work... very basic question
quadrilateral? check off the show constraints and remove the constraints that are causing the issue. also check out learn.onshape.com to learn more about constraints and more
MDesign
Re: opCreateCurvesOnFace() for parameters 0 and 1 fail?
Thanks fellas. Here's what I ended up coming up with. Since my case is somewhat narrow I don't have to worry about dealing with trimmed surfaces and I know that the only 2 edges a periodic surface will have are the ones I need.
function getEdgesOfPeriodicSurface(context is Context, face is Query) returns array{var paramPoints = evFaceTangentPlanes(context, {"face" : face,"parameters" : [vector(0, 0), vector(1, 1)]});return [qContainsPoint(edges, paramPoints[0].origin), qContainsPoint(edges, paramPoints[1].origin)];}
Re: Routing curve & Control point curve - Introduction of two new features for 3D curve creation
Jonathan, thanks for the feedback and continued interest in this feature… Firstly, how many points are in your Routing curve array? Does it become too laggy after a certain number of them, or is your comment a general one.
As my own "general" comment, we are doing a lot of work on this feature, and despite not having shared any updates since the first 11 updates we made following the Custom feature's launch last year, we've been addressing many of the issues that have been raised in this thread. Much of it with usability of the manipulator, point creation,/referencing, but also much more. I hope to share details about this shortly. Rest assured your feedback has been heard, appreciated and invaluable. Please stay tuned.
