Maniphest T70204

RGB Curve Node point order switching
Closed, Archived

Assigned To
Jeroen Bakker (jbakker)
Authored By
Julien Kaspar (JulienKaspar)
Sep 24 2019, 2:58 PM
Tags
  • Blender Studio
  • BF Blender (2.82)
Subscribers
Brecht Van Lommel (brecht)
Dalai Felinto (dfelinto)
Germano Cavalcante (mano-wii)
Jeroen Bakker (jbakker)
Julien Kaspar (JulienKaspar)

Description

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30

Blender Version
Broken: version: 2.81 (sub 12), branch: master, commit date: 2019-09-23 15:18, hash: rB14acac0bb7f3

Short description of error
In the RGB curves node it is possible to set multiple points to have the same x location. In that case Blender seems to decide which one is the first in the curve.
Every time the same value is used, Blender cycles through the points to decide which one comes first.

The current issue is that when rendering it seems to now also cycle between the points every time.
There is one of these instances in the Spring Splash Screen and Spring Benchmark render that result in her jacket turning pink every other time it is being rendered.

While this is also a mistake by the user, the order of the curve points that Blender decided on should not change every time it is being rendered.

Event Timeline

Julien Kaspar (JulienKaspar) created this task.Sep 24 2019, 2:58 PM
Julien Kaspar (JulienKaspar) added a project: Blender Studio.
Julien Kaspar (JulienKaspar) moved this task from To Do to Commited/In Review on the Blender Studio board.
Julien Kaspar (JulienKaspar) updated the task description.Sep 24 2019, 3:02 PM
Germano Cavalcante (mano-wii) assigned this task to Jeroen Bakker (jbakker).Sep 27 2019, 7:52 PM
Germano Cavalcante (mano-wii) lowered the priority of this task from 90 to 50.
Germano Cavalcante (mano-wii) added subscribers: Jeroen Bakker (jbakker), Brecht Van Lommel (brecht), Germano Cavalcante (mano-wii).

It involves the same area of the problem reported in T67981
Therefore assigning to @Jeroen Bakker (jbakker)

Cc @Brecht Van Lommel (brecht)

Jeroen Bakker (jbakker) edited projects, added BF Blender (2.82); removed BF Blender.Oct 15 2019, 11:38 AM
Jeroen Bakker (jbakker) lowered the priority of this task from 50 to 30.Nov 1 2019, 9:45 AM

@Julien Kaspar (JulienKaspar) Can you retest, I am not able to reproduce this one anymore.

Dalai Felinto (dfelinto) changed the task status from Unknown Status to Unknown Status.Nov 26 2019, 10:50 PM
Dalai Felinto (dfelinto) added a subscriber: Dalai Felinto (dfelinto).

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

Julien Kaspar (JulienKaspar) added a comment.Nov 27 2019, 7:27 AM

@Jeroen Bakker (jbakker) I fixed the files on the cloud since there were still people sharing the pink jacket spring renders ...
I can still reliably reproduce this bug. We can look at it once I'm back from CTN.

Jeroen Bakker (jbakker) changed the task status from Unknown Status to Unknown Status.Nov 27 2019, 8:04 AM
Germano Cavalcante (mano-wii) raised the priority of this task from 30 to 50.Nov 27 2019, 2:00 PM

I can confirm that the problem still persists.
To do this simply add an RGB Curves Node to the material;
Add 2 points;
and type 0.5 for the x coordinate of these 2 points.

Each time you update the coordinate of the upper point, the curve changes.

Jeroen Bakker (jbakker) added a comment.Dec 11 2019, 8:48 AM

Argh... I am still not able to reproduce using master. Also with the steps mentioned the results are consistent on my machine...
I am running on Linux Ubuntu 18.04.4. Any confirm on any point gives the same result.

Julien Kaspar (JulienKaspar) added a comment.Dec 11 2019, 10:27 AM

@Germano Cavalcante (mano-wii) @Jeroen Bakker (jbakker)

I also can't reproduce it anymore in the latest master, both manually or when rendering.

Jeroen Bakker (jbakker) changed the task status from Unknown Status to Unknown Status.Dec 17 2019, 1:56 PM

Unable to reproduce it anymore. checked with @Julien Kaspar (JulienKaspar) he is ok to close it for now.