Bump Node Outputting Pure Black #53518

Closed
opened 2017-12-09 00:46:48 +01:00 by Joey Bennett · 9 comments

System Information
Windows 7
EVGA GeForce GTX 770 Classified 4GB GPU
2x Intel Xeon E5-2670 8-cre 2.6 Ghz
8 GB ADATA RAM @1833Mhz

Blender Version
Broken: Blender 2.79a (Hash: 5bd8ac9) and Blender 2.79.1 (Hash: 2ae6a93)
Worked: N/A

Short description of error
In short, I don't know for sure if it's a bug, or an intended limitation of Cycles nodes. I have over like 450 nodes, and the bump no longer works when certain ones are plugged into it, and instead acts as if it's a black emission node, as does the Principled BSDF if the Bump node is connected.
It's worth noting I had a friend test on his rig, and his own blender version, and it didn't work for him either.

Exact steps for others to reproduce the error
Just download the .blend, and it's already done for you. To "fix" it, simply delete the Reroute marked "REMOVE ME" or the Reroutes labelled "OR REMOVE US". steel_shader_002.blend

**System Information** Windows 7 EVGA GeForce GTX 770 Classified 4GB GPU 2x Intel Xeon E5-2670 8-cre 2.6 Ghz 8 GB ADATA RAM @1833Mhz **Blender Version** Broken: Blender 2.79a (Hash: 5bd8ac9) and Blender 2.79.1 (Hash: 2ae6a93) Worked: N/A **Short description of error** In short, I don't know for sure if it's a bug, or an intended limitation of Cycles nodes. I have over like 450 nodes, and the bump no longer works when certain ones are plugged into it, and instead acts as if it's a black emission node, as does the Principled BSDF if the Bump node is connected. It's worth noting I had a friend test on his rig, and his own blender version, and it didn't work for him either. **Exact steps for others to reproduce the error** Just download the .blend, and it's already done for you. To "fix" it, simply delete the Reroute marked "REMOVE ME" or the Reroutes labelled "OR REMOVE US". [steel_shader_002.blend](https://archive.blender.org/developer/F1350111/steel_shader_002.blend)
Author

Added subscriber: @JoeyBennett

Added subscriber: @JoeyBennett

Added subscriber: @FloridaJo

Added subscriber: @FloridaJo

Change this node from Multiply to Mix.
See if that fixes it for you. Everything else besides Mix, makes it black.
In the meantime, I'll see if I can recreate with a simpler set up.

nodebug.png

Change this node from Multiply to Mix. See if that fixes it for you. Everything else besides Mix, makes it black. In the meantime, I'll see if I can recreate with a simpler set up. ![nodebug.png](https://archive.blender.org/developer/F1367408/nodebug.png)

@JoeyBennett Joey, I started reducing this bug, but it's a massive node layout, can you do that? Delete things until you get to the minimum node setup where that still is outputting black?

@JoeyBennett Joey, I started reducing this bug, but it's a massive node layout, can you do that? Delete things until you get to the minimum node setup where that still is outputting black?
Member

Added subscriber: @GregZaal

Added subscriber: @GregZaal
Member

For me this prints an error in the console: Cycles: out of SVM stack space, shader "Steel" too big.

For me this prints an error in the console: `Cycles: out of SVM stack space, shader "Steel" too big.`

Added subscriber: @Sergey

Added subscriber: @Sergey

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2017-12-11 16:47:39 +01:00

Thanks for the report, but it is a known limitation. Your shader requires too many stack variables for the shader machine. While re-route nodes doesn't necessarily require extra stack space, having them in shader graph changes the way how graph is being travesred.

There is some ongoing development to optimize stack usage, but is not all finished yet. See D1676.

Thanks for the report, but it is a known limitation. Your shader requires too many stack variables for the shader machine. While re-route nodes doesn't necessarily require extra stack space, having them in shader graph changes the way how graph is being travesred. There is some ongoing development to optimize stack usage, but is not all finished yet. See [D1676](https://archive.blender.org/developer/D1676).
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
4 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#53518
No description provided.