Shader node connections in v3.0 file broken in v3.3 #101014

New Issue

Karl Nyman · 2022-09-12T18:47:30+02:00

Karl Nyman commented

2022-09-12 18:47:30 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79

Blender Version
Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: 0759f671ce
Worked: 3.0

Short description of error
Rendering in 3.3 a file created in 3.0 (using both Cycles & Eevee) showed major differences from rendering made in 3.0. Investigation showed that critical node connections in multiple shader trees were broken when opening file in 3.3. Unable to determine if broken connections are consistent in terms of node type. Which nodes have broken connections seems consistent from file to file using the same shaders -- sample .blend was constructed with shaders used in file where bug was first observed. All shaders were originally created in versions prior to 3.0 but later than 2.80.

Attached GIMP .xcf file has exemplary renderings and explanatory screenshots from file where bug was first identified. Sample .blend file was created in v3.0 using shaders from this file. Bug does occur in other files which render fine in 3.0 but have broken shaders in 3.3

Exact steps for others to reproduce the error
REVISED sample file 300.blend

Open "sample file 300.blend" in v3.0 and inspect shader trees. Open in 3.3 and inspect shader trees, some nodes of which are now disconnected.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79 **Blender Version** Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: `0759f671ce` Worked: 3.0 **Short description of error** Rendering in 3.3 a file created in 3.0 (using both Cycles & Eevee) showed major differences from rendering made in 3.0. Investigation showed that critical node connections in multiple shader trees were broken when opening file in 3.3. Unable to determine if broken connections are consistent in terms of node type. Which nodes have broken connections seems consistent from file to file using the same shaders -- sample .blend was constructed with shaders used in file where bug was first observed. All shaders were originally created in versions prior to 3.0 but later than 2.80. Attached GIMP .xcf file has exemplary renderings and explanatory screenshots from file where bug was first identified. Sample .blend file was created in v3.0 using shaders from this file. Bug does occur in other files which render fine in 3.0 but have broken shaders in 3.3 ![Shader node bug.xcf](https://archive.blender.org/developer/F13484631/Shader_node_bug.xcf) **Exact steps for others to reproduce the error** [REVISED sample file 300.blend](https://archive.blender.org/developer/F13486164/REVISED_sample_file_300.blend) Open "sample file 300.blend" in v3.0 and inspect shader trees. Open in 3.3 and inspect shader trees, some nodes of which are now disconnected.

Karl Nyman commented

2022-09-12 18:47:30 +02:00

Added subscriber: @chipmasque

Richard Antalik commented

2022-09-13 00:42:39 +02:00

Added subscriber: @iss

Richard Antalik commented

2022-09-13 00:42:39 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2022-09-13 00:42:39 +02:00

I don't think I can reproduce the issue, here are 2 images rendered in version 3.3 and 3.0:

Also I don't see any difference in node tree (at least functionally).

Can you double check if provided file is the correct one?

I don't think I can reproduce the issue, here are 2 images rendered in version 3.3 and 3.0: ![300.png](https://archive.blender.org/developer/F13485577/300.png) ![330.png](https://archive.blender.org/developer/F13485579/330.png) Also I don't see any difference in node tree (at least functionally). Can you double check if provided file is the correct one?

Karl Nyman commented

2022-09-13 04:34:40 +02:00

You are correct, the sample file included above is not as I intended -- I think I might have inadvertently saved the file in 3.3 then resaved it in 3.0 without noticing the change (missing shader node connections) caused by the bug. My apologies. Attached is a new "REVISED sample file 300.blend" which I have double and triple-checked in 3.0 and 3.3 (including a download of the files from this thread), and the bug is there; please see also the new .xcf file with screenshots of the UI in both versions with preview rendering in Cycles. I have used only one shader showing the bug in this new sample file, called "RoxiesSlinkyDress," and have displayed the shader tree prominently so the missing connections are obvious. Nonetheless it took me a great deal more time to prep because it is made from the file that was used for the renderings in the initial .xcf file, and I had to strip out many dozens of irrelevant data blocks, Please be sure not to save this file in 3.3!

Procedure: Open file in version 3.0 and preview render (or render to an image file). Close file and open in 3.3 and repeat the rendering step(s), but DO NOT SAVE in 3.3. Notice the missing shader node connections in the UI. Please also note that the other shader in the file, called "Pearl," also uses Glossy and SSS nodes, but its connections remain intact, so the bug does not seem to be related to a particular shader node type, though both Glossy and SSS nodes more often show the bug.

This also may be germane: After reading Richard's post above, in version 3.0 I fixed the disconnected shader nodes in the original sample file, the one I may have saved in 3.3 by accident with broken shader connections. I saved that file in 3.0, then opened it in 3.3, and the bug DID NOT HAPPEN -- the fixed shader node connections made it through the transition to 3.3. Perhaps having it saved in 3.3 before the repairs in 3.0 were made affected some aspect of the file that prevented the bug from occurring. This is also why I could not provide a replacement copy of the original sample .blend -- I had somehow fixed it, or it fixed itself. Hence the new and simpler file (that took twice as long to produce).

REVISED sample file 300.blend

You are correct, the sample file included above is not as I intended -- I think I might have inadvertently saved the file in 3.3 then resaved it in 3.0 without noticing the change (missing shader node connections) caused by the bug. My apologies. Attached is a new "REVISED sample file 300.blend" which I have double and triple-checked in 3.0 and 3.3 (including a download of the files from this thread), and the bug is there; please see also the new .xcf file with screenshots of the UI in both versions with preview rendering in Cycles. I have used only one shader showing the bug in this new sample file, called "RoxiesSlinkyDress," and have displayed the shader tree prominently so the missing connections are obvious. Nonetheless it took me a great deal more time to prep because it is made from the file that was used for the renderings in the initial .xcf file, and I had to strip out many dozens of irrelevant data blocks, Please be sure not to save this file in 3.3! Procedure: Open file in version 3.0 and preview render (or render to an image file). Close file and open in 3.3 and repeat the rendering step(s), but DO NOT SAVE in 3.3. Notice the missing shader node connections in the UI. Please also note that the other shader in the file, called "Pearl," also uses Glossy and SSS nodes, but its connections remain intact, so the bug does not seem to be related to a particular shader node type, though both Glossy and SSS nodes more often show the bug. This also may be germane: After reading Richard's post above, in version 3.0 I fixed the disconnected shader nodes in the original sample file, the one I may have saved in 3.3 by accident with broken shader connections. I saved that file in 3.0, then opened it in 3.3, and the bug DID NOT HAPPEN -- the fixed shader node connections made it through the transition to 3.3. Perhaps having it saved in 3.3 before the repairs in 3.0 were made affected some aspect of the file that prevented the bug from occurring. This is also why I could not provide a replacement copy of the original sample .blend -- I had somehow fixed it, or it fixed itself. Hence the new and simpler file (that took twice as long to produce). [REVISED sample file 300.blend](https://archive.blender.org/developer/F13486164/REVISED_sample_file_300.blend) ![REVISED sample file screenshots.xcf](https://archive.blender.org/developer/F13486166/REVISED_sample_file_screenshots.xcf)

Richard Antalik commented

2022-09-13 21:27:12 +02:00

Changed status from 'Needs User Info' to: 'Confirmed'

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Shader node connections in v3.0 file broken in v3.3 #101014