Home› General

Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. 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.

🚨 Custom Feature Alert 🚨 Query Pattern

EvanReeseEvanReese Member, Mentor Posts: 2,759 PRO
edited January 17 in General

Get the feature here.

Query Pattern performs a feature pattern, but swaps out the input query every time it loops, allowing you to perform the same operations on very different faces, edges, bodies, etc. Here's how it works!

Evan Reese
The Onsherpa | Reach peak Onshape productivity
www.theonsherpa.com

Comments

  • Konst_ShKonst_Sh Member Posts: 115 PRO

    Smart idea, Evan. You might also consider allowing array of query inputs as iteration input, so that it could consume multi-entity seed queries

  • EvanReeseEvanReese Member, Mentor Posts: 2,759 PRO

    Thanks, Konstantin! Do you mean so that you could, for example, have one seed for an edge and another for a face or something? What scenario do you have in mind?

    Evan Reese
    The Onsherpa | Reach peak Onshape productivity
    www.theonsherpa.com
  • Konst_ShKonst_Sh Member Posts: 115 PRO

    For example if the seed would need to be a union of edges for fill surface feature and would want to poppulate it across array of edge loops that wouldn't be possible currently, because its iterating through individual entities

  • S1monS1mon Member Posts: 3,860 PRO

    Once again, @EvanReese adds amazing functionality that I'd love to see in the first party tools. There's a lot to digest here, but I'm looking forward to doing things that used to be more something that you needed Rhino+Grasshopper to do.

    Simon Gatrall | Product Development Specialist | Open For Work

  • Derek_Van_Allen_BDDerek_Van_Allen_BD Member Posts: 589 PRO

    When I did the update to Query Variable Plus to add qEverything I thought about putting qNothing in there as bait to see what @EvanReese would do with setting a query variable to nothing. I pictured something like this.

  • EvanReeseEvanReese Member, Mentor Posts: 2,759 PRO

    Add qSomething and we'll see

    Evan Reese
    The Onsherpa | Reach peak Onshape productivity
    www.theonsherpa.com
  • EvanReeseEvanReese Member, Mentor Posts: 2,759 PRO

    @S1mon Yep! Try pairing it with face curves to split it to make a grid and iterate on that

    Evan Reese
    The Onsherpa | Reach peak Onshape productivity
    www.theonsherpa.com
  • Derek_Van_Allen_BDDerek_Van_Allen_BD Member Posts: 589 PRO

    OOH, that'd be a slick way to get around some frames limitations too where complex junctions aren't supported out of the box. I gotta try that.

  • S1monS1mon Member Posts: 3,860 PRO

    @EvanReese I could see a version of attractor pattern that just creates a series of points or mate connectors for the centers of some feature which could then be patterned with query pattern.

    The Face curves idea is great for things that want to be in a grid like pattern on a surface, but to get the triangular pattern we’ll need something else.

    Simon Gatrall | Product Development Specialist | Open For Work

Sign In or Register to comment.