question on patern

Replies to This Discussion

Permalink Reply by peter fotiadis on February 7, 2016 at 12:51am

Post some stuff otherwise we are talking thin air.

Other than that, the recommended way to "combine" items in collections is to use Relative Item(s) ... where you "shift" branches/items and then you combine stuff by picking items from the "original" collection AND from the "modified" one.

Plan B involves code to do ... er ... hmm ... anything (sky's the limit).

Permalink Reply by Konstantinos andreou on February 7, 2016 at 5:16am

hey so here a screenshot and the data. so now i have the wind bracers and louvers and i want to make a pattern out of them for example one row with wind bracers and louvers and one row with only the windows . i hope you can understand;] 

Attachments:

• screenshot1.jpg, 347 KB
• abgabe.3dm, 24 KB
• abgabe.gh, 37 KB

Permalink Reply by Joseph Oster on February 7, 2016 at 10:20am

You lost your columns and rows due to flattening in the first group at the top of the canvas; that makes it harder to refer to them later.

Permalink Reply by peter fotiadis on February 7, 2016 at 12:30pm

OK, you are a compatriot so you'll receive Lord's full support, he he

Let's reload the matrix on that one. In a series of tutorials you'll see how to do it the proper way ... and when it's finished you'll receive (in your mail) the other thingy (straight from the Dark Side that does it with instance definitions (in real-time: meaning zero delay time) plus some "other" rather very unusual things).

V1: doing the grid, the coordinate systems and putting the frame in place.

next tutorials (V2 - V6: mild, wild and freaky stuff).

best, Lord of Darkness

Attachments:

• Reload_the_matrix_V1.gh, 143 KB

Permalink Reply by Konstantinos andreou on February 7, 2016 at 1:05pm

sorry but i dont get it;p what do i have to do with the file that you've attached?

Permalink Reply by peter fotiadis on February 8, 2016 at 2:17am

LOL ... can I have some other question please?

Maybe this can shed some light?

BTW: these are "on going" tutorials you know ... the V1 was about getting the gist of the critical part: coordinate systems and ... making ONE thing (or many) and THEN using the planes and the orient component. In the real world we use instance definitions boosting the response time by a factor of 100 and reducing the baked file size by ... er ... you name it.

Attachments:

• Reload_the_matrix_V2.gh, 166 KB

Permalink Reply by peter fotiadis on February 8, 2016 at 4:06am

Added a random option and something for (my) fun.

Observe that the more the "objects" (frames, louvers, xBars) - not to mention what happens if we add real-life detailing to these - the less "responsive" GH becomes (for more than obvious reasons).

For the solution wait the V4.

Attachments:

• Reload_the_matrix_V3.gh, 178 KB

Permalink Reply by Konstantinos andreou on February 9, 2016 at 4:49am

hey yes now i get it really heplfull tutorialrs;] thank you

Permalink Reply by peter fotiadis on February 9, 2016 at 4:55am

Try this as well:  it's code but you can always pretend that some good Samaritan provided it as a compiled (i.e. sealed) component in some GH add-on.

You can use this instead of the other methods for the xBar patterning (feed it with the planes tree and redirect the output to the orient component that deals with the xBars).

PS: if the input is Planes the autoZoom doesn't work (it works with GeometryBase types and Point3d).

Attachments:

• Patterns_in_1d_trees_V1.gh, 123 KB