Yeah, there's some serious issues with merging animation layers. We experienced very frequent crashes and extreme slowness, just as you did. We were able to at least prevent the crashing by baking the animation layers using our own command - and the key there is to use the "simulation" flag when calling bakeResults. My guess is that this makes a difference because if you don't, maya tries to merge all the frames "at once", and runs out of memory, while simulation mode does it frame by frame, freeing up memory as it goes... Just a hunch, though. Regardless, the underlying call made when you do a merge layers through the GUI doesn't use "simulation", so I recommend avoiding that when baking.
- Paul On Tue, Jun 29, 2010 at 1:32 AM, Mark Jackson <[email protected]> wrote: > Yes, were running layers in production, whilst the animators like it, we > have had some issues. If you're using 2010 and characterSets there was an > issue that Maya would disconnect the characterSet from it's members, > breaking any referencing.... thankfully this is fixed in 2011. > > Also it's painfully difficult and slow to get rig of layers once you've used > them. For a large scale cutscene, say 4000frms of baked moCap, it can take > 20minutes to merge layers down, if it even manages it before crashing. I > don't understand how they could have got this process SOOOOOOO slow. If you > do the same kind of dense data operation on multiple Trax it takes seconds. > > > > On 25 June 2010 20:37, ynedelin <[email protected]> wrote: >> >> Animation layers and custom attributes? >> >> Has anyone used animation layer in production? >> >> We are on Maya 2010 and running into bugs. >> >> For example animation layers do not seem to like custom attributes. >> >> Also animation does not get refreshed if there is not actual animation >> curves at the given frame. >> >> Yury >> >> >> >> -- >> http://groups.google.com/group/python_inside_maya > > -- > http://groups.google.com/group/python_inside_maya -- http://groups.google.com/group/python_inside_maya
