Double-clicking on a texture image node on the shader editor, no longer show's the texture on the image editor #70643

New Issue

Daniel Santana · 2019-10-08T16:27:05+02:00

Daniel Santana commented

2019-10-08 16:27:05 +02:00

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48

Blender Version
Broken: version: 2.81 (sub 14), branch: master, commit date: 2019-10-08 13:58, hash: abc36cad83
Worked: before commit r5f51e781720649be7c1079353d068a51829b33b9

Short description of error
Double-clicking on a texture image node on the shader editor, no longer show's the texture on the image editor if it's open.

Exact steps for others to reproduce the error
Open Blender
Add the shader editor and the image editor to the current layout.
Assing any image texture to the default cube material.
Double click on the image texture node.
Nothing happens on the image editor.

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48 **Blender Version** Broken: version: 2.81 (sub 14), branch: master, commit date: 2019-10-08 13:58, hash: `abc36cad83` Worked: before commit `r5f51e781720649be7c1079353d068a51829b33b9` **Short description of error** Double-clicking on a texture image node on the shader editor, no longer show's the texture on the image editor if it's open. **Exact steps for others to reproduce the error** Open Blender Add the shader editor and the image editor to the current layout. Assing any image texture to the default cube material. Double click on the image texture node. Nothing happens on the image editor.

Daniel Santana commented

2019-10-08 16:27:05 +02:00

Added subscriber: @dgsantana

Dalai Felinto commented

2019-10-08 16:29:56 +02:00

Added subscribers: @JulianEisel, @dfelinto

Julian Eisel was assigned by Dalai Felinto

2019-10-08 16:29:56 +02:00

Dalai Felinto commented

2019-10-08 16:29:56 +02:00

Hi @JulianEisel was this change intentional? From the look at the commit log this was supposed to be a refactor/cleanup with no behaviour changes.
PS I haven't tested it, but trusting the reporter here

Hi @JulianEisel was this change intentional? From the look at the commit log this was supposed to be a refactor/cleanup with no behaviour changes. PS I haven't tested it, but trusting the reporter here

Julian Eisel commented

2019-10-08 16:58:36 +02:00

Just checked this with a build from before my changes, as well as the 2.80 and the 2.79b releases. I can't get the behavior you describe here in either of them.
Are you sure this is a standard feature? I.e. not implemented by an Add-on? You can try with factory settings ({nav File > Defaults > Load Factory Settings} - this will not override your default configuration, no worries).

Otherwise, please check if the mentioned steps really invoke the wanted behavior.

Just checked this with a build from before my changes, as well as the 2.80 and the 2.79b releases. I can't get the behavior you describe here in either of them. Are you sure this is a standard feature? I.e. not implemented by an Add-on? You can try with factory settings ({nav File > Defaults > Load Factory Settings} - this will not override your default configuration, no worries). Otherwise, please check if the mentioned steps really invoke the wanted behavior.

Daniel Santana commented

2019-10-08 17:09:02 +02:00

Sorry for the delay, I'm rebuilding again before your commit, and will test with defaults. The only addon that I have for the nodes is the node wrangler.

Daniel Santana commented

2019-10-08 17:17:04 +02:00

Sorry to make lose time, but definitely is some addon, just can't figure which one, even when disabling all, the behaviour persists. But I will keep investigating, please close this bug report.

Philipp Oeser commented

2019-10-08 17:21:45 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-10-08 17:21:45 +02:00

Changed status from 'Open' to: 'Archived'

Philipp Oeser closed this issue

2019-10-08 17:21:45 +02:00

Philipp Oeser commented

2019-10-08 17:21:45 +02:00

OKi, will close, thx for getting back...

chris hofmann commented

2020-10-04 15:21:32 +02:00

Added subscriber: @krz9000

chris hofmann commented

2020-10-04 15:21:32 +02:00

Double-clicking on a texture image node on the shader editor, no longer show's the texture on the image editor.

i have no clue if this ever was a feature but it needs to happen. double clicking a texture node should always update the image editor. pls let me know what speaks against such a common sense behaviour

Double-clicking on a texture image node on the shader editor, no longer show's the texture on the image editor. i have no clue if this ever was a feature but it needs to happen. double clicking a texture node should always update the image editor. pls let me know what speaks against such a common sense behaviour

chris hofmann commented

2021-07-26 19:37:38 +02:00

any news on this? double clicking the texture node should show the texture in the image editor. very basic feature that would make blender one step less akward to use

Philipp Oeser commented

2021-07-26 21:03:39 +02:00

note D11498: Texture Paint: sync changing active texture in the Node Editor to the Image Editor is sort of doing a sync (but on single click)

note [D11498: Texture Paint: sync changing active texture in the Node Editor to the Image Editor](https://archive.blender.org/developer/D11498) is sort of doing a sync (but on single click)

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

Double-clicking on a texture image node on the shader editor, no longer show's the texture on the image editor #70643