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.
Comments
I might split that out since you're talking about something that modifies the geometry. Sounds potentially very useful for molds etc.
Simon Gatrall | Product Development, Engineering, Design, Onshape | Ex- IDEO, PCH, Unagi, Carbon | LinkedIn
I think it’s cleaner if that lives as a different feature. I can see more features coming that modify geometry and output a QV for downstream operations (like the auto split edges feature I just made based on Ramons autoLoftconnections work)
People looking for this ‘split faces by direction function’ aren’t going to be looking for it in a QV function, nor does the QV function lend itself well for the interface and functionality expansion that this operation may warrant later down the line.
Yeah probably best to just make a different feature instead of making QV+ sometimes produce unexpected behavior. Looks like the only 2 real operations that return a query are related to shadow projection or isocline results for draft type features so I'll just split those off into their own thing.
Derek Van Allen | Engineering Consultant | MeddlerLooks like one of my previous updates overrode the qEverything and qParallelish options. Restored them and added the icon in V13.
Next update coming today likely. Trying to make it possible to pass QVs through a derive operation to save selection sets in one document and reuse them in another document using attributes.
Derek Van Allen | Engineering Consultant | MeddlerV15 release brings the ability to save and load Query Variable selections to pass between derived part studios. Set up a QV in your seed document and check the box to save that selection for use in derived studios and now all of those entities will be labelled with an attribute that stores information about the name of the QV on those entities. Then when you derive those parts / entities into another document the attributes come with them and you run a second QV+ targeting the derive operation, all of the attributes that QV+ picks up from the geometry will get reconstructed into new QVs with their original names.
If you're a fan of procedural workflows this update was for you.
Derek Van Allen | Engineering Consultant | MeddlerSiiiick!
The Onsherpa | Reach peak Onshape productivity
www.theonsherpa.com
Oh boy, I was just thinking about this functionality yesterday! Thanks @Derek_Van_Allen_BD !
I'm not sure if I'm making a mistake, but Size comparison seems to be not working correctly.
Could be something I messed up. Care to link the document for diagnosis?
Derek Van Allen | Engineering Consultant | MeddlerHere you go!
Pattern Testing, size comparison bug
Also, wanted to say a huge thanks, because I can now stop using Grasshopper with your tools and Evan's attractor pattern for this simpler patterns I use for FDM printing.
Ah, looks like a scale related issue. My tolerance values are not size dependent on the input so it's casting too wide a net at smaller scales. I don't typically work in mm scale so that explains why I missed this. I'll look into updating that to be some percentage of the input reference instead of a global tolerance for comparison.
Derek Van Allen | Engineering Consultant | MeddlerThanks a bunch!
Another one one I've noticed is in the Positional > plane normal, it selects faces that are normal to the chosen face independent of direction. Would love for that to have the ability to have it only allow if the normal is actually in the same direction as the reference face.
For example, the orange part I posted earlier, those internal crosses are identical on top and bottom and exist on the same plane, but I just wanted to select all the ones that were facing upward in order to chamfer. Had to split the part into two bodies, query the faces, then boolean, then chamfer.
@armandoRR looks like there's an overload for the parallelPlanes query that I could use to toggle parallel / antiparallel geometry so I can pencil that in for an update as well. Currently I'm messing around with sheet metal queries (and inventing a few new ones that I would argue should already exist) so it may take a moment before I push that update.
Derek Van Allen | Engineering Consultant | Meddler