Unintended GH geometry param data persistence after new blank rhino file

I have a “new” behavior of Rhino and I don’t know if this is a “new feature” or a bug.

If a Grasshopper geometry container (Geometry parameter) is referencing e.g. a brep in an opened Rhino file and I load a “new” Rhino file while keeping the grasshopper definition open then:

  • container doesn’t change to orange
  • container data “persists”
  • everything connected keeps on working as if nothing changed

Anybody knows what’s going on?

Rhino
Version 6 SR35
(6.35.21222.17001, 08/10/2021)

moved to grasshopper category

1 Like

The canvas hasn’t recalculated (play button) or the geometry was internalized (right click on components to internalize) and is now in the GH document.

Container is not internalized.

The recompute works again (had to restart my machine).

However, I usually have the solver enabled. For a very long time, for me the solver was always triggered if a “reference” to a geometry suddenly doesn’t exist. This is a definite behavior change for me.
Did you never experience that?

The solver runs on these events primarily

Some components/plugins referencing external objects require a ‘Play’ to refresh.

I recognize those indeed, although this is the trigger list for autosave. I have a new behavior regarding the solver and will definitely confuse users of our tool.

Strange enough, if I load another Rhino file (so not a blank “New” file) then the container does get triggered.

I’m going to switch this to the Grasshopper Developer category.

1 Like