different render result using custom shader in 2.8/2.79 vs. 2.79 branch #69386

New Issue

Marcin · 2019-09-01T20:15:08+02:00

Marcin commented

2019-09-01 20:15:08 +02:00

System Information
Operating system: WIN 10 64bit
Graphics card: GTX 1080Ti

Blender Version 2.79 2019.01.04 [hash a6acb4fba094]

Broken: 2.79 a6acb4fba094 2019.01.04
Worked: 2.79 rc-1

Short description of error scene created on 2.79 or 2.79a with custom Dielectric shader - than opened in 2.79 (last build), or scene created in 2.79 (last build) with materials created earlier (2.79 or 2.79RC) - effect like in file "freshy created...] When this scene will be opened in 2.8 the effect is the same but in 2.79RC the effect will be different - after overwrite (2.79rc) the effect will be the same on all versions
TEST scene [opened in 2.79RC and saved].blend

TEST scene [freshy created on 2.79lastV w apended materials].blend

Exact steps for others to reproduce the error same scene with glossy reflections and roughness parameter that work on other (earlier) builds and also on 2.8

**System Information** Operating system: WIN 10 64bit Graphics card: GTX 1080Ti **Blender Version** 2.79 2019.01.04 [hash a6acb4fba094] Broken: 2.79 a6acb4fba094 2019.01.04 Worked: 2.79 rc-1 **Short description of error** scene created on 2.79 or 2.79a with custom Dielectric shader - than opened in 2.79 (last build), or scene created in 2.79 (last build) with materials created earlier (2.79 or 2.79RC) - effect like in file "freshy created...] When this scene will be opened in 2.8 the effect is the same but in 2.79RC the effect will be different - after overwrite (2.79rc) the effect will be the same on all versions [TEST scene [opened in 2.79RC and saved].blend](https://archive.blender.org/developer/F7713310/TEST_scene__opened_in__2.79RC_and_saved_.blend) [TEST scene [freshy created on 2.79lastV w apended materials].blend](https://archive.blender.org/developer/F7713313/TEST_scene__freshy_created_on_2.79lastV_w_apended_materials_.blend) ![WOOD.jpg](https://archive.blender.org/developer/F7713308/WOOD.jpg) ![Test_B3[2.79_ biuld 2019.01.04 time 4m22s].png](https://archive.blender.org/developer/F7713302/Test_B3_2.79__biuld_2019.01.04_time_4m22s_.png) ![Test_B3[2.79rc_ biuld 2017.08.01 time 5m06s].png](https://archive.blender.org/developer/F7713301/Test_B3_2.79rc__biuld_2017.08.01_time_5m06s_.png) **Exact steps for others to reproduce the error** same scene with glossy reflections and roughness parameter that work on other (earlier) builds and also on 2.8

Marcin commented

2019-09-01 20:15:08 +02:00

Added subscriber: @MarcinChomiczuk

Philipp Oeser changed title from ~~2.79 2019.01.04 [hash a6acb4fba094]~~ to different render result using custom shader in 2.8/2.79 vs. 2.79 branch

2019-09-02 15:53:17 +02:00

Philipp Oeser commented

2020-01-20 15:38:55 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-01-20 15:38:55 +01:00

Changed status from 'Needs Triage' to: 'Archived'

Philipp Oeser closed this issue

2020-01-20 15:38:55 +01:00

Philipp Oeser self-assigned this 2020-01-20 15:38:55 +01:00

Philipp Oeser commented

2020-01-20 15:38:55 +01:00

Hi and thx for the report (sorry this has been lying around for so long...)

I see a difference between those two files in that the Reflection nodegroup has an extra Power node inserted from the Group Input socket before the Glossy BSDF.
If I remove that, both renders are identical. Cannot really imagine this was part of the newer 2.79 logic?

In any case, since I dont have access to this build anymore and this seems to have been corrected (if it ever was wrong) and this now works as expected, I am afraid we have to close this now...
(Sorry if this has caused trouble).
Feel free though to comment again if this ever comes up again.

Hi and thx for the report (sorry this has been lying around for so long...) I see a difference between those two files in that the `Reflection` nodegroup has an extra `Power` node inserted from the Group Input socket before the Glossy BSDF. If I remove that, both renders are identical. Cannot really imagine this was part of the newer 2.79 logic? In any case, since I dont have access to this build anymore and this seems to have been corrected (if it ever was wrong) and this now works as expected, I am afraid we have to close this now... (Sorry if this has caused trouble). Feel free though to comment again if this ever comes up again.

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

different render result using custom shader in 2.8/2.79 vs. 2.79 branch #69386