Page MenuHome

Animation works in view port but acts differently when rendered
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92

Blender Version
Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: rB211b6c29f771
Worked: (newest version of Blender that worked as expected)

Short description of error
I rigged a clamp and animated it. It works fine when previewing the animation in the viewport. However, when I go to render out the animation the animation acts very strange and does not move as it should.

Exact steps for others to reproduce the error
view the animation in the viewport to see how it should move, then render the animation using either the workbench render engine or eevee and you will notice the clamp arm is not animating as it did in the viewport.

Event Timeline

Evan Wilson (EAW) changed the task status from Needs Triage to Needs Information from User.Jun 12 2020, 2:09 AM

You have a couple of dependency cycles as shown in the following debug log.

This file has 433 objects in it, making it too complicated to try to debug further. Please simplify it, removing the parts that are not involved in the issue.

Hi Evan,

Attached is a simplified file. Thanks.

Philipp Oeser (lichtwerk) closed this task as Archived.Jun 12 2020, 3:25 PM
Philipp Oeser (lichtwerk) claimed this task.

These are the dependecy cycles reported:

Dependency cycle detected:
  OBArmature.001/Bone.001/BONE_CONSTRAINTS() depends on
  OBArmature.001/Bone.002/BONE_DONE() via 'Damped Track'
  OBArmature.001/Bone.002/BONE_READY() via 'Ready -> Done'
  OBArmature.001/Bone.002/BONE_POSE_PARENT() via 'Pose -> Ready'
  OBArmature.001/Bone.003/BONE_DONE() via 'Parent Bone -> Child Bone'
  OBArmature.001/Bone.003/BONE_READY() via 'Ready -> Done'
  OBArmature.001/Bone.003/BONE_CONSTRAINTS() via 'Constraints -> Ready'
  OBArmature.001/Bone.001/BONE_DONE() via 'Damped Track'
  OBArmature.001/Bone.001/BONE_READY() via 'Ready -> Done'
  OBArmature.001/Bone.001/BONE_CONSTRAINTS() via 'Constraints -> Ready'
Detected 1 dependency cycles
Dependency cycle detected:
  OBArmature.001/Bone.001/BONE_CONSTRAINTS() depends on
  OBArmature.001/Bone.002/BONE_DONE() via 'Damped Track'
  OBArmature.001/Bone.002/BONE_READY() via 'Ready -> Done'
  OBArmature.001/Bone.002/BONE_POSE_PARENT() via 'Pose -> Ready'
  OBArmature.001/Bone.003/BONE_DONE() via 'Parent Bone -> Child Bone'
  OBArmature.001/Bone.003/BONE_READY() via 'Ready -> Done'
  OBArmature.001/Bone.003/BONE_CONSTRAINTS() via 'Constraints -> Ready'
  OBArmature.001/Bone.001/BONE_DONE() via 'Damped Track'
  OBArmature.001/Bone.001/BONE_READY() via 'Ready -> Done'
  OBArmature.001/Bone.001/BONE_CONSTRAINTS() via 'Constraints -> Ready'
Detected 1 dependency cycles

So Bone.001 depends on Bone.002 which depends on Bone.003 which in turn depends on Bone.001

Those dependency cycles are not supported in a reliable manner, meaning that they will have issues with a possible one-frame-delay, issues in scrubbing/jumping in the timeline, and yes, issues in rendering.
There might be ways to rig this differently, but this is outside the scope of the bugtracker unfortunately.

Afraid we have to close this (feel free to comment again though if issues persist when setting this up without dependency cycles). Thx reporting anyways!