Exponential easing/interpolation might be incorrect #50011
Labels
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#50011
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
blender 2.78a
Linux bubastis 4.0.5-gentoo #1 SMP Mon Nov 16 11:48:34 EST 2015 x86_64 Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz GenuineIntel GNU/Linux
I created an fcurve with two keyframes: (1,1) and (100,1024) When I zoom in on the curve it appears to jump from (1,1) to (2,2) before resuming an exponential track. I would have assumed it didn't reach a y of 2 until keyframe 10 or 11.
In any case, this discontinuity in the first frame after the keyframe seems incorrect.
Changed status to: 'Open'
Added subscriber: @mutantbob
Added subscribers: @JoshuaLeung, @brecht
Confirmed: exponential_discontinuity.blend.
I guess this is one for @aligorith.
This is very strange...
A while back, I spent some time investigating this issue. I went and double-checked whether the implementations of the easing equations were were using were correct - I went as far as copying the code out of one of the reference implementations, making the relevant adjustments, and trying again.
While there are some slight errors I picked up this way (affecting other cases), ultimately they didn't seem to be related to what we're seeing here. The code used to calculate these curves is practically the same as is used everywhere.
The main point of different I suppose is that we stick to the 0-1 range (on both the x and y axes), and then try to scale up the y-range to accomodate the amount of change between the keyframes. My current best guess is that this is a numeric precision error/discontinuity in the exp function that might not show up if we weren't trying to scale things up by using only the 0-1 range. If anyone has any better suggestions about what we could try here, patches are welcome :)
Added subscriber: @dr.sybren
Changed status from 'Open' to: 'Resolved'
Closing, as this doesn't seem to be an issue any more.