[Eric Lagman]

I thought I would try putting some custom mxm's onto some test objects. There seems to be a signicant bug becuause some of my custom mxm tags on one object get mysteriously put onto objects that have a different custom mxm tag when it goes to render. As soon as I take the custom mxm tag off of the object that somehow acquired the wrong one and put a basic cinema tag it renders fine. So it is definately an issue with the custom tag. This makes the plugin useless for me because I usually use the power of weightmapping with maxwell materials. This is hard not to get discouraged when simple things like this don't work time and time again.

[AndreD]

Hi,
if you start a new mxm from within cinema plugin ("start material editor" with empty mxm slot), a manual export is needed to save the .mxm filename (overwrite the existing file).
Otherwise, the name stays "default" and you will mix up the materials..
Would be nice o have this bug fixed but there is a simple workaround

[Eric Lagman]

Thanks Andre. I did notice wierd things happening in the last plugin because of this. I hoped it would have been fixed by now. So when creating an custom mxm I have to give it a name and where to save to open the mat editor then re-export it from the material editor to overwrite the one it made to begin with?

[AndreD]

Hi,
you don´t have to open a new created mxm twice, nor give it a name!
Just export the mxm before closing mxed and overwrite the new created one, the name will be stored correctly.