I am using Blender v2.74.
I am working with two .blend files. The main assembly .blend and a separate subassemblies .blend file. As it turns out, the two files are at two different scales. The subassemblies .blend is at 1/10 that of the main assembly file. I linked a subassembly of parths from the subassemblies file. In order to translate, rotate and scale the subassembly, I converted the links to proxies. When I do this, the edge-split modifier on the proxied parts loses its effect, and the smoothing result is not acceptable.
What I've tried
Since all the parts in the subassembly are children of on of the parts there-within, and since I was able to effectively convert its link to a proxy (with the disastrous effects) and have all its children follow the translation, rotation, scale I provided this parent, it made sense that if I were to make this parent part a child to an empty in the subassemblies file, I should be able to convert the link to it in the main assembly file to a proxy, and use it to translate, rotate and scale its children.
When I tried that, it enables me to translate, rotate, and scale the empty, but when I do, none of it's children respond appropriately as they did when their parent object (not the empty) is converted to a proxy and translated, rotated or scales.
The meat and potatoes of the question(s)
- Why is this happening? Why is it that when I convert a link to a proxy, it seems to ignore its edge-split modifier, even though the modifier remains in the stack?
- Why wont the parents follow their empty parent? Why does a relationship to a physical object allow for children following the translation, rotation and scale of their parent, whereas; one to an empty does not?
- How do I get to work? How do I either re-enforce the edge-split modifier on the proxy, or re-enforce the relationship between the parent empty and the child objects?
In the meantime, I'll keep playing and hopefully solve my problem. If I do, I shall, of course, post it here.
Yes, I know
In anticipation of some comments or answers suggesting I simply change the scale of either file: I have thought of that, and while it would solve the scaling issue, it does nothing to resolve the translation and rotation issue coupled with the ghastly lack of proper edge-splitting.