2
$\begingroup$

Maybe I'm overlooking something but I have a problem and don't want to screw up my files ;-)

I created my Assets for a scene in one file, put the objects into groups (each object got its own) and am then linking the group in my scene builder file.

Everything works great that far.

I now wanted to change some materials on a few of the objects that I linked, unifying them basically.

Therefore I changed the assigned material in my asset source file.

When reloading the scene builder file now I get errors corresponding to the materials changed: Lib: Material: 'InsertMaterialName' is missing from 'AssetSourceFilePath', parent ''

So it seems to still point to the old Material even though I changed it in my source file.

Does anyone know why this happens and how to fix this?

Help is greatly apprectiated.

Cheers Daniel

Edit: Removing the Materials from the scene outliner -> Blender File -> mySourceAssetFile.blend removes the errors. Though I really would like to know where this error comes from and how to "really" fix it!

$\endgroup$
1
$\begingroup$

This is normal behavior and expected as far as I know.

The destination file where you linked from saves both the group you linked to along with the data contained in that group. That means objects, materials, image textures, animations, particles. In doing so it saves the link to said group but also a reference to the internal data.

If you change the linked file, when reopening the master those references will be missing from the group, and hence the warning you get. This is however expected, and if you save the master file, close blender and reopen, the broken references should be gone and so should the warning too.

$\endgroup$
  • $\begingroup$ Hey thanks for your reply! I can see that this might be expected bevahior. Though from a non technical standpoint it is weird behavior as Ilinked something that got changed in its own file and reloaded in the master file where it outputs an error. But O.K. Blender is rather technical sometimes and it might make sense for someone else ;-) What I don't understand though and what fixed the problem as you said: You have to close and reopen Blender. Simply reopening the maste file doesn't do the trick. Which is really weird if it was expected behavior :) But thanks! It is working now! $\endgroup$ – Daniel Friedenberger Oct 10 '17 at 12:44
  • $\begingroup$ That has to do with blender philosophy of keeping erased data around until you close it, so it can be recovered from accidental deletion. Closing and reopening clears it. It is one of those arcane things that are planned to change for future 2.8 versions. $\endgroup$ – Duarte Farrajota Ramos Oct 10 '17 at 13:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.