Using viewernode as an image texture causes shader or compositor to fail intermittently #85717

New Issue

Matthew Wiebe · 2021-02-17T03:34:27+01:00

Matthew Wiebe commented

2021-02-17 03:34:27 +01:00

System Information
Operating system: Linux-5.8.0-38-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03

Blender Version
Broken: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash: 5be9ef4177

Short description of error
Set up a scene with compositor tree and a viewer node connected to the scene input. Add a material to the default cube, connect an image texture node to the surface output. Select "Viewer Node" as the image texture. Press render. Result will probably be a purple cube. This is perfectly understandable, however what's not understandable (or at least not desireable) is that this will often still happen even if the viewer node currently contains a valid image. Say you just rendered something into the compositor and you want to preview it as a texture on an object. You can do this with the viewer node, and then tweak masks or compositor settings and see the texture update on the model in realtime. However, if you press render again, even if the viewernode textured model is offscreen, this stops working. In fact, it even breaks the viewer node itself, such that trying to view the viewer node contents in the image editor shows solid purple.

Expected behaviour: contents of viewer node (and probably "render result" as well) should be cached before rendering so blender can use them during the shading process without getting confused. Would allow better editing of objects textured by renders. This already seems to kind of work intermittently, so I don't really consider this a feature request.

**System Information** Operating system: Linux-5.8.0-38-generic-x86_64-with-debian-bullseye-sid 64 Bits Graphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03 **Blender Version** Broken: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash: `5be9ef4177` **Short description of error** Set up a scene with compositor tree and a viewer node connected to the scene input. Add a material to the default cube, connect an image texture node to the surface output. Select "Viewer Node" as the image texture. Press render. Result will probably be a purple cube. This is perfectly understandable, however what's *not* understandable (or at least not desireable) is that this will often still happen even if the viewer node currently contains a valid image. Say you just rendered something into the compositor and you want to preview it as a texture on an object. You can do this with the viewer node, and then tweak masks or compositor settings and see the texture update on the model in realtime. However, if you press render again, *even if the viewernode textured model is offscreen*, this stops working. In fact, it even breaks the viewer node itself, such that trying to view the viewer node contents in the image editor shows solid purple. Expected behaviour: contents of viewer node (and probably "render result" as well) should be cached before rendering so blender can use them during the shading process without getting confused. Would allow better editing of objects textured by renders. This already seems to kind of work intermittently, so I don't really consider this a feature request.

Matthew Wiebe commented

2021-02-17 03:34:27 +01:00

Added subscriber: @cerebral

Philipp Oeser commented

2021-02-17 14:19:13 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-02-17 14:19:13 +01:00

There is some discussion about this in #73182 (Exclude 'Render Result' and 'Viewer' image types in the dropdown in certain contexts [Shader Editor, Compositor, UV Editor...])

Philipp Oeser commented

2021-02-17 14:20:41 +01:00

Added subscriber: @Jeroen-Bakker

Philipp Oeser commented

2021-02-17 14:20:41 +01:00

My understanding is that at its current state, this is not supported.
@Jeroen-Bakker: objections to merge this into {#73182}?

My understanding is that at its current state, this is not supported. @Jeroen-Bakker: objections to merge this into {#73182}?

Philipp Oeser commented

2021-02-18 17:29:27 +01:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Philipp Oeser commented

2021-02-18 17:29:27 +01:00

I would not hold my breath here (do not think there is a high chance of this being supported).
Will tag as needing module input, this might also be a design question.

I would not hold my breath here (do not think there is a high chance of this being supported). Will tag as needing module input, this might also be a design question.

Jeroen Bakker commented

2021-04-12 13:47:47 +02:00

Closed as duplicate of #73182

Jeroen Bakker closed this issue

2021-04-12 13:47:47 +02:00

Jeroen Bakker commented

2021-04-12 13:47:51 +02:00

@lichtwerk yes this is currently not supported and should be hidden.

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

Using viewernode as an image texture causes shader or compositor to fail intermittently #85717