Page MenuHome

EeVee/Workbench: image sequence offset doesn't have the expected behavior (as seen in Cycles)
Confirmed, HighPublicBUG

Description

System Information
Operating system: Linux and Windows
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116 / Radeon (TM) RX 480 Graphics

Blender Version
Broken: version: 2.80rc1
Worked: (optional)

Short description of error
A camera with an "offset" Background Image sequence causes an object texture with "Window" texture coordinates to be offset as well, but only in EeVee (not Cycles)

Exact steps for others to reproduce the error
Image sequence:


Blend File:

  • Download the attached images and .blend file.
  • Decompact the images in the same directory as the .blend file but within a folder named images/.
  • Open attached file.
  • Switch the selection between the mesh and camera to compare image sequence settings in the mesh material and camera background. (Must be the same).
  • Forward some frames, note that the images are synchronized.
  • In any of the image settings (for example the background), change the offset and forward or backward some frames.
  • In Eevee and Workbench it makes no difference other than not finding some images in the sequence.
  • In Cycles it works correctly.

This can be observed causing an issue at ~13:35 in this video: https://youtu.be/8irtcgc8GqE?t=814
...In that tutorial video, the instructor is removing a large tracking marker using "Window" texture coordinates. At ~13:35 he switches from EeVee to Cycles to do the texture baking on to the overlay plane.

The image sequence on the textured plane aligns perfectly with the duplicate background image sequence when the renderer is set to EeVee, but when he switches to Cycles, it is misaligned. Strangely, though, I don't think the camera object is using an "offset" in that case, so perhaps the bug (if it is one) goes deeper than I have supposed. [update: turns out he did set an offset, though I'm not clear if it was already in place at the timestamp in that video.]

Another way to reproduce the bug:

  • open blender with fresh/clean profile directory
  • delete default cube, add a plane, create a new material
  • in shader editor, delete BSDF node, add Image Texture node, connect Color output to Surface input of Material Output node
  • add Texture Coordinate node, connect Window output to Image Texture "Vector" input
  • in Texture Node, open provided image sequence, then enable "Cyclic" and "Auto Refresh"
  • select main camera; in Properties -> Camera pane, enable Background Images, click "Add Image" and then "Open" the same image sequence as before; Change Alpha to 1.0
  • assume camera view with numpad-0, change to rendered mode (EeVee, by default)
  • observe that the background image and the plane texture are in sync, as expected, even when changing frames
  • change render mode to Cycles, and observe the same
  • select camera object in outliner; in Properties->Camera->Background Images, change the Offset to 1
  • observe that in Cycles, the plane texture and background textures are offset by 1 frame
  • observe that in EeVee, they are not: the plane adopts the offset of the camera background image

Event Timeline

I have sync between Eevee and cycles, so I don't experience the issue that you are describing.

I have attached a .blend with packed images for anyone who want's to test this thing.

System Information
Operating system: Windows-10-10.0.17763-SP0 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00

Blender Version
Broken: version: 2.82 (sub 6), branch: master, commit date: 2019-12-24 16:58, hash: rB33eabb82207e


I tried that demo file but the packed images don't seem to come through... In the image editor I see only "5.png" and the image doesn't actually appear in the image editor when it's selected (although the icon/thumbnail seems to be correct?). Similarly the outliner shows only "5.png"... let me know if I'm doing something wrong...

Germano Cavalcante (mano-wii) renamed this task from EeVee texture with "Window" texture coordinates adopts the image sequence offset of the camera object, and Cycles does not to EeVee/Workbench: image sequence offset doesn't have the expected behavior (as seen in Cycles).Tue, Dec 31, 1:21 PM
Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Confirmed.
Germano Cavalcante (mano-wii) triaged this task as High priority.
Germano Cavalcante (mano-wii) updated the task description. (Show Details)
Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Bug".