Page MenuHome

Eevee motion blur causes ghosting on image sequences when steps are greater than one
Confirmed, NormalPublic


System Information
Operating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits
Also tested on Windows-10-10.0.19041
Graphics card: AMD Radeon Pro Vega 48 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: rB0330d1af29c0
Worked: (newest version of Blender that worked as expected)

Short description of error
The next frame of an image sequence/video texture is added onto the current one when the step count in Eevee's motion blur is any value greater than one.

Demo file:

Video used:

Exact steps for others to reproduce the error

  1. Create a material that references a video or image sequence in any form
  2. Turn on motion blur and set step count to any value greater than one
  3. Render

Event Timeline

Richard Antalik (ISS) changed the task status from Needs Triage to Confirmed.Wed, Sep 9, 3:32 AM

This issue also appears to affect objects when Disable in Render is keyframed. Behavior on the frame when the value changes from -1 (visible) to 1 (invisible):

1 step

2 steps