[Bf-animsys] Visualisation Matters

[joe]

That's no reason not to implement the feature.  Truthfully, that's
something that can and will happen fairly easily anyway.  It's not
like it's really preventable, especially the performance problems.

Joe

On Fri, Aug 14, 2009 at 5:48 AM, Gianmichele
Mariani<g.mariani at liquidnet.it> wrote:
> I have to agree that there are a lot of different workflows (I consider mine
> always evolving) and probably some kind of option that will let you choose
> if you want to see actual previous/next N frames or keyframes should be in
> place.
>
> My only concern is that viewport will be cluttered really soon and
> performance crawl down.
>
> Keep us informed on your work :D
>
> Gian
>
> On Fri, Aug 14, 2009 at 8:27 AM, joe <joeedh at gmail.com> wrote:
>>
>> On Fri, Aug 14, 2009 at 1:15 AM, Gianmichele
>> Mariani<g.mariani at liquidnet.it> wrote:
>> > About ghosting, or as it's called in the 2d arena, onion skinning, it is
>> > used mainly during the construction of a pose and in the
>> > blocking/breakdown
>> > definition phase. As a result I think the the only ability should be to
>> > visualize the previous and next keyframe (not frame). That is why should
>> > be
>> > on the actual mesh and not on bones or other things (I still don't know
>> > how
>> > one can use only the armature to pose a character).
>>
>> Eh that's kindof an authoritative statement.  There's a fair number of
>> different animation workflows, and I imagine many people would hate
>> working that way.  I certainly would, I use ghosting to detect spacing
>> problems, which certainly wouldn't work if you could only see the
>> previous/next keyframe.
>>
>> Joe
>> _______________________________________________
>> Bf-animsys mailing list
>> Bf-animsys at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-animsys
>>
>
>
> _______________________________________________
> Bf-animsys mailing list
> Bf-animsys at blender.org
> http://lists.blender.org/mailman/listinfo/bf-animsys
>
>