The new evaluate field component appears to work with geometry that is outside of a block but does not work when a block is referenced and then the geometry inside that block is accessed. See below. The top script references the curve after the block has been exploded manually. The bottom tries to access geometry within the block either by exploding the block or by access the block definition components. Either way the field returns a 0 value.
I’m assuming this has something to do with the new way you are referencing GUID’s in grasshopper?
For anyone that is having this issue I figured out how to get it to work. You need to use the block definition component, expode gets you geometry but without the GUID. Get the GUID of the object and then replace that with the one in the field. Somehow the GUID of the field used to create the field pre-block creation gets redefined post-block creation. Potentiall same issue as discussed here:
Why do nested Block Instance GUIDs change when the parent Block is edited? - Rhino / Rhino for Windows - McNeel Forum
Since I’m doing this in grasshopper, I can just find the length etc and write this to a key value pair. I think this is a better work flow if you are not having users update the block manually.
