BUG - Geometry Inputs No Longer Carry Model Object Attribute Data

Rhino WIP 8.0.23220.12305 no longer carries Model Object attributes through components with Geometry inputs such as “Transform” , “Move” and others.

This was working last week but no longer works in the most recent WIP.

Example:

Thanks!

Hi @michaelvollrath,

Now ‘Model Object’ is converted to geometry for convenience, but is up to the user reassign the geometry to the correct ‘Model Object’ again like this.

We had a bug before, but was more subtle.
Transform components create a new transformed ‘Geometry’ out of the input ‘Geometry’, as new this means is no more the model referenced geometry and it lose the ID, so when baked, the ‘Bake Content’ component did not know is referenced and can’t Update existing objects after transform.

Now the ‘Geometry’ is as any other Attribute if you need to modify it you have to assign it again.
On previous versions the term ‘Geometry’ was ambiguous it may contained attributes or not, now it’s more concise ‘Geometry’, it is as it was in V7, just geometry with no attributes.

Also, this new behavior forces ‘Model Object’ to be converted to pure Geometry and previous components that are able to handle ‘Geometry’ do work with the converted version of the ‘Model Object’ while the previous implementation forces to update all the existing ‘Geometry’ aware components to work like ‘Area’ is doing here. And this includes all third party components that we do not control.

1 Like

Thanks @kike for the detailed explanation. That makes sense and I’ll update accordingly!