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
oh its public now
The Onsherpa | Reach peak Onshape productivity
www.theonsherpa.com
You got a query variable set to evaluate on use with all solid bodies. The bodies being inserted are pretty solid after insertion. That means they get added to the subtraction scope. Was scratching my head real hard for that one.
Derek Van Allen | Engineering Consultant | MeddlerV16 - New updates: global rotation of all seeds to make flipping stuff easier. Composite part support for insertion operations.
Derek Van Allen | Engineering Consultant | MeddlerOmg that's it! insane. It was an excellent case study in why it's important to capture ALL of the right logic with your Query Variables, not just what happens to get the selection you want right now. I was actually able to fix it by declaring another qv of the same name with "evaluate on use" UNchecked. That's an interesting workflow I'd not considered. You can essential turn "evaluate on use" off/on at various points in your tree that way.
The Onsherpa | Reach peak Onshape productivity
www.theonsherpa.com
@EvanReese there's probably some utility there as well by starting with a QV evaluated one way on startup and then running a new QV with the same name copied into itself stored as Selection as some kind of cache, or to recursively iterate on queries. Or a qNothing.
Derek Van Allen | Engineering Consultant | Meddler