Very Useful Tutorial. Thankyou Andrea! I am using Wasp 5.0. Plane constraints work fine and seamlessly with 1 or 2 planes constructed using point(s), but it does not work at all with the voronoi cell. It raises a warning that it could not place 'n-1' parts. Why is it so ? Also, the algorithm fails to run if I try to connect another geometry with respective connecting points and direction curves from the same rhino file. Thank you in advance :)
Hi, could you send me the file? Either per email at ghwasp@gmail.com, or on the Discord Support Server (discord.gg/Wke9Jt6). Then I can take a better look.
how can I reduce the density of the aggregation? When I type N=1000 OR ABOVE, it looks very dense. How can I reduce the density, but make the overall structure grow larger? Thanks!
Well, the aggregation will grow dense if it it allowed to. There is no direct way to control that, because this is determined by a lot of different parameters. The best solution would have to design a part and its connection so that they do not allow aggregation with a high density. Another option would be to use Adjacency and Exclusion constraints to make sure that parts are staying apart from each other. This is still an experimental feature of Wasp, but you can see it and test it from this video: ruclips.net/video/dnrK8wpUNmg/видео.html Finally, another option to avoid high densities would be to use an additional collider attached to the part, to make sure that you make an area around the part itself not available to other parts.
Probably, there's a bug with placing reference part. When i place reference part too far away from the 0.0.0 coordinate (i.e. -150000, -75000.0), Part element starts showing "1. Could not compute a valid collider geometry. Please provide a valid collider in the COLL input.". Then i randomly move reference part across the whole scene and there's a chance that there'll be no errors. Thus there're some "anomaly" zones where algorithm doesn't work. I faced this problem several times during the tutorial series and got different errors such as "1. Could not place N parts" in a aggregation components, so no matter what kind errors it shows, the problem is with placing the reference part
I checked the file you sent by email, and the error has to do with your collider. As you used the geometry itself as collider, your geometries have a strange behavior, and they often do not work (actually, they should never work!). The collider should be calculated internally by Wasp. If you provide a collider yourself, it should not be the geometry of the part itself, but a geometry which is created from the base one through an inwards offset of a small amount. If the collider is calculated internally, the aggregation seems to always work. I will send you the file via email to check. Thanks for reporting the issue!
Ooh, that's brilliant - and there's a mesh constraint too. Excellent.
Mesh constraints Tutorial coming soon 😉
Thank you so much!!! This is brilliant!
Yeah, another Wasp Tutorial!! Thank you!
You are welcome 😉
Very Useful Tutorial. Thankyou Andrea! I am using Wasp 5.0. Plane constraints work fine and seamlessly with 1 or 2 planes constructed using point(s), but it does not work at all with the voronoi cell. It raises a warning that it could not place 'n-1' parts. Why is it so ? Also, the algorithm fails to run if I try to connect another geometry with respective connecting points and direction curves from the same rhino file. Thank you in advance :)
Hi,
could you send me the file? Either per email at ghwasp@gmail.com, or on the Discord Support Server (discord.gg/Wke9Jt6). Then I can take a better look.
how can I reduce the density of the aggregation? When I type N=1000 OR ABOVE, it looks very dense. How can I reduce the density, but make the overall structure grow larger? Thanks!
Well, the aggregation will grow dense if it it allowed to. There is no direct way to control that, because this is determined by a lot of different parameters. The best solution would have to design a part and its connection so that they do not allow aggregation with a high density.
Another option would be to use Adjacency and Exclusion constraints to make sure that parts are staying apart from each other. This is still an experimental feature of Wasp, but you can see it and test it from this video: ruclips.net/video/dnrK8wpUNmg/видео.html
Finally, another option to avoid high densities would be to use an additional collider attached to the part, to make sure that you make an area around the part itself not available to other parts.
@@TempAutonArch thanks so much:)
Probably, there's a bug with placing reference part.
When i place reference part too far away from the 0.0.0 coordinate (i.e. -150000, -75000.0), Part element starts showing "1. Could not compute a valid collider geometry. Please provide a valid collider in the COLL input.". Then i randomly move reference part across the whole scene and there's a chance that there'll be no errors. Thus there're some "anomaly" zones where algorithm doesn't work. I faced this problem several times during the tutorial series and got different errors such as "1. Could not place N parts" in a aggregation components, so no matter what kind errors it shows, the problem is with placing the reference part
I checked the file you sent by email, and the error has to do with your collider. As you used the geometry itself as collider, your geometries have a strange behavior, and they often do not work (actually, they should never work!). The collider should be calculated internally by Wasp. If you provide a collider yourself, it should not be the geometry of the part itself, but a geometry which is created from the base one through an inwards offset of a small amount.
If the collider is calculated internally, the aggregation seems to always work. I will send you the file via email to check. Thanks for reporting the issue!
I will make a video about colliders soon ;)