Keyed sliders instantly jumping back #59495

New Issue

Julien Kaspar · 2018-12-17T15:09:02+01:00

Julien Kaspar commented

2018-12-17 15:09:02 +01:00

Blender VersionBroken: 2.80 9b80c70fc5bShort description of error*
The usual behaviour now when changing the values of a keyed value slider is that the sldier turns orange to indicate that the values don't match with the animation anymore. Afterwards they can be keyed or they will jump back to their keyed values once the current frame changes.
With some shapekeys this does not happen. Instead the value jumps back instantly when changed. Even with autokey the value will jump back when sliding, completely ignoring the value input.

bug_report.blend

In this file there is a cube and a plane. The plane has the above described bug. When changing the value of the keyed shapekeys this should be clear. The current cube or any new object likely will not have the bug but at some point the bug will appear.
I couldn't find out how or why.

*Blender Version**Broken: 2.80 9b80c70fc5b**Short description of error** The usual behaviour now when changing the values of a keyed value slider is that the sldier turns orange to indicate that the values don't match with the animation anymore. Afterwards they can be keyed or they will jump back to their keyed values once the current frame changes. With some shapekeys this does not happen. Instead the value jumps back instantly when changed. Even with autokey the value will jump back when sliding, completely ignoring the value input. [bug_report.blend](https://archive.blender.org/developer/F5980758/bug_report.blend) In this file there is a cube and a plane. The plane has the above described bug. When changing the value of the keyed shapekeys this should be clear. The current cube or any new object likely will not have the bug but at some point the bug will appear. I couldn't find out how or why.

Julien Kaspar commented

2018-12-17 15:09:02 +01:00

Added subscriber: @JulienKaspar

blender-admin commented

2018-12-17 15:09:02 +01:00

blender/blender#60830 was marked as duplicate of this issue

Jacques Lucke commented

2018-12-17 16:03:48 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2018-12-17 16:03:48 +01:00

I can reproduce it in this example but don't reallly understand what is happening. Were you able to reproduce it in any other file as well?

What I know is that when the value is changed, the depsgraph will be triggered and it overrides the value (twice). I don't know why changing the value of one shape key triggers the reevaluation of fcurves and changing the value of another does not.

I can reproduce it in this example but don't reallly understand what is happening. Were you able to reproduce it in any other file as well? What I know is that when the value is changed, the depsgraph will be triggered and it overrides the value (twice). I don't know why changing the value of one shape key triggers the reevaluation of fcurves and changing the value of another does not.

Julien Kaspar commented

2018-12-17 16:30:26 +01:00

@JacquesLucke At a random point while setting up the simple blend file the cube got the bug as well. Trying to reproduce it didn't work unfortunately.
I couldn't pinpoint it in other files as well.

@JacquesLucke At a random point while setting up the simple blend file the cube got the bug as well. Trying to reproduce it didn't work unfortunately. I couldn't pinpoint it in other files as well.

Jacques Lucke commented

2019-01-25 11:09:19 +01:00

Added subscribers: @HenriqueGonzaga, @WilliamReynish

Philipp Oeser commented

2019-01-25 11:33:26 +01:00

Added subscribers: @angavrilov, @mont29, @Sergey, @brecht, @lichtwerk

Philipp Oeser commented

2019-01-25 11:33:26 +01:00

The list of this phenomenom is quite worrying...
I am not sure if these all have the same roots (so atm. there are a lot of reports flying around), but this should be looked at sooner than later I think.
I tried gathering some of the reports in blender/blender#60559 (pretty sure there are others as well), but will repeat them here:
blender/blender#59904, blender/blender#59992, blender/blender#60318, blender/blender#59178, #59495, blender/blender#60598, blender/blender#60830, the list keeps growing...

@brecht, @Sergey, @angavrilov, @mont29 : have an idea?
(I dare setting this to High Priority -- even though not even assigned yet...)

The list of this phenomenom is quite worrying... I am not sure if these all have the same roots (so atm. there are a lot of reports flying around), but this should be looked at sooner than later I think. I tried gathering some of the reports in blender/blender#60559 (pretty sure there are others as well), but will repeat them here: blender/blender#59904, blender/blender#59992, blender/blender#60318, blender/blender#59178, #59495, blender/blender#60598, blender/blender#60830, the list keeps growing... @brecht, @Sergey, @angavrilov, @mont29 : have an idea? (I dare setting this to High Priority -- even though not even assigned yet...)

Sergey Sharybin commented

2019-01-25 12:16:28 +01:00

@lichtwerk, see my comment in blender/blender#59178#606785.