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
@EvanReese @zoltan_nemeth973 try Move Face version 2780. They've been doing some engine work on Move Face recently that I ran into that this was the last stable version before some breaking changes were made. My bugs were related to sheet metal, and specifically an opEdgeChange call that isn't what you guys are working with but whatever bugs there were in the in between builds they were on the engine side and not the featurescript side. Running an older version might help discover the edge case.
Derek Van Allen | Engineering Consultant | MeddlerUsed this the other day. It's brilliant, well implemented.
.
RENDERCAD
rendercad.ai - Photorealistic product rendering.
â–šâ–žâ–šâ–žâ–šâ–žâ–šâ–žâ–š
________________________________________________________________________
I tried Move Face version 2780 and it throws the same SELF_INTERSECTING_CURVE_SELECTED error.
Thanks, @Derek_Van_Allen_BD - I have tried the old Move Face version, but the Query Pattern doesn't work with that either. @EvanReese , I confirm that Thicked worked, but for curiosity, I have also tried Delete Face, and it doesn't work either. (I also assume after this that Replace Face would fall into this category, too!)
@EvanReese worth to try wrapping query items in either makeRobustQuery(context, itemQuery) or qUnion(itemQuery, startTracking(context, itemQuery))
@Konst_Sh I'm still not entirely sure how and when makeRobustQuery is applicable to any given situation. It sounds super useful but the handful of times I reached for it, tracking was the answer instead.
Derek Van Allen | Engineering Consultant | MeddlerI have same impression regarding robust query actually, another cryptic function is startTrackingIdentity
If @Konst_Sh and @Derek_Van_Allen_BD don’t understand these functions, I’m guessing most of us mere mortals are even more baffled. Queries are powerful but also one of the more confusing parts of FS. I do find having query variables in regular Onshape helps a lot.
Simon Gatrall | Product Development, Engineering, Design, Onshape | Ex- IDEO, PCH, Unagi, Carbon | LinkedIn
the thing is that at some moment you stop caring, if one doesn't work you just try another, If nothing of graceful queries work you just switch to a greedy procedural filtering based on spatial queries.
I did some more testing: it's not true that Query Pattern doesn't work with Move Face in general! It only fails when Move Face is the first feature to pattern (the one that references the Seed!) If the first feature is something else, however - e.g., an Extract - and it is followed by a Move Face, it already works. See here: https://cad.onshape.com/documents/4a142ce31429dae12b75a3dc/w/6a2a2436caf0724cd2e8bba1/e/815c28e2113af59046d33237