Rhino 8 seems to neglect the ‘referenced’ properties of Breps when brought in using either Geometry Pipeline or the new Query Model Objects.
In the image you can see that if I bring in the Breps via a Geometry container, the referenced user-text attributes are imported. But if I use the Brep container, the ‘referenced’ state is removed resulting in losing the attribute information as well.
I also tested with Meshes, but they seem to work as they should.
My question, is there a specific reason for this and can we get this reverted back to the way it was? This breaks a lot of Rhino 7 Grasshopper scripts for me. @DavidRutten@AndyPayne
The primary reason this is happening in your case is because the Geometry Pipeline component is returning a Referenced Extrusion and then you are casting it to a different geometry type (ie. Brep) which is causing it to lose the reference. If you were to simply use the Extrusion parameter, instead of the Brep parameter, then it should work as expected.
Nevertheless, we thought it would be a good idea to add a proper casting mechanism where a GH Brep would retain a reference if it’s being cast from an GH Extrusion or a GH SubD. I have fixed this issue (RH-83226) and it should be available in the next Rhino 8.11 release. Thanks for reporting this.
The reason why having an Extrusion parameter would not be a good solution is that there might be both Extrusions and more complex polysurfaces in the script. Extrusion is too restricting in this case.
