keyframe interpolation "Elastic" always starts down on the Y-Axis #85433

Closed
opened 2021-02-06 18:55:27 +01:00 by tt · 7 comments

System Information
Operating system: Linux-5.4.0-65-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04

Blender Version
Broken: version: 2.92.0 Beta, branch: master, commit date: 2021-01-31 13:31, hash: a9b53daf23
Worked: (newest version of Blender that worked as expected)

Short description of error
when having two keyframes and setting the interpolation of the first one to elastic the curve always goes down on the Y- Axis first.
This leads to having to add another keyframe like this:
grapheditor elastic.jpg
Maybe I am missing something and this is not a bug, but setting the Amplitude of the elastic interpolation to a negative value is where I would flip that behaviour, but the amplitude is limited to positive values only. Allowing negative values for the amplitude would fix this.

Exact steps for others to reproduce the error
Add 2 keyframes to cube, set interpolation of the first keframe to elastic, try to flip the elastic curve to start upwards bound on the Y-Axis...

**System Information** Operating system: Linux-5.4.0-65-generic-x86_64-with-debian-bullseye-sid 64 Bits Graphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04 **Blender Version** Broken: version: 2.92.0 Beta, branch: master, commit date: 2021-01-31 13:31, hash: `a9b53daf23` Worked: (newest version of Blender that worked as expected) **Short description of error** when having two keyframes and setting the interpolation of the first one to elastic the curve always goes down on the Y- Axis first. This leads to having to add another keyframe like this: ![grapheditor elastic.jpg](https://archive.blender.org/developer/F9674300/grapheditor_elastic.jpg) Maybe I am missing something and this is not a bug, but setting the Amplitude of the elastic interpolation to a negative value is where I would flip that behaviour, but the amplitude is limited to positive values only. Allowing negative values for the amplitude would fix this. **Exact steps for others to reproduce the error** Add 2 keyframes to cube, set interpolation of the first keframe to elastic, try to flip the elastic curve to start upwards bound on the Y-Axis...
Author

Added subscriber: @ToxicTuba

Added subscriber: @ToxicTuba
Member

Added subscriber: @filedescriptor

Added subscriber: @filedescriptor
Member

I believe what you want to adjust is the Period. If you just flip the sign it will flip the direction.
image.png
image.png

I believe what you want to adjust is the *Period*. If you just flip the sign it will flip the direction. ![image.png](https://archive.blender.org/developer/F9748198/image.png) ![image.png](https://archive.blender.org/developer/F9748208/image.png)
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Author

indeed this solves this issue. Somehow I figured it has to be the amplitude that needs to be flipped, scaling down the period seems counter intuitive, as in my mind it would flip the curve along the x axis and the elastic interpolation always starts at the keyframe and goes on to the right and there is nothing to the left of it where that flipped period would appear in a maths graph when manipulating the x expansion, but in a keyframe editor it kind of makes sense...
scaling the amplitude seemed more intuitive as it was manipulating the y axis already... can't we have negative values on both amplitude and period?

indeed this solves this issue. Somehow I figured it has to be the amplitude that needs to be flipped, scaling down the period seems counter intuitive, as in my mind it would flip the curve along the x axis and the elastic interpolation always starts at the keyframe and goes on to the right and there is nothing to the left of it where that flipped period would appear in a maths graph when manipulating the x expansion, but in a keyframe editor it kind of makes sense... scaling the amplitude seemed more intuitive as it was manipulating the y axis already... can't we have negative values on both amplitude and period?
Member

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
Member

I am not sure about the negative amplitude. Usually, it's an absolute value. "The amplitude is the amount of the maximum deflection in the 𝑦 direction". This would have to be discussed with the UI team.

Closing this for now since it's not a bug.

I am not sure about the negative amplitude. Usually, it's an absolute value. "The amplitude is the amount of the maximum deflection in the 𝑦 direction". This would have to be discussed with the UI team. Closing this for now since it's not a bug.
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
2 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#85433
No description provided.