Jeffrey Dates wrote:
But yes point cache is great! But a couple of questions about
non-linear workflow with them.
If build a rig and proxy geo, and hand it off to the animator to start
blocking in motion, before the model is complete. Is There is no easy
way to propagate modeling changes across many animated scenes without
re-caching, and re-importing for each??
Hey Jeff -
Maybe it would be possible (from the lighting person's side) to launch
an xsibatch -script command to regenerate all the pointcaches for a
given scene and have that stuff relinked on completion. Kind of like
you "pull" the cache from the last saved scene they did. Basically the
scene could have a custom property with a string to the scene from which
it came.
But doing something like that doesn't really solve the problem I think
(it's a lame excuse not to do anything, I know). What is interesting is
that almost invariably any discussion about this points back to having
some kind of database. Every time I start thinking about this stuff it
turns in to a really big project and I wind up someplace very very far
away from the source of my original problem and that problem I had seems
symptomatic of something bigger that's rather tough to address all at
once.
Especially when all I needed to do at that particular moment was link up
some caches and start some renders so I could go home. :)
-T
--
A.K.I.T.A.: Artificial Killing and Immediate Troubleshooting Android
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
