image texture set to view node isn't working. #76352

Closed
opened 2020-05-02 23:54:59 +02:00 by michael campbell · 9 comments

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

Blender Version
Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-05-01 21:55, hash: 83304e4c22
Worked: (newest version of Blender that worked as expected)

Short description of error
image texture set to view node isn't working.

Exact steps for others to reproduce the error

See below:

2020-05-02 22-52-14.mp4

**System Information** Operating system: Windows-10-10.0.17763-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92 **Blender Version** Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-05-01 21:55, hash: `83304e4c22` Worked: (newest version of Blender that worked as expected) **Short description of error** image texture set to view node isn't working. **Exact steps for others to reproduce the error** See below: [2020-05-02 22-52-14.mp4](https://archive.blender.org/developer/F8508206/2020-05-02_22-52-14.mp4)

Added subscriber: @3di

Added subscriber: @3di

Added subscriber: @iss

Added subscriber: @iss

This looks like a workaround to view result in image editor https://docs.blender.org/manual/en/latest/compositing/types/output/viewer.html#using-the-image-editor
It is probably not supported to use it in other ways even if it look it can be. Though I would have to look into code to be completely sure.

This looks like a workaround to view result in image editor https://docs.blender.org/manual/en/latest/compositing/types/output/viewer.html#using-the-image-editor It is probably not supported to use it in other ways even if it look it can be. Though I would have to look into code to be completely sure.
Member

Added subscribers: @Sergey, @Jeroen-Bakker, @lichtwerk

Added subscribers: @Sergey, @Jeroen-Bakker, @lichtwerk
Member

This reminds me of #73182 (Exclude 'Render Result' and 'Viewer' image types in the dropdown in certain contexts [Shader Editor, Compositor, UV Editor...]).

It would be nice to have [if it were safe], but wouldnt this also run into recursion?
If you use the Viewer to feed into the shader that would update your Render result (which then would update the Viewer and shader again?)?

@Sergey, @Jeroen-Bakker: same as in #73182: should we exlude IMA_TYPE_COMPOSITE and IMA_TYPE_R_RESULT from the Image Browsing in the Shader Editor if this known to not work? -- possible enhancement... )

This reminds me of #73182 (Exclude 'Render Result' and 'Viewer' image types in the dropdown in certain contexts [Shader Editor, Compositor, UV Editor...]). It would be nice to have [if it were safe], but wouldnt this also run into recursion? If you use the Viewer to feed into the shader that would update your Render result (which then would update the `Viewer` and shader again?)? @Sergey, @Jeroen-Bakker: same as in #73182: should we exlude `IMA_TYPE_COMPOSITE` and `IMA_TYPE_R_RESULT` from the Image Browsing in the Shader Editor if this known to not work? -- possible enhancement... )
Member

Seems like this and #73182 are really the same issues, so will merge these reports and make a TODO out of this (exclude Render Result & Viewer types from the image dropdown if appropriate...)

Seems like this and #73182 are really the same issues, so will merge these reports and make a TODO out of this (exclude Render Result & Viewer types from the image dropdown if appropriate...)
Member

Closed as duplicate of #73182

Closed as duplicate of #73182

recursion could be avoided in some way, similar to how houdini does it. I'm not sure how they do it though. Guessing they run all compositors that are used in textures etc before the render. Maybe only disallow the use of comp outputs in textures if the compositor has a render layers node, as these would cause a recursion. Anything that only has sources such as images or movies should never cause recursion, so would be safe.

recursion could be avoided in some way, similar to how houdini does it. I'm not sure how they do it though. Guessing they run all compositors that are used in textures etc before the render. Maybe only disallow the use of comp outputs in textures if the compositor has a render layers node, as these would cause a recursion. Anything that only has sources such as images or movies should never cause recursion, so would be safe.

The idea in the above case was to be able to edit a video in blender's video editor, and then output the edited version onto a plane, so that the edited video could be more quickly rendered as a new video with an orthographic camera using EEVEE gpu rather than a slow CPU. A poor mans workaround to getting GPU rendering for the video editor :)

The idea in the above case was to be able to edit a video in blender's video editor, and then output the edited version onto a plane, so that the edited video could be more quickly rendered as a new video with an orthographic camera using EEVEE gpu rather than a slow CPU. A poor mans workaround to getting GPU rendering for the video editor :)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#76352
No description provided.