We've been using keyable parameters on Justin's production<http://www.justinandtheknightsofvalour.com>without issues. Of course we had to develop some tools to create/manage 'selection groups' and make life easier for the animation crew, but nothing to fancy to be worried about.
On Fri, Jan 11, 2013 at 9:45 AM, Enrique Caballero < [email protected]> wrote: > Hey everyone, > I need some advice. I am considering dropping the use of Marking Sets > in our pipeline. > > The reason for this is that with Keyable Parameters I don't really see > much of a point for using Marking Sets anymore. > > Marking sets also give me the unfortunate side effect of showing duplicate > Fcurves in the Fcurve editor, one for the master parameter and another for > the proxy param on the marking set. Also we use DisplayInfo as well and > that makes 2 proxy parameters and 1 master parameter. Basically just a > bunch of clutter. > > I'm giving this a lot of thought before I move on it, and I'm keenly > interested in what your guy's view is on this. > > The only current benefit that I can see from marking sets over keyable > parameters is that marking sets are really easy to find via scripting, i > just do a search for a Property("MarkingSet") > > But its not really much more work to find all Keyable parameters. > > Anyway please tell me your views. I would really appreciate it > > -Enrique >
