Camera DOF distance based on an object doesn't update on animations with compositing Defocus #60961

New Issue

msalv · 2019-01-29T00:03:31+01:00

msalv commented

2019-01-29 00:03:31 +01:00

System Information
Win 10 64, nvidia 1060 6gb

Blender Version
Broken: blender-2.80.0-git.cad1016c20b5-windows64

Short description of error

Not render engine related. If you use the Defocus node in the compositor, and an animated object as the target for your camera to determine the focus distance, when you press ctrl+f12, the defocus won't animate, stuck at one distance, the one on the frame you had on the viewport before you pressed ctrl+f12. It seems the camera distance based position of the target object is not being evaluated when the animation is being composited. Animating the Distance value of the Camera directly, without an object, works though. And native eevee or cycles depth of field works with animated distance object too. This is not a huge priority or anything.

Exact steps for others to reproduce the error
Play the animation in the viewport and you'll see the distance of the camera focus does change, but render the animation with ctrl+f12 and the defocus doesn't change in the final video. Using eevee's internal depth of field or animating the distance value of the camera directly does work, and you can render that to compare.
bug9.blend

**System Information** Win 10 64, nvidia 1060 6gb **Blender Version** Broken: blender-2.80.0-git.cad1016c20b5-windows64 **Short description of error** Not render engine related. If you use the Defocus node in the compositor, and an animated object as the target for your camera to determine the focus distance, when you press ctrl+f12, the defocus won't animate, stuck at one distance, the one on the frame you had on the viewport before you pressed ctrl+f12. It seems the camera distance based position of the target object is not being evaluated when the animation is being composited. Animating the Distance value of the Camera directly, without an object, works though. And native eevee or cycles depth of field works with animated distance object too. This is not a huge priority or anything. **Exact steps for others to reproduce the error** Play the animation in the viewport and you'll see the distance of the camera focus does change, but render the animation with ctrl+f12 and the defocus doesn't change in the final video. Using eevee's internal depth of field or animating the distance value of the camera directly does work, and you can render that to compare. [bug9.blend](https://archive.blender.org/developer/F6436851/bug9.blend)

msalv commented

2019-01-29 00:03:31 +01:00

Added subscriber: @moisessalvador

blender-admin commented

2019-01-29 00:03:31 +01:00

#60804 was marked as duplicate of this issue

Philipp Oeser commented

2019-01-29 13:21:09 +01:00

Added subscriber: @lichtwerk

Philipp Oeser self-assigned this 2019-01-29 13:21:09 +01:00

Philipp Oeser commented

2019-01-29 13:21:09 +01:00

Can confirm, checking...

Brecht Van Lommel commented

2019-01-29 13:52:23 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-01-29 13:52:23 +01:00

This is basically a known issue at this point. Animation updates for render parameters and compositing are currently restricted to the scene and masks, and including objects will involve some deeper changes.

Philipp Oeser commented

2019-01-29 14:17:53 +01:00

Hm, yes, compositors ConvertDepthToRadiusOperation::determineFocalDistance calls BKE_camera_object_dof_distance (but with an unevaluated camera, no depsgraph...)
(A renderengine [e.g. Eevee] calls this, too, but has access to the evaluated camera)

While the hacks for compositing [9375c941b7, db78a8ee2e] worked [and stuff is updated for the copied scene], the compositor goes to the unevaluated camera...
(at least this is how I understand it)

One more argument for a sequencer-depsgraph, I guess...

@brecht: what to do then? Put on TODO?

Hm, yes, compositors `ConvertDepthToRadiusOperation::determineFocalDistance` calls `BKE_camera_object_dof_distance` (but with an unevaluated camera, no depsgraph...) (A renderengine [e.g. Eevee] calls this, too, but has access to the evaluated camera) While the hacks for compositing [9375c941b7, db78a8ee2e] worked [and stuff is updated for the copied scene], the compositor goes to the unevaluated camera... (at least this is how I understand it) One more argument for a sequencer-depsgraph, I guess... @brecht: what to do then? Put on TODO?

Brecht Van Lommel commented

2019-03-01 03:46:59 +01:00

Added subscribers: @matt_satch, @WilliamReynish

Philipp Oeser removed their assignment 2019-05-03 14:06:54 +02:00

Philipp Oeser commented

2019-05-03 14:06:54 +02:00

Since I wouldnt know how to proceed with this, stepping down...

Brecht Van Lommel commented

2019-05-23 16:45:20 +02:00

Added subscriber: @Sergey

Brecht Van Lommel commented

2019-05-23 16:45:20 +02:00

@Sergey, this bug is still happening after b432209f63.

Seems the empty use to control the distance is not made part of the graph.

find_node component: Could not find ID OBEmpty
add_relation(Camera DOF) - Could not find op_from (ComponentKey(OBEmpty, TRANSFORM))
add_relation(Camera DOF) - Failed, but op_to (ComponentKey(CACamera, PARAMETERS)) was ok

@Sergey, this bug is still happening after b432209f63. Seems the empty use to control the distance is not made part of the graph. ``` find_node component: Could not find ID OBEmpty add_relation(Camera DOF) - Could not find op_from (ComponentKey(OBEmpty, TRANSFORM)) add_relation(Camera DOF) - Failed, but op_to (ComponentKey(CACamera, PARAMETERS)) was ok ```

Sergey Sharybin commented

2019-05-23 17:16:11 +02:00

Actually, i think it is now fixed by faf48c0f64.

The confusing thing is that with the f-stop of 2.4 (used in the attached file) the blur is higher than Max Blur setting. Making f-stop 32 clearly shows that the animation on DoF object works correct.

Actually, i think it is now fixed by faf48c0f64. The confusing thing is that with the f-stop of 2.4 (used in the attached file) the blur is higher than Max Blur setting. Making f-stop 32 clearly shows that the animation on DoF object works correct.

Brecht Van Lommel commented

2019-05-23 17:23:17 +02:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2019-05-23 17:23:17 +02:00

Brecht Van Lommel self-assigned this 2019-05-23 17:23:17 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Camera DOF distance based on an object doesn't update on animations with compositing Defocus #60961