Even if you do not see any issue, dependency cycle still here. Blender support dependencies between multiple properties on the same data block, but can not do that for components of the same…
Nothing here is odd, geometry nodes can output only a fields outside of the modifier.
What the point of this function right now?
To get access to the list of layers in a way that's safer than direct array access via a pointer-to-a-pointer?
`blender::Span<const Layer…
What the point of this function right now? Ideally you should change the things only via spans and move all non-trivial processing algorithm into separate free functions.
I actually do like the second one case from the video to be. Even more, with multi-input support, but this is not main one.
Every time you put the hash into the socket that define number of details of geometry, you trying to allocate more memory then anyone even can have. Totaly expected.
Please run make format in the root of your blender fork folder\
Between node with some smaller range of supported types and explicit mean to be exclusive/inclusive actually would be better to probably will allow us to remove float epsilon.
Yes this is…
I don't see why it should be a built-in node. Making a node group that calculates the Determinant is easy and is also already part of the Linear Algebra bundle that I presented.
This one is…
Just use one more compare nodes and boolean math?