Lamp data color not replaced when using nodes in cycles #65859

Closed
opened 2019-06-16 18:24:55 +02:00 by Cédric · 11 comments
Member

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.91

Blender Version
Broken: version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-15 22:35, hash: 87de71a8aa
Worked: (optional)

Short description of error
In Cycles, the data color of the lamp is not replaced but multiplied when using the nodes shading.

Exact steps for others to reproduce the error
Open the default scene
Select the point lamp
Change the data color to red
In the object data, click on "Use Nodes"
In the Emission node, change the color to blue.
The lamp color should be blue, but instead of replacing the data color, the color is multiplied.
image.png
color_data_lamp.blend

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.91 **Blender Version** Broken: version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-15 22:35, hash: `87de71a8aa` Worked: (optional) **Short description of error** In Cycles, the data color of the lamp is not replaced but multiplied when using the nodes shading. **Exact steps for others to reproduce the error** Open the default scene Select the point lamp Change the data color to red In the object data, click on "Use Nodes" In the Emission node, change the color to blue. The lamp color should be blue, but instead of replacing the data color, the color is multiplied. ![image.png](https://archive.blender.org/developer/F7105891/image.png) [color_data_lamp.blend](https://archive.blender.org/developer/F7105890/color_data_lamp.blend)
Author
Member

Added subscriber: @Clarkx

Added subscriber: @Clarkx

#68535 was marked as duplicate of this issue

#68535 was marked as duplicate of this issue

#68361 was marked as duplicate of this issue

#68361 was marked as duplicate of this issue

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2019-06-16 20:48:52 +02:00

This is by design, the shading nodes are intended to be an additional effect and not to replace the color.

This is by design, the shading nodes are intended to be an additional effect and not to replace the color.
Author
Member

Ok, thanks, i thought it was a bug..

Sorry to bother you, but just for my information, why not just set the color data to full white and hide it if "Use nodes" is checked ?

Maybe that is because EEVEE does not support nodes for the moment, but what is the benefits of this design as a user ? because it is veryconfusing. If I check "Use Nodes", I'm expecting to use only the nodes. Is it the same for the strength and the power ?

Thanks again for your help.

Ok, thanks, i thought it was a bug.. Sorry to bother you, but just for my information, why not just set the color data to full white and hide it if "Use nodes" is checked ? Maybe that is because EEVEE does not support nodes for the moment, but what is the benefits of this design as a user ? because it is *very*confusing. If I check "Use Nodes", I'm expecting to use *only* the nodes. Is it the same for the strength and the power ? Thanks again for your help.

It's the same for strength and power, and it's useful to be able to share lights with Eevee and to allow units to be used for power.

It's the same for strength and power, and it's useful to be able to share lights with Eevee and to allow units to be used for power.

Added subscribers: @YegorSmirnov, @Mets, @jenkm

Added subscribers: @YegorSmirnov, @Mets, @jenkm
Member

Added subscribers: @BugFinder, @lichtwerk

Added subscribers: @BugFinder, @lichtwerk

Well, but ... seriously: two input nodes labelled the same as two other input nodes?
I think it would be a good idea if the labels close to the input nodes would have some different text.

Say: Color, Strength for the "normal" values (as of now) and Color Multiplier, Strength Multiplier for the "Nodes" values.
Probably this would help creating less confusion.

I think it's just a 5 seconds update on the UI for man...
And a big leap for humanity!

;)

Just to cite someone wiser than me, some 50 years ago...

Well, but ... seriously: two input nodes labelled **the same** as two other input nodes? I think it would be a good idea if the labels close to the input nodes would have some **different text**. Say: `Color`, `Strength` for the "normal" values (as of now) and `Color Multiplier`, `Strength Multiplier` for the "Nodes" values. Probably this would help creating less confusion. I think it's just a 5 seconds update on the UI for man... And a big leap for humanity! ;) Just to cite someone wiser than me, some 50 years ago...
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#65859
No description provided.