Color Ramp node keyed colors and keyed positions jumps to the next color stop when adding or removing color stops #77931

New Issue

Gilberto Rodrigues · 2020-06-16T22:09:25+02:00

2020-06-16 22:09:25 +02:00

Blender Version
Broken: 2.7x, 2.8x

Short description of error
The keyed color and position should be assigned to the color stop itself, not it's order. As of now it follows the order of stops, so the keyed color and position jumps from one color stop to next one when a color stop is added or removed.

2020-06-16 17-27-47.mp4	2020-06-16 17-13-58.mp4

Exact steps for others to reproduce the error

open blender
go the shader editor
make a new material
add a color ramp node
Press "i" with the mouse hovering the black bar to key the color.
now the white color stop and do the same, key the color by pressing "i" over it.
now select the black color stop and remove it by clicking the "-"
press space bar to play, the keyed color will jump from the black one that was removed to the white one.
The same happens if you key the color stop's position instead of it's color.
It also jumps when adding in a color stop instead of removing one.

**Blender Version** Broken: 2.7x, 2.8x **Short description of error** The keyed color and position should be assigned to the color stop itself, not it's order. As of now it follows the order of stops, so the keyed color and position jumps from one color stop to next one when a color stop is added or removed. |[2020-06-16 17-27-47.mp4](https://archive.blender.org/developer/F8626458/2020-06-16_17-27-47.mp4)|[2020-06-16 17-13-58.mp4](https://archive.blender.org/developer/F8626479/2020-06-16_17-13-58.mp4) | -- | -- | **Exact steps for others to reproduce the error** - open blender - go the shader editor - make a new material - add a color ramp node - Press "i" with the mouse hovering the black bar to key the color. now the white color stop and do the same, key the color by pressing "i" over it. now select the black color stop and remove it by clicking the "-" - press space bar to play, the keyed color will jump from the black one that was removed to the white one. The same happens if you key the color stop's position instead of it's color. It also jumps when adding in a color stop instead of removing one.

Gilberto Rodrigues commented

2020-06-16 22:09:25 +02:00

Added subscriber: @Gilberto.R

Gilberto Rodrigues commented

2020-06-16 22:35:05 +02:00

2020-06-16 17-27-47.mp4

[2020-06-16 17-27-47.mp4](https://archive.blender.org/developer/F8626458/2020-06-16_17-27-47.mp4)

Gilberto Rodrigues commented

2020-06-16 22:44:18 +02:00

2020-06-16 17-13-58.mp4

[2020-06-16 17-13-58.mp4](https://archive.blender.org/developer/F8626479/2020-06-16_17-13-58.mp4)

Germano Cavalcante commented

2020-06-19 05:29:43 +02:00

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

Germano Cavalcante commented

2020-06-19 05:36:01 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-06-19 05:36:02 +02:00

I can imagine why this happens.
Perhaps a diver/keyframe takes a stop reference as being index + position.
When you delete a stop you change the index of the rest, but the references in the drivers are not updated.

I imagine the confusion can be greater if a driver changes the order of stops.

Perhaps updating references can add a lot of overhead to the code. So it is not guaranteed that it is worth fixing it.

I can imagine why this happens. Perhaps a diver/keyframe takes a stop reference as being index + position. When you delete a stop you change the index of the rest, but the references in the drivers are not updated. I imagine the confusion can be greater if a driver changes the order of stops. Perhaps updating references can add a lot of overhead to the code. So it is not guaranteed that it is worth fixing it.

Jacques Lucke commented

2020-09-15 11:29:43 +02:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2020-09-15 11:29:43 +02:00

It's unlikely that this will be worked on soon. So I'll reclassify this as known issue.

It might be worth considering whether we could give each stop some kind of unique id that is referenced by fcurves and drivers, instead of referencing them by index. That might be much easier to do than to update all references when a new stop is inserted or one is removed.

It's unlikely that this will be worked on soon. So I'll reclassify this as known issue. It might be worth considering whether we could give each stop some kind of unique id that is referenced by fcurves and drivers, instead of referencing them by index. That might be much easier to do than to update all references when a new stop is inserted or one is removed.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Color Ramp node keyed colors and keyed positions jumps to the next color stop when adding or removing color stops #77931