file based modularisation
I am using blender 2.8+ mainly for technical projects. I find the scene collection very useful to maintain order for complex parts.
Now, I thought about having an "include" function.
I give an example: In the scene collection, I can add a new collection, and build a tree like structure here. OK.
What if I could add another element type here, an "include" type, with 2 parameters: 1) a (relative) file path/name to another blend file 2) a prefix. The behaviour would be to include all data from that other blender file with the prefix added to any element / object there. (A behaviour similar to a namespace) And maybe 3) A filter definition that specifies what should be "included"
Maybe, that way, it would be possible, for example, to have one blender file with a material collection ... Maybe it would give a different way to reuse things ... Maybe it would give a different way to collaborate ...
Just an idea. I assume this Idea it appearing similarly in many variations.
Another thought to approach this: A simple "workaroud" to get this behaviour would be a script like "uodate content from ...".
2 Comments
Unless I'm missing something, this is exactly what "Link" and "Append" do
Needs better explaination.