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: New Feature: Tween Curve (WIP)
I don't want to get anyone too excited yet but…
Re: Every time I visit the onshape website I need to log in again. Is there a "remember me" option?
always logs me out when I close the tab too aggressive security. onshape should really disable this feature or just add an option to stay logged in/remember me.
Re: Cross hatching a rib
@seyozen I was only pulling your leg. I would love to have this as a feature but knowing what pain the developers went through at SoldiWorks in order to make this work (and it only works on really simple geometry) I know this is a major undertaking.
Re: Update: Super Derive with mate connectors
Unfortuantely, the variables are measured dimensions from imported parts.
ry_gb
Re: Cross hatching a rib
I appreciate the standards are there and strictly speaking would need that feature but have to say I doubt this would be very useful in the "real-world"…
As Neil points out, you would need a second view to properly disambiguate the design anyway…
More importantly, is there anyone still doing "real work" that doesn't include a STEP file with the 3D geometry alongside 2D drawings? Our 2D drawings are only used to convey design intent and tolerances and other "notes" that aren't part of the 3D model.
I don't think 2D drawings need to fully describe the design anymore so the standards should really be updated to reflect that. Our drawing template has a "built-in" note that says the drawing doesn't fully describe the part geometry and to refer to the 3D file and I've never heard a supplier complain about it! (but have heard many times questions like "do you have a STEP file? or for "2D only" process a 1:1 scale DXF)…
I hope 3D drawings will disappear within my lifetime (although somehow doubtful). For now I look forward to MBD capabilities in Onshape to hopefully reduce the number of 2D drawings we have to make (or at least further reduce the information needed).
Re: New CNC Overcuts (/Dogbones) custom feature
@hendrik_kueck big fan of this script. It was one of the biggest changes to our company practices coming from Solidworks which has no equivalent for corner treatment. I used to do my corner overcuts with a chamfer and a hole feature centered on the span of the chamfer and this is insanely faster.
I do have my own custom copy with the only change being that if a part contains no concave edges I'll skip the body and move on to the next one in the list to overcut. Current published version will fail if you pass it a body needing no overcuts. Otherwise 10/10 feature and I'm glad to never have to apply that old 4 step solidworks method ever again.
Re: Featurescript: Setting parameters to optional
@ry_gb I'd get the key steps put into their own functions, which can be used as needed in either feature. Those functions could live entirely in their own feature studio and be imported to the feature studio for Loft Fillet and Auto Loft Connections.
As for conditional UI things others have covered it, but you just need to write your code in such a way that it doesn't fail if they don't use a certain field. For example if you have an optional query parameter you might do this
if(isQueryEmpty(context, definition.pointReference))
{
// If the query is empty, decide how to proceed without it. Maybe you don't need to do anything special, or maybe you wanna set it to something like this
definition.pointReference = qOrigin(EntityType.BODY);
// OR
definition.pointReference = qNothing();
}
else
{
// Do whatever you want to use the reference
}
Re: Featurescript: Setting parameters to optional
If you create an opCreateMatchConnections function separately in its own feature studio in a document, you would be able to import it in AutoLoftConnections as well as the Loft fillet feature and get the benefit of version control where you might update it in one feature and deal with ramifications while the other one stays put until you get to updating it there.
I think the ‘optional’ functions all have a default or fall-back setting for if the argument is undefined.
In your opExtrude example (speculating here): if (definition.startBound != undefined)
{offsets the starting faces or edges by startBound value}
So if startBound is not used, it’ll still just work with the original faces or values…
these were my 2 cents. Would be very curious to hear what @Caden_Armstrong’s advice is on this matter of when/how to split functions into their own feature studio.
Re: Featurescript: Setting parameters to optional
You can conditionally show and hide UI like this: https://cad.onshape.com/documents/c7c08274a0d273b9a5f5b47d/w/f348f21ad2fa5c8771f1e1b1/e/0abb9be049d15f1839c40841
This can be controlled manually when you insert functions, or dynamically with either user choices or edit logic.
.
