# Geometry Nodes from Scratch - Notes
Some notes from me (Dalai) while watching the [course by Simon](https://studio.blender.org/training/geometry-nodes-from-scratch/).
## 1. UI Alignment Bug:
## 2. Mesh Primitives Modifier Fields
If the fields are not being calculated on the Group Input > Geometry, should they really be given the option of using an "attribute"?
Is this for built-in attributes?
## 3. Duplicated Group Input Parameters
When duplicating an existing Input, the range and default values are not copied over.
## 4. Performance of Realized Instance
In cases like this is the geometry actually realized? Or does this fall under "implementation detail", where under the hood they could still be kept as instances?
I wonder if this is one of those potential performance improvements that we could do.
For another example, see Random thoughts #2.
## 5. Spreadsheet Color Filter Operations
In the Spreadsheet, there is no "Less Than", "Greater Than" option for Color Attributes (e.g., vertex color). Only "Equal to":
## 6. Anti-alias
Nothing to do with Geometry Nodes, but would be so nice to have better anti-aliasing:
## 7. Geometry Input Material
We still need a way to get the material currently assigned to a geometry and re-use it in the node tree. Specially for trees that actually use the Geometry Input.
*Note: The workaround of using Object material doesn't work if you make multiple materials in the object. But maybe this is just a bug.*
## 8. Attributes Propagation and Volume
If I capture an attribute before converting a mesh to points then to volumes then to mesh again the attribute doesn't propagate.
I wonder if having the node that can directly convert from a mesh to a volume would solve that (besides improving the overall performance).
## 9. Join Attributes
We still need the option to join attributes. In this example the "Top" selection atttribute could be joined together.
Is the modifier stack a way to organize different node pages?
For example, the same way that for textures we can choose the blending mode, in this case we could pick between "join" or "stack".
Instead of realizing the geometry to make bounding box, you can just pipe another bounding box node with the realized bounding boxes:
Update: I'm shocked that it seems to be cheaper to realize instead and then bounding box. But now that I think of it, it can make sense:
3. I want a T-Shirt with Simon's face and the phrase "*So let's make just a little bit more space.*". Or at the very least a meme ;) #NodesPages
4. In Geometry Nodes, no selection == everything selected (e.g., in the Delete Geometry node). Just something to keep in mind for the discussions about selection masks.
5. It would be interesting to see some values in the spreadsheet editor as distribution graphs instead of raw values.