Thanks for the lovely video. But what about converting SubD into a mesh. Furthermore, I have experienced an issue where when I perform mesh difference between two meshes I get a mesh intersection instead or in other cases the mesh difference operation is skipped completely resulting in A-B = A. Instead of A-B = A-B. How can I solve this issue if you have any knowledge of it, it would be greatly appreciated. Thank you
Boolean operations in grasshopper are not reliable and prone to failure. Even there, Boolean operations with breps and more successful than Boolean operations in meshes. My suggestion would be to convert mesh into brep for any Boolean operations and then convert back to mesh .
Hello, do you know if the steps work on Rhino7? I did all the steps and even downloaded the file from Qbrick Lab, but it didn't work; the mesh is not working.
Hello! Thanks for the great tutorial! Can I make this simulation with a set of surfaces? Or should I somehow convert them into a mesh and connect them? p.s. and an additional question, can I somehow display the amount of water that is left on the surface? Maybe a color gradient that would display the number of these balls?
Hi. Sorry for the late reply. To use surfaces for simulation, you will have to convert the surfaces into meshes and then connect them to kangaroo. You can display the number of ball collected in one area by using Point Group component. It allows for grouping of points based on distance threshold.
hello for some odd reason when I do the curve closet to point command it turns red and there's an error "1. Data conversion failed from Number to Point" I followed step by step however the points don't show up even if they're right on the circle. HELP PLEASEEE
Hey Nur. I think tri-remesh should work for triangulation. Incase it doesn't work, I prefer to use Mesh Machine as second option. If you don't know how to get started, share your Rhino+gh file to qbricklab@gmail.com and I'll help you.
there is one issue when we flip the whole algorithm to make other side, the boxes on top part are colliding, even if we do negative y and changing from -0.5 to 0.5 still in middle there are some cubiods which are still colliding.
Hey, thanks for your video. I applied everything correctly starting from MeshThicken while using existing geometry (mesh from mapbox). However, the spheres pass through the terrain. I have no error messages. Do you have any idea what could have went wrong? ps: here's what the component help says "Computes a new mesh that is a closed solid, provided that the original mesh is offsettable and oriented" ; I have tried manually offsetting the original mesh, it worked and it seems like it's oriented as well.
There are slicer software that generate G-codes that is used by 3D printer to print the geometry. This video covers the workflow for modelling a closed geometry, which is the essential starting point for any object that is to be printed.
At 8:45 when I used the sort aling curve, the points are sorted but not in the correct order, the stating points of warp and weft boundary polylines were not aligned, resulted in crossed triagulated faces. I used shift list on the points then get the desired output. Anyone run into the same problem or know why this happen?
