[Bf-committers] Degrees, radians, and drivers
hadriscus at gmail.com
Thu Feb 20 00:46:34 CET 2014
At first that seemed like a clever idea but I guess you'd expect someone
who's manipulating drivers to know about the radian thing, therefore not
bothering with an additional conversion. In the end I guess Campbell is
right and it's a documentation issue. Thanks for adding that section !
On 19 February 2014 23:23, patrick boelens <p_boelens at msn.com> wrote:
> I think Hadrien makes a good point though; not everyone is familiar enough
> with radians to feel comfortable using them. I'm not sure how practical/
> user friendly this would be, but would an F-Curve "Degrees-to-Radians"
> modifier be a possible solution? That way the artist can still think in
> terms of degrees, and Blender could still be using radians everywhere
> > Date: Thu, 20 Feb 2014 08:50:05 +1100
> > From: ideasman42 at gmail.com
> > To: bf-committers at blender.org
> > Subject: Re: [Bf-committers] Degrees, radians, and drivers
> > On Thu, Feb 20, 2014 at 1:20 AM, Hadrien Brissaud <hadriscus at gmail.com>
> > > The variable's current value is in fact clearly displayed both in deg
> > > rad in the graph editor, it's just a behaviour I didn't expect, not
> > > particularly hefty at math. Maybe it should be pointed out more
> > > in the interface, or in the chapter about drivers in the doc. Is
> > > permanently making the unit drivers use to be degrees out of the
> > > too ?
> > Yep, trigonometry functions from Python's math module expect radians.
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers