Camera Location, keyframe Bug #58739

New Issue

Philip · 2018-12-04T21:40:30+01:00

Philip commented

2018-12-04 21:40:30 +01:00

System Information
Operating system: Win 10 64 bit
Graphics card: 2xGTX 1080 Ti

Blender Version
Broken:
2.80, 2018-12-03, a205493426
Worked: (optional)

Short description of error
When camera location keyframed beyond timeline(or sometimes in) can't change keyframed values from 1st keyframe.

Exact steps for others to reproduce the error
Create camera, set view to camera, add keyframe, change position on timeline, move camera in location tab - its looking like view is still only outframe of camera is moving and changing visual od depth. After release for ex OY location it will back to value from first keyframe. If description will be not enough I can provide video.

**System Information** Operating system: Win 10 64 bit Graphics card: 2xGTX 1080 Ti **Blender Version** Broken: 2.80, 2018-12-03, a205493426b Worked: (optional) **Short description of error** When camera location keyframed beyond timeline(or sometimes in) can't change keyframed values from 1st keyframe. **Exact steps for others to reproduce the error** Create camera, set view to camera, add keyframe, change position on timeline, move camera in location tab - its looking like view is still only outframe of camera is moving and changing visual od depth. After release for ex OY location it will back to value from first keyframe. If description will be not enough I can provide video.

Philip commented

2018-12-04 21:40:30 +01:00

Added subscriber: @DrPhil

blender-admin commented

2018-12-04 21:40:30 +01:00

#60318 was marked as duplicate of this issue

blender-admin commented

2018-12-04 21:40:30 +01:00

#58241 was marked as duplicate of this issue

blender-admin commented

2018-12-04 21:40:30 +01:00

#58725 was marked as duplicate of this issue

Sebastian Parborg commented

2018-12-05 11:16:28 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2018-12-05 11:16:28 +01:00

I can not reproduce this issue. All location values does not seem to reset to previous value (unless the timeline is changed).

Philip commented

2018-12-05 11:25:11 +01:00

I will attach link with video:

https://drive.google.com/open?id=1e8n_MVjLIDVREjyKuzeGRPk_iln0qU3f

I will attach link with video: https://drive.google.com/open?id=1e8n_MVjLIDVREjyKuzeGRPk_iln0qU3f

Sebastian Parborg commented

2018-12-05 12:14:40 +01:00

Is this still a problem for you if you switch to solid mode? Perhaps it's a problem with the rendered view.

However, I still have a hard time to reproduce this issue on my side (I'm on linux and built blender from git).
I'm trying to reproduce this issue with the default blender cube scene and I'm having no luck with that.

It would be really helpful if you could create a minimal blend file that have the issue and upload it here.

Is this still a problem for you if you switch to solid mode? Perhaps it's a problem with the rendered view. However, I still have a hard time to reproduce this issue on my side (I'm on linux and built blender from git). I'm trying to reproduce this issue with the default blender cube scene and I'm having no luck with that. It would be really helpful if you could create a minimal blend file that have the issue and upload it here.

Philip commented

2018-12-05 13:17:30 +01:00

camera_bug.blend

Here is a file - try to change OY and keyframe it while in view to camera

[camera_bug.blend](https://archive.blender.org/developer/F5833423/camera_bug.blend) Here is a file - try to change OY and keyframe it while in view to camera

Sebastian Parborg commented

2018-12-05 15:23:08 +01:00

I can reproduce the issue on my end with that file, thanks!

Sebastian Parborg commented

2018-12-05 15:58:08 +01:00

Have you tried any newer blender versions? If I open up your scene and duplicate the camera and set that one as the active camera, it does not have this problem.
I'm beginning to suspect that this issue has been solved in never 2.8 builds. But files created with older builds are still bugged.

Have you tried any newer blender versions? If I open up your scene and duplicate the camera and set that one as the active camera, it does not have this problem. I'm beginning to suspect that this issue has been solved in never 2.8 builds. But files created with older builds are still bugged.

Philip commented

2018-12-05 16:10:25 +01:00

Video I sent was from a20549342 version from 2 days ago

and file I sent was created in be91d4ef9 version that is from yesterday

Video I sent was from a20549342 version from 2 days ago and file I sent was created in be91d4ef9 version that is from yesterday

Sebastian Parborg commented

2018-12-05 16:21:15 +01:00

Does the problem still happen if you copy the camera and set the copy as the active scene camera?

Philip commented

2018-12-05 16:33:26 +01:00

Yes, it behave in same way. But if I "go out" of camera it start working properly.

Philip commented

2018-12-05 16:35:19 +01:00

Now I deleted this copied camera and again select old camera as active and now it looks like it is working properly.

Sergey Sharybin was assigned by Sebastian Parborg

2018-12-06 10:07:11 +01:00

Sebastian Parborg commented

2018-12-06 10:07:11 +01:00

According to angavrilov on IRC, this seem to be a depsgraph issue:

angavrilov | DarkDefender: right, after a brief look it seems something fishy may be happening with the AnimData->recalc flag - it's probably related to COW and depsgraph, so need to discuss with hackerman-
angavrilov | DarkDefender: basically, it seems if that flag is set on the non-COW instance, it is never cleaned up and forces animation to be re-evaluated every time
angavrilov | DarkDefender: If I clear that stuck flag from that camera object in the debugger, the bug is fixed

According to angavrilov on IRC, this seem to be a depsgraph issue: > angavrilov | DarkDefender: right, after a brief look it seems something fishy may be happening with the AnimData->recalc flag - it's probably related to COW and depsgraph, so need to discuss with hackerman- > angavrilov | DarkDefender: basically, it seems if that flag is set on the non-COW instance, it is never cleaned up and forces animation to be re-evaluated every time > angavrilov | DarkDefender: If I clear that stuck flag from that camera object in the debugger, the bug is fixed

Sergey Sharybin commented

2018-12-06 11:11:39 +01:00

Added subscribers: @angavrilov, @brecht

Sergey Sharybin commented

2018-12-06 11:11:39 +01:00

@angavrilov , why not to talk here, huh ;)

I am a strong believer in theory that AnimData->recalc flag is to be forgotten, gone and never brought back. It is kind of conflicts with granularity nature of the new dependency graph.

This is also something, i believe, we've discussed with @brecht about IDs -- they shouldn't get recalc flags set nowadays.

@angavrilov , why not to talk here, huh ;) I am a strong believer in theory that AnimData->recalc flag is to be forgotten, gone and never brought back. It is kind of conflicts with granularity nature of the new dependency graph. This is also something, i believe, we've discussed with @brecht about IDs -- they shouldn't get recalc flags set nowadays.

Sebastian Parborg commented

2018-12-07 16:45:04 +01:00

Added subscriber: @JaySchay