replacing materials from material library, with distance tex associations makes a right mess of my scenes

[super gnu]

ive got a few near identical scenes.. needed to propagate a few material tweaks from one to the others..

saved out tweaked materials to library

brought into scene and did "put to scene"


instead of asking me if i would like to reparent the distance tex to an object in scene with same name, it just brings in a copy of the object... that object happens to be linked to another object with a lookat constraint, so it brings in a copy of that too.. that object is linked to a path, so it brings in a copy of that too... all with identical names to original... links get screwed.. trying to find out which is original object is hard, and for some reason, deleting one of the objects deletes both.. i also have issues with objects being brought in which i can select in selection list, but not in viewport.. also the lookat seems to be broken, or does not know where to look any more. and to make matters worse, the distance tex on imported material lists driver object as "deleted" despite bringing the damn thing in.

i just swapped out 5 materials, and now i have 5 broken copies of my lighting rig. wtf..

[hermit.crab]

I'm not sure I understood correctly, could you record a video reproduction of the issue?

[super gnu]

im 2 days away from a deadline so its unlikely i will have time, but basically if you merge a material into a scene, which has a distance tex in it, it somehow brings in the geometry that the distance tex references..

[hermit.crab]

It does indeed bring up the geometry when loading the material a material library through a .max file, however, it is linked and only occurs on the initial library loading from what I tested. How would you imagine the behavior?