Really thankful for having developer and artist like you to share the works and tools created to everyone... I am a student, and just started using grasshopper, this series is very fascinating! Please keep up the great work and can't wait to see more!
@@TempAutonArch Hello, just a quick question! Is it possible to set the numbers for the hexagon and the cube separately? For example what if I want 100 hexagons and 75 cubes? Thank you!
Hi, it is unfortunately not in the official release of Wasp. However, I implemented it in the current WIP version of Wasp, which you can find on Github
thank you for your videos they are clear and easy to follow! really appreciate it, came across many long winded videos. yours are so straightforward and a joy to learn from. thank you so much
@@TempAutonArch I have another question about the attributes, it seems that there is an error when I add an attribute that is sticking out of the basic part. Does the attribute only work within the basic part? ps. I'm trying to filter the attributes by materials in my architecture project for wasp. Unless there is a better way then I would love to hear it! Thank you for your work!
@mork3743 no, there should not be a problem. An attribute can be anything and does not need to fit within the part geometry. Feel free to send the files over Discord or email, and I can take a look.
The plugin and tutorials are great ! Thanks for sharing :) so just wanted to check with you wether there is any way to replace the final output with blocks.
If you use the DeconstructPart component on the final aggregated parts, in the TR input you will find the transformation data of the Part. You can use that transformation to transform your blocks, or transform the base planes of the blocks, and then use something like Elefront to bake blocks in place of the Part Geometry. Let me know if it is clear, if not I can send you an example file.
Temporary Autonomous Architecture okay, ty for the reply. Will try and get back to you. Last time I tried using the transform output- it did not work on polysrf/blocks - only works on low poly meshes - I will try again and get back
@@TempAutonArch hello there i've been following your tutorials so far and i'm working a project like this ( www.archdaily.com/120886/seeds-of-life-mekano-studio) and im having so difficulties can you share something that can do something to achieve sort of mass like that (rmkhanyzi@gmail.com) also is there any way to contact you. THANKS ALOT
Hi, these videos might help you out to develop your project further: th-cam.com/video/NJCE0tFWMlQ/w-d-xo.html th-cam.com/video/bJOzr1O_bbg/w-d-xo.html th-cam.com/video/dnrK8wpUNmg/w-d-xo.html If you need more help, you can join the Discord chat server ( discord.gg/Wke9Jt6 ).
They both are plug-ins for generation of assemblies from discrete units. However they have few differences, the main one being that Monoceros operates on a fixed cartesian grid, which is predefined, and fills the cells of this grid with elements based on their neighbouring relationships. Wasp instead works exclusively from the parts, and hence does not assume any predefined grid for the aggregation (the grid is generated by placing parts, and each part can change the choices available in the next step). So, it really depends what your goal is, whether you are more interested in defining multiple neighboring relationships between parts, at the cost of relying on a fixed grid, or if you are more interested in the growth process of the aggregation. Both really powerful tools, but for different purposes.
Had a doubt, could we use multiple geometries as proxy? One cube containing 2-3 detailed elements which are not one single entity but discrete ? If yes how ??
Yes, you can. Simply, when importing the proxy geometry, instead of selecting "set one geometry". you can choose "set multiple geometries" and select all the parts. Even if you plug a list of geometries, the Attribute component will still create a single Attribute object storing all the geometries. If instead you want to keep your elements separated and be able to access them independently, you can create one Attribute for each element, give them different names, and plug them all in the ATTR input of the Part. Wasp Parts can carry as many attributes as you want.
Hi, i might have found a bug? This Attribute function doesn't seem to work with Field Driven Aggregations? I was getting the error "1. No attribute found matching the provided id" from the Wasp_Get Attribute By Name node until i swapped from a Field Driven Aggregation to a Stochastic one. I've tested this in both my own script and the one with this video. Thanks!
Uhm, that is quite strange. I used Attributes several times with Field-Driven Aggregations, and never had problems. Can you send me the file either through the Wasp Discord Channel (discord.gg/Wke9Jt6) or send it to me via email at ghwasp@gmail.com? Thanks!
I have solved it. Now am not getting the same patterns as you did. It is saying the part can not be joined unless using the individual rules for P and T. The wasp is awesome by the way. Thanks.
I have solved it, Thanks. It seems that the use of nonsolid geometries while making a part was creating the issue. While I tried it with solids it is working fine. Thanks.
Really thankful for having developer and artist like you to share the works and tools created to everyone... I am a student, and just started using grasshopper, this series is very fascinating! Please keep up the great work and can't wait to see more!
Wow, thanks! Happy to hear!
@@TempAutonArch Hello, just a quick question! Is it possible to set the numbers for the hexagon and the cube separately? For example what if I want 100 hexagons and 75 cubes? Thank you!
Hi, it is unfortunately not in the official release of Wasp. However, I implemented it in the current WIP version of Wasp, which you can find on Github
You can see how to use it here: th-cam.com/video/rn2Obdd8T6E/w-d-xo.html
and here: th-cam.com/video/dnrK8wpUNmg/w-d-xo.html
@@TempAutonArch Thank you so much!
You are seriously the best grasshopper teacher on youtube!!
thank you for your videos they are clear and easy to follow! really appreciate it, came across many long winded videos. yours are so straightforward and a joy to learn from. thank you so much
Thank you very much! Fantacy components and very clear tutorials
Awesome. This series is amazing
Glad you enjoy it!
fantastic and well explained, thank you!
Is it possible to add multiple attributes to the basic part?
As many as you want
@@TempAutonArch I have another question about the attributes, it seems that there is an error when I add an attribute that is sticking out of the basic part. Does the attribute only work within the basic part?
ps. I'm trying to filter the attributes by materials in my architecture project for wasp. Unless there is a better way then I would love to hear it! Thank you for your work!
@mork3743 no, there should not be a problem. An attribute can be anything and does not need to fit within the part geometry. Feel free to send the files over Discord or email, and I can take a look.
Thanks for the precious content. I appreciate a lot.
Happy to hear!
The plugin and tutorials are great ! Thanks for sharing :) so just wanted to check with you wether there is any way to replace the final output with blocks.
If you use the DeconstructPart component on the final aggregated parts, in the TR input you will find the transformation data of the Part. You can use that transformation to transform your blocks, or transform the base planes of the blocks, and then use something like Elefront to bake blocks in place of the Part Geometry.
Let me know if it is clear, if not I can send you an example file.
Temporary Autonomous Architecture okay, ty for the reply. Will try and get back to you. Last time I tried using the transform output- it did not work on polysrf/blocks - only works on low poly meshes - I will try again and get back
@@TempAutonArch hello there i've been following your tutorials so far and i'm working a project like this ( www.archdaily.com/120886/seeds-of-life-mekano-studio) and im having so difficulties can you share something that can do something to achieve sort of mass like that (rmkhanyzi@gmail.com) also is there any way to contact you. THANKS ALOT
Hi, these videos might help you out to develop your project further:
th-cam.com/video/NJCE0tFWMlQ/w-d-xo.html
th-cam.com/video/bJOzr1O_bbg/w-d-xo.html
th-cam.com/video/dnrK8wpUNmg/w-d-xo.html
If you need more help, you can join the Discord chat server ( discord.gg/Wke9Jt6 ).
Excellent narration! But where can I download the agent model in lesson 002?
In the description: bit.ly/wasp101_002
What is the difference between Wasp and Monoceros for grasshopper ?
They both are plug-ins for generation of assemblies from discrete units. However they have few differences, the main one being that Monoceros operates on a fixed cartesian grid, which is predefined, and fills the cells of this grid with elements based on their neighbouring relationships. Wasp instead works exclusively from the parts, and hence does not assume any predefined grid for the aggregation (the grid is generated by placing parts, and each part can change the choices available in the next step).
So, it really depends what your goal is, whether you are more interested in defining multiple neighboring relationships between parts, at the cost of relying on a fixed grid, or if you are more interested in the growth process of the aggregation. Both really powerful tools, but for different purposes.
Had a doubt, could we use multiple geometries as proxy? One cube containing 2-3 detailed elements which are not one single entity but discrete ? If yes how ??
Yes, you can. Simply, when importing the proxy geometry, instead of selecting "set one geometry". you can choose "set multiple geometries" and select all the parts. Even if you plug a list of geometries, the Attribute component will still create a single Attribute object storing all the geometries.
If instead you want to keep your elements separated and be able to access them independently, you can create one Attribute for each element, give them different names, and plug them all in the ATTR input of the Part. Wasp Parts can carry as many attributes as you want.
@@TempAutonArch both the techniques worked! thank you so much for the clarification and resoponse
It shows "1. No attribute found matching the provided id" even if the id completely matches with all small caps done. What might be the problem
Maybe you have a capitalization (you pressed enter at the end of the name, and added a line in the panel?
Hi, i might have found a bug? This Attribute function doesn't seem to work with Field Driven Aggregations? I was getting the error "1. No attribute found matching the provided id" from the Wasp_Get Attribute By Name node until i swapped from a Field Driven Aggregation to a Stochastic one. I've tested this in both my own script and the one with this video. Thanks!
Uhm, that is quite strange. I used Attributes several times with Field-Driven Aggregations, and never had problems. Can you send me the file either through the Wasp Discord Channel (discord.gg/Wke9Jt6) or send it to me via email at ghwasp@gmail.com? Thanks!
The same Problem, and seems to be something wrong with Mesh Brep component because it doesn't show mesh preview
Could you send me a file where this happens? Either by email at ghwasp@gmail.com or on Discord ( (discord.gg/Wke9Jt6 ). Are you on Mac or on Windows?
@@TempAutonArch
Okkaay. . I've launched the file a few minutes.... and it works !!! I don't get what is happening!!!??
Are you or Windows or Mac? Which version of Rhino are you using?
I have followed the same and am getting an error stating that 'Exception: index out of range: 2". Please help
I have solved it. Now am not getting the same patterns as you did. It is saying the part can not be joined unless using the individual rules for P and T. The wasp is awesome by the way. Thanks.
Hi, I am not sure I understand your problem. Could you send me a file at ghwasp@gmail.com or on Discord?
I have solved it, Thanks. It seems that the use of nonsolid geometries while making a part was creating the issue. While I tried it with solids it is working fine. Thanks.
thank you so much
thank you very good
Welcome 😊
amazing