[Bf-animsys] Does anybody really use (and like) Copy Scale with Offset?

Juan Pablo Bouza jpbouza at hotmail.com
Sun Mar 4 16:44:42 CET 2018


I have that option in use for some very specific cases in my rig, like when I need a bone to inherit Loc and Rot from the parent bone, but scale from another bone. Therefore, I use the copy scale option to inherit scale from another bone (in pose or world space), but as I also want to be able to manually scale the bone, I use the offset option. Of course, I also have to turn off the inherit scale option in the bone, otherwise the offset option in world space makes the bone inherit the scale from all the bones that go up the hierarchy.


Anyway, that's how I use it, but as Ton said in an interview, at some point in the near future, the Animation 2020 project will start and If the plan is to replace the constraint system with nodes, maybe it doesn't make much sense to go changing things right now. Sometimes undesired behaviors for some users might be desired behaviors for others. The node system might be the answer for many issues that we have right now 😊

________________________________
De: Bf-animsys <bf-animsys-bounces at blender.org> en nombre de Nathan Vegdahl <nathanvegdahl at gmail.com>
Enviado: domingo, 04 de marzo de 2018 12:13 a.m.
Para: Discussion list to assist animation developers
Asunto: Re: [Bf-animsys] Does anybody really use (and like) Copy Scale with Offset?

Personally, I don't think I've ever used the Offset option on any of
the constraints.  I always use an extra bone and parenting for such
cases.  But I may be weird in that respect...

--Nathan

On Fri, Mar 2, 2018 at 11:30 PM, Alexander Gavrilov
<angavrilov at gmail.com> wrote:
> Hi,
>
> As implemented, Copy Scale with the Offset option for some reason
> _adds_ the scales together like with rotation and location, which
> makes no sense because scale is a multiplicative quantity. This
> means that properly combining scales can only be done with multiple
> bones and parenting, while the constraint is useless.
>
> I think 2.8 may be a good opportunity to break strict backward
> compatibility and fix this historical problem.
>
> Alexander
>
>
> _______________________________________________
> Bf-animsys mailing list
> Bf-animsys at blender.org
> https://lists.blender.org/mailman/listinfo/bf-animsys
Bf-animsys Info Page - Blender<https://lists.blender.org/mailman/listinfo/bf-animsys>
lists.blender.org
To see the collection of prior postings to the list, visit the Bf-animsys Archives. Using Bf-animsys: To post a message to all the list members, send ...


_______________________________________________
Bf-animsys mailing list
Bf-animsys at blender.org
https://lists.blender.org/mailman/listinfo/bf-animsys
Bf-animsys Info Page - Blender<https://lists.blender.org/mailman/listinfo/bf-animsys>
lists.blender.org
To see the collection of prior postings to the list, visit the Bf-animsys Archives. Using Bf-animsys: To post a message to all the list members, send ...


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.blender.org/pipermail/bf-animsys/attachments/20180304/49db63e4/attachment.html>


More information about the Bf-animsys mailing list