Page MenuHome

Bezier curve show as Constant
Closed, InvalidPublic

Description

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: rB9bd0d8b5505a
Worked: (optional)

Short description of error
Bezier curve show as Constant

Event Timeline

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?]

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.

Philipp Oeser (lichtwerk) lowered the priority of this task from 90 to 50.Nov 18 2019, 12:48 PM

behaviour changed in rBedb3b7a323a1 btw.

CC @Sebastian Parborg (zeddb)

I can take a look at this later, I don't have time right now.

Sybren A. Stüvel (sybren) claimed this task.

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 float values, 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