Eevee: image sequence data bloc displays different offset attributes when set from different locations (texture editor, shader editor, image locator) #109769

New Issue

Sarah Laufer · 2023-07-06T10:38:39+02:00

Sarah Laufer commented

2023-07-06 10:38:39 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12

Blender Version
Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b
Worked: (newest version of Blender that worked as expected)

Short description of error
if I change the offset (or start frame) of the sequence in the shader editor, I would expect it to also change in the image editor or wherever I am using the same image sequence, otherwise it causes discrepancies and buggy viewport display (since we dont know which offset is displayed in the viewport).

Exact steps for others to reproduce the error
Just change the offset of 1 of the 3 displayed image sequence settings displayed... the other 2 won't follow.

Cycles does this fine btw.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12 **Blender Version** Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: `1be25cfff18b` Worked: (newest version of Blender that worked as expected) **Short description of error** if I change the offset (or start frame) of the sequence in the shader editor, I would expect it to also change in the image editor or wherever I am using the same image sequence, otherwise it causes discrepancies and buggy viewport display (since we dont know which offset is displayed in the viewport). **Exact steps for others to reproduce the error** Just change the offset of 1 of the 3 displayed image sequence settings displayed... the other 2 won't follow. Cycles does this fine btw.

image_sequence_bug.zip

4.6 MiB

Sarah Laufer added the

labels 2023-07-06 10:38:40 +02:00

Dalai Felinto referenced this issue

2023-07-07 14:50:28 +02:00

Polishing the Painting Experience #109820

Philipp Oeser commented

2023-07-12 11:35:24 +02:00

Can confirm the behavior, but this is due to different Editors having different ImageUser.

So I think the separation between e.g. Image Editor and 3DView actually works as intended [and might even be useful :) ]

This also reminds me of #106312 (where another setting on the ImageUser is not propagated properly to the 3DView : Texture interpolation -- but strangely enough in that report it is only an issue with Solid/Workbench, whereas for this report it is an issue with Solid/Workbench and Eevee, in both #106312 and this report, Cycles does this properly btw.)

The situation in the 3DView seems much more problematic, it seems the 3DView cant actually display settings of different ImageUser users properly (in the case of this report, the ImageUser from the Image object vs, the ImageUser of the material node tree), as mentioned in #106312, it probably uses the last found ImageUser of that image as ground truth (which is confusion and not transparent, since the order of getting these cannot really be predicted).
This might be because of performance/resource issues on the GPU? (but even if so, I would assume "correctness" beats "performance" from the user side of things).

Will confirm for now.

Can confirm the behavior, but this is due to different Editors having different `ImageUser`. So I _think_ the separation between e.g. Image Editor and 3DView actually works as intended [and might even be useful :) ] This also reminds me of #106312 (where another setting on the `ImageUser` is not propagated properly to the 3DView : Texture interpolation -- but strangely enough in that report it is only an issue with Solid/Workbench, whereas for this report it is an issue with Solid/Workbench **and** Eevee, in both #106312 and this report, Cycles does this properly btw.) The situation in the 3DView seems much more problematic, it seems the 3DView cant actually display settings of different `ImageUser` users properly (in the case of this report, the `ImageUser` from the Image object vs, the `ImageUser` of the material node tree), as mentioned in #106312, it probably uses the last found `ImageUser` of that image as ground truth (which is confusion and not transparent, since the order of getting these cannot really be predicted). This might be because of performance/resource issues on the GPU? (but even if so, I would assume "correctness" beats "performance" from the user side of things). Will confirm for now.

Philipp Oeser added

and removed

labels 2023-07-12 11:35:38 +02:00

Philipp Oeser changed title from ~~image sequence data bloc displays different offset attributes when set from different locations (texture editor, shader editor, image locator)~~ to image sequence data bloc displays Eevee: different offset attributes when set from different locations (texture editor, shader editor, image locator)

2023-07-12 11:36:05 +02:00

Philipp Oeser changed title from ~~image sequence data bloc displays Eevee: different offset attributes when set from different locations (texture editor, shader editor, image locator)~~ to Eevee: image sequence data bloc displays different offset attributes when set from different locations (texture editor, shader editor, image locator)

2023-07-12 11:36:18 +02:00

Philipp Oeser added the

Module

EEVEE & Viewport

label 2023-07-12 11:36:29 +02:00

Philipp Oeser added the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Eevee: image sequence data bloc displays different offset attributes when set from different locations (texture editor, shader editor, image locator) #109769