Testing different ways of LINKING assets that have Geometry Node Based adjustabililty

[thinsoldier]

Setup #1

\3DAssets\archive3d.net\Luster N181120\Luster N181120.blend

Linking this gives an object that cannot be moved or configured without first creating a Library Override on the Object level (Don’t forget to also clear the Asset mark after doing that.)

Only that one object appears in the Outliner.
The mesh data is LINKED.
The Geometry Node group is LINKED but can be interacted iwth.

The various objects that are combined to make the asset are nowhere to be seen in the Blend File.

Even the Light Object “Point Light Customized” does not appear anywhere.

As before, the size of the point lights don’t scale up with the rest of the object.

So to use the asset in a very different scenario I need to be able to replace the original light in the asset with a custom one from the current scene file.

I can add a custom light to this scene, hide it out of the way somewhere, and use it with the Geometry Node settings.

[thinsoldier]

Setup #2

\3DAssets\archive3d.net\Luster N181120\Luster N181120.blend

Same asset as before but Appending this time.

Miserable messy failure. Every object that is a component of the asset gets appended.

[thinsoldier]

Setup #3

Just the Geometry Nodes node group itself linked to the default cube of the main scene file.

It worked as cleanly as Setup #1 , but the point light is missing.
This is understandable since the light object to use is defined in the source file on the object level in the Geometry Nodes modifier of an object.

If the point light to use was defined in the node network itself or in the default value of the node group settings it likely would have been appended or linked to this test file and appeared, undesirably, in the outliner. I should test that assumption next.