Get Geometry component does not support planes:
what is happening is a subtle conversion/cast from plane to surface…
Here you can see the same error without even using hops:
The conversion from surface to plane is actually a double conversion: surface>curve>plane
re-extract you correct plane by evaluating the surface at 0,0 inside the Hops …
Remotely similar argument here: Grasshopper Player defects
(which is marked for 9.x …)
@AndyPayne @stevebaer @DavidRutten
Get Geometry component could be better if able to accept more types of geometries (Line, Plane, Vector, Transform…) , particularly when for deeper use with Hops.
Maybe a “Get Data” which just preserve the original type can be done?
Side note, probably more related to GH2:
a user visible explicit feedback of when an item is converted due to param type would be useful
(string>number , line>vector, point>plane, etc etc)
… maybe it’s already planned, I’m not informed about Gh2…
EDIT:
this is also related to this:
Programming and editing .gh documents for Hops are much more “distant” from user experience, compared to normal gh programming and clusters. You can’t see what is going on.
In this case Andrew was not able to see that Get Geometry (iPlane) is outputting a surface instead of a plane. Nobody can.
When you open it, everything is orange with no data.
And if, while editing its code, you pass a plane to it, it seems to pass it correctly:
but this would not really happens while inside Hops.
Hops can be better.
We are seeing an incredible potential (for simpler managing complex datatree) but we are not there yet.