Graph Editor generator for angles works in Radians while the graph editor displays the result in degrees. #62238

Open
opened 2019-03-06 05:23:11 +01:00 by Alaska · 11 comments
Member

System Information:
N/A

Blender Version
Broken: Blender 2.80 Beta (18e5540a48) and Blender 2.79 (e290a0b056)

Short description of error:
If you use the "generator" modifier in the graph editor for an angle, the generator will work in radians while the graph editor will display the output in degrees.

Exact steps for others to reproduce the error

  1. Open the startup file.
  2. Select the default cube and key frame one of the rotational axis.
  3. Open a graph editor and give the "key framed rotation" an "generator" modifier.
  4. When entering values into the modifier such as 0 and 1 so your polynomial is y=x, the result shown on the graph editor is y=57.3x. This is because the values input to the generator is read as radians while the scale in the graph editor is read in degrees.

Screenshot from 2020-05-17 17-11-35.png

**System Information:** N/A **Blender Version** Broken: Blender 2.80 Beta (18e5540a48b6) and Blender 2.79 (e290a0b0568e) **Short description of error:** If you use the "generator" modifier in the graph editor for an angle, the generator will work in radians while the graph editor will display the output in degrees. **Exact steps for others to reproduce the error** 1. Open the startup file. 2. Select the default cube and key frame one of the rotational axis. 3. Open a graph editor and give the "key framed rotation" an "generator" modifier. 4. When entering values into the modifier such as 0 and 1 so your polynomial is y=x, the result shown on the graph editor is y=57.3x. This is because the values input to the generator is read as radians while the scale in the graph editor is read in degrees. ![Screenshot from 2020-05-17 17-11-35.png](https://archive.blender.org/developer/F8539706/Screenshot_from_2020-05-17_17-11-35.png)
Author
Member

Added subscriber: @Alaska

Added subscriber: @Alaska
Joshua Leung was assigned by Sebastian Parborg 2019-03-06 10:57:21 +01:00

Added subscriber: @schweppie

Added subscriber: @schweppie

I've made a patch: D4458

I've made a patch: [D4458](https://archive.blender.org/developer/D4458)

Ah.. just after making the D4458 patch I noticed the assignment @JoshuaLeung

Ah.. just after making the [D4458](https://archive.blender.org/developer/D4458) patch I noticed the assignment @JoshuaLeung
Member

From discussions with various people over the years, we've all consistently come to the conclusion that all of these things should always be evaluated in radians only, since that's technically how Blender stores + uses all rotation values internally, and it's also what all the math/trig functions in every standard math library work.

It is only for user convenience that we set the "display units" to degrees, to make it easier for artists to use. Technically, everything is really getting evaluated/interpreted in radians everywhere. In the graph editor, we usually apply some conversions to map between the two as necessary when dealing with rotation curves. Perhaps this case is getting skipped when doing the display unit adjustments when drawing the curve, but I'd have to check carefully to know.

From discussions with various people over the years, we've all consistently come to the conclusion that all of these things should always be evaluated in radians only, since that's technically how Blender stores + uses all rotation values internally, and it's also what all the math/trig functions in every standard math library work. It is only for user convenience that we set the "display units" to degrees, to make it easier for artists to use. Technically, everything is really getting evaluated/interpreted in radians everywhere. In the graph editor, we usually apply some conversions to map between the two as necessary when dealing with rotation curves. Perhaps this case is getting skipped when doing the display unit adjustments when drawing the curve, but I'd have to check carefully to know.
Joshua Leung was unassigned by Dalai Felinto 2019-12-23 16:34:57 +01:00

Added subscriber: @JoshuaLeung

Added subscriber: @JoshuaLeung
Author
Member

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren
Author
Member

@dr.sybren Do you believe this could be added to the "quick hacks" project? Or is it too complex? Or is this more of a design task.

@dr.sybren Do you believe this could be added to the "quick hacks" project? Or is it too complex? Or is this more of a design task.

@Alaska I can't really tell, it's a UI interface issue and I'm not familiar with the C UI code. It could be fairly simple to let the UI code determine that the FCurve represents an angular value, but then again it may not be.

@Alaska I can't really tell, it's a UI interface issue and I'm not familiar with the C UI code. It could be fairly simple to let the UI code determine that the FCurve represents an angular value, but then again it may not be.

Added subscriber: @hatinacat2000

Added subscriber: @hatinacat2000

I've been using 2.82 for a while and I have a bachelors in math. I love radians...when they are written as FRACTIONS.
Nobody knows what the hell these values are in decimals so it REALLY messes up our animation workflow to reverse-engineer stored angles when we need to make changes. Regardless of how these angles are stored internally, they should be displayed in degrees. At the very least, we should be able to enter new values in degrees.

I've been using 2.82 for a while and I have a bachelors in math. I love radians...when they are written as FRACTIONS. Nobody knows what the hell these values are in decimals so it REALLY messes up our animation workflow to reverse-engineer stored angles when we need to make changes. Regardless of how these angles are stored internally, they should be displayed in degrees. At the very least, we should be able to enter new values in degrees.
Philipp Oeser removed the
Interest
Animation & Rigging
label 2023-02-09 14:36:42 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#62238
No description provided.