1
$\begingroup$

Say I have an instanced model (duplicated with alt+D) and I add a meshcache modifier with a .mdd or .pc2 file loading a different version of the model. Will this break the instancing and cause it to count as a different model for memory usage in rendering?

How about different shapekeys on instanced models?

How about modifiers that actually change the number of verts, like boolean or solidify?

$\endgroup$
  • $\begingroup$ This seems a bit of an odd question, why would it break? $\endgroup$ – ideasman42 Mar 11 '16 at 0:59
  • $\begingroup$ I'm not sure. If it's the same object, but the vertices are re-ordered, is that still the same object? I'm pretty sure some modifiers break it, like boolean and solidify. $\endgroup$ – Drudge Mar 11 '16 at 1:04
  • $\begingroup$ The question doesn't mention boolean-modifier - suggest to ask edit it to make it more spesific. $\endgroup$ – ideasman42 Mar 11 '16 at 3:39
  • $\begingroup$ Good call. Updated it. $\endgroup$ – Drudge Mar 11 '16 at 3:41
1
$\begingroup$

Duplicating mesh data won't change its vertex order, so to answer your first question - yes this is supported.

As for destructive modifiers (boolean, decimate, build... etc). These will change vertex count and order, not for the mesh-datablock, only within the modifier stack. So destructive modifiers must be applied after Mesh-Cache modifier, for this to work as expected.

$\endgroup$

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.