- Fri May 25, 2007 1:22 pm
#227746
Some people find it easier to work with embedded materials, others prefer to reference MXM files on disk. Embedded materials have some advantages like the texturing stuff you mentioned and also that the scene is autonomous (no headaches when you move it to another computer and you discover that the paths don't match anymore).
The referenced model also has some strengths, like the ability to share materials. With this model, when a MXM file is updated, you don't need to touch any of the scenes that use it (you will need to re-render them, of course :) ).
Since the plug-in was rewritten from scratch, we have focused on the challenging features first as they impose more restrictions to the way the plug-in will develop in the future. The embedded material requires way more code and tricks than the referenced version and we wanted to make sure it's working first. We'll add referenced materials in a future update.
The referenced model also has some strengths, like the ability to share materials. With this model, when a MXM file is updated, you don't need to touch any of the scenes that use it (you will need to re-render them, of course :) ).
Since the plug-in was rewritten from scratch, we have focused on the challenging features first as they impose more restrictions to the way the plug-in will develop in the future. The embedded material requires way more code and tricks than the referenced version and we wanted to make sure it's working first. We'll add referenced materials in a future update.