I’ve accessed the corners of a box using Field at Index. The positions themselves are non-zero, tested by placing Cube primitive. But when I calculated distance between two points to use in Grid primitive, the connections are red and Grid is invisible. Is the Grid node bugged or it is something else?
You plugged a field into a value socket. When a socket is diamond shaped it is a field. If it is round it is a value. If it is diamond with a little dot in the center it accepts both.
1 Like
Damn complicated. Any way to convert between them within the same node tree?
Do you want to get the max an min values of the box? If that is the case then perhaps the “bounding box” node can help you.
I wanted to generate a room based on a box mesh (lets assume it stays orthogonal), where each wall would be a separate submesh based on corresponding face. So then I could both move the sides of the box in Edit mode, and apply some operation on each wall (enable or disable based on bool, or change its mesh). Bounding Box may help, but I’m not sure it will be less hassle than accessing each corner by index. Since I’ll still need to calculate positions of the corners (for things like finding center of each wall)
The following method works. I am not that savvy with GN and I am sure there are more elegant ways but it does work. Select the Indices in the red box.
1 Like
Definitely more elegant that what I’d use, thanks
Still, thats a dev oversight that Grid cell size cant be changed directly the way I tried it. Of course I can rescale the resulting mesh afterwards, but it is much clunkier