Problem mixing Hair shader using color ramp and Hair Info Intercept value #93187

Closed
opened 2021-11-18 14:27:09 +01:00 by Terry Edhouse · 9 comments

System Information
Operating system: Linux-4.15.0-142-generic-x86_64-with-glibc2.23 64 Bits
Graphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.82.00

Blender Version
Broken: version: 2.93.6, branch: master, commit date: 2021-11-16 14:54, hash: c842a90e2f; also broken on 3.0 beta 'd8fd575af9cd'
Worked: None

Short description of error
Shader mixing problem when passing Hair Info 'Intercept' value through ColorRamp

Captura de Tela 2021-12-08 às 16.41.20.png

When the 1st shader input to a Mix Shader node is a Hair Shader and the mix factor value is a "Pure White" value output by a ColorRamp node (using the Intercept value from a Hair Info node as the input factor), the output of the Mix shader is Black.

If the same Hair shader is connected to both Mix Shader inputs then the problem does not occur - but if two separate Hair shader nodes with identical settings are connected to the Mix shader then the problem occurs.

Using Cardinal on the ColorRamp node gives a banding effect when the righthand color stop is set to off-white.

If you have the Hair Shader connected to the Mix Shader's 2nd input, the problem does not occur.

Exact steps for others to reproduce the error

  • Open attached blend file
  • Set the 3D Viewport shading to Rendered.

MixHairShaders.blend

**System Information** Operating system: Linux-4.15.0-142-generic-x86_64-with-glibc2.23 64 Bits Graphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.82.00 **Blender Version** Broken: version: 2.93.6, branch: master, commit date: 2021-11-16 14:54, hash: `c842a90e2f`; also broken on 3.0 beta 'd8fd575af9cd' Worked: None **Short description of error** Shader mixing problem when passing Hair Info 'Intercept' value through ColorRamp ![Captura de Tela 2021-12-08 às 16.41.20.png](https://archive.blender.org/developer/F12712732/Captura_de_Tela_2021-12-08_a_s_16.41.20.png) When the 1st shader input to a Mix Shader node is a Hair Shader and the mix factor value is a "Pure White" value output by a ColorRamp node (using the Intercept value from a Hair Info node as the input factor), the output of the Mix shader is Black. If the same Hair shader is connected to both Mix Shader inputs then the problem does not occur - but if two separate Hair shader nodes with identical settings are connected to the Mix shader then the problem occurs. Using Cardinal on the ColorRamp node gives a banding effect when the righthand color stop is set to off-white. If you have the Hair Shader connected to the Mix Shader's 2nd input, the problem does not occur. **Exact steps for others to reproduce the error** - Open attached blend file - Set the 3D Viewport shading to Rendered. [MixHairShaders.blend](https://archive.blender.org/developer/F11823883/MixHairShaders.blend)
Author

Added subscriber: @MrTez

Added subscriber: @MrTez
Author

After further experimentation I've found that if you control the Mix Shader factor using a Map Range node with settings From Min: 0, From Max: 1, To Min: 0, To Max: 1.1 (or any value above 1.0), and the input Value: 1, the entire strand is rendered Black. However , if you plug a Value node into the Mix Shader factor and set it to a value above 1.0 the problem does not occur.

After further experimentation I've found that if you control the Mix Shader factor using a Map Range node with settings From Min: 0, From Max: 1, To Min: 0, To Max: 1.1 (or any value above 1.0), and the input Value: 1, the entire strand is rendered Black. However , if you plug a Value node into the Mix Shader factor and set it to a value above 1.0 the problem does not occur.
Author

For info, I've checked this using the newly released version 3.0 and the problem still persists.

For info, I've checked this using the newly released version 3.0 and the problem still persists.

Added subscriber: @mano-wii

Added subscriber: @mano-wii

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

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

Thanks for the report. I edited the description to make the problem easier to understand.
In fact, that black color is curious.

Thanks for the report. I edited the description to make the problem easier to understand. In fact, that black color is curious.
Member

Added subscriber: @LukasStockner

Added subscriber: @LukasStockner
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Lukas Stockner self-assigned this 2022-10-19 02:30:50 +02:00
Member

Was already fixed by c257443192 (v3.3 and newer).

Was already fixed by c257443192 (v3.3 and newer).
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
3 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#93187
No description provided.