Is this in the python API? If so I am having trouble finding it. I have found the corresponding c function, but I am yet to find any usages of it in the source to see use case examples

Hi, I'd like to have stab at this, I wonder if you could expand on "the data would be accessed directly from the evaluated geometry set of the active object." Is this the alternative to the way the search in geometry nodes accesses/stores the attribute data in the node ui storage? So instead of having to store the data and later access it, it can be directly accessed through an existing api?

Hi, I have a working fix for this, but I have a question about how it should be implemented. I was wondering if I should implement a new operator that copies the active tree in the geometry nodes modifier, and keep the old NewGeometryNodeTreeAssign. Then assign the new operator to the relevant button, or if I should just change the functionality of NewGeometryNodeTreeAssign to copy the active tree if it exists?

I tested it, and the collision works over 50m if the planes are extruded, so it seems to be a issue with simulation resolution when far from the origin.
I would love to have a go at investigating this, if anyone more experienced with this area of the code could give me a pointer as to where to start I'd be very grateful.

Could you give a description of how you created the plane? It also doesn't respond normally to other edit mode opetaions, so could be a wider bug not contained to knife tool.