cousin it
03-04-2005, 10:45 PM
This could be a bit longish, but here goes. I've noticed that messiah and Max don't always understand one another fully. Here's where it went wrong for me. I'd created a linked Max-scene, with one mesh driven by and imported from messiah. This was a 'cage' object, which in messiah i'd tab, in Max, I'd slap a Meshsmooth or Turbosmooth modifier on. Everything was going swimmingly, until I saved the scene and decided to do a network render.
My mesh didn't quite look the same, so I opened the scene again, hit the gui button on the messiah deform modifier and found that my character had imploded into a spikey kind of thing, though in setup it looked fine. Too fine, actually, since it didn't change back into the cage, however much I hit the tab button.
Apparently, at the time of loading up the mesh data messiah's supposed to link to, the messiah deform plugin passes on the entire stack of modifiers to messiah, meshsmooth included, instead of only the ones sitting below it.
I've managed to work around this behavior, but was wondering if anybody else noticed this and if something could be done to remedy this?
My mesh didn't quite look the same, so I opened the scene again, hit the gui button on the messiah deform modifier and found that my character had imploded into a spikey kind of thing, though in setup it looked fine. Too fine, actually, since it didn't change back into the cage, however much I hit the tab button.
Apparently, at the time of loading up the mesh data messiah's supposed to link to, the messiah deform plugin passes on the entire stack of modifiers to messiah, meshsmooth included, instead of only the ones sitting below it.
I've managed to work around this behavior, but was wondering if anybody else noticed this and if something could be done to remedy this?