Alembic can save transforms and point caches, you could try with Exocortex Crate, that would help on the file size front. You could also script saving plotted global transforms on geometries which don't have and envelope or deformer and save them to a clip which you load in your rendering scene, you would need to assume that if it has an operator on the animation section of the stack then its being deformed, if its clear then it's transforming. Just be sure you keep the centers in the same place between your rigged version and your rendering version of the asset.
All of that is scriptable, with Crate I think you get that behavior out of the box. On Mon, Nov 18, 2013 at 3:31 PM, Jean-Louis Billard <[email protected]>wrote: > Yes that’s what we did previously on a model that had just a few surfaces > to cache (a mouse). > Here however we have a robot with hundreds of elements, some rigid and > some deformed, with a pretty huge geometry count. Things risk getting big > pretty quickly, so I was hoping to avoid caching unless it was strictly > necessary. > > Incidentally, what would be the best practice to cache rigid elements > (i.e. transforms only, no geometry) to avoid having large amounts of data > written out? > > > Jean-Louis > > > > > On 16 Nov 2013, at 02:57, Cesar Saez <[email protected]> wrote: > > > Or you can just cache the rigs (en everything else) before send them to > the farm... just saying :-) > > > Jean-Louis Billard > > Digital Golem > BE: +32 (0) 484 263 563 > UK: +44 (0) 7973 660 119 > [email protected] > http://www.digitalgolem.com/ > 53 Rue Gustave Huberti > 1030 Brussels > > > >
