Bezier curve show as Constant #71650
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#71650
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?
System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63
Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-13 16:25, hash:
9bd0d8b550Worked: (optional)
Short description of error
Bezier curve show as Constant
Переход кадра.blend
Added subscriber: @cheteron
Added subscriber: @lichtwerk
There is indeed something weird going on [not really sure what exactly is going on], regarding the "normalized" display...
[at first sight these keyframes are all at zero? so might be a rounding issue when normalizing tiny values?]
Added subscriber: @ErickNyanduKabongo
I have seen some glitch like this before when i zoom really deep, the curve sometimes becomes weird. In your file if you selected everything and do to the interpolation bezier one more time it works well.
Added subscriber: @ZedDB
behaviour changed in
edb3b7a323btw.CC @ZedDB
I can take a look at this later, I don't have time right now.
Added subscriber: @dr.sybren
Changed status from 'Confirmed' to: 'Archived'
This is just the limitation of floating point operations in a computer. Zooming in very far or using normalisation makes it less visible that the keyframe was actually at Y=0.0000000187. The report basically says that there aren't enough steps between 0.0000000000 and 0.0000000187.
Seriously? 2019 end, and this glitch, can't you optimize it to display correctly?
The thing is, with floating point precision the way it is, the graph might actually properly show the values as they are applied over time. Blender works with
floatvalues, and the smallest number that can be represented is in the order of magnitude of 0.0000000187. This means that there are no possible numbers between 0.0 and 0.0000000187, and the constant interpolation is actually correctly representing what's happening.What about u talk? What 0.000000187, if there value between ~0.4 and ~0.6???
Round the value and make a normal display. Stop justifying the glitch. For almost every blender flaw - this is normal, instead of fixing and making user-friendly