Bump node : height input value bug #45748
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#45748
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Investigating another bug related to panoramic cameras (https://developer.blender.org/T45721) we've discovered that bump nodes are not working like before.
Adding two bump nodes doesnt work. The Bump node needs a value or an RGB input into the height to work.
Here is an exemple :
and the file that goes with it :
bug_cycles_bump_node.zip
In this file you can see the suzanne on the left has a bump, and the one on the right doesnt. It's the same shader with two bumps plugged into the normals. In the official build (2.75a), bump still works on the right one...
tested on windows 7 with blender build
65c3207
Changed status to: 'Open'
Added subscriber: @MathieuAuvray
Added subscriber: @Blendify
Added subscriber: @dfelinto
Confirmed. It happens regardless of the lens type (perspective/panorama).
The example file is here as well as plain .blend: bug_cycles_bump_node.blend (packed the image and saved as compressed from within Blender)
Added subscriber: @ThomasDinges
That seems to be by design (introduced here:
b6665937
) @ThomasDinges what do you say?@MathieuAuvray I guess you know the workaround, right?
@ThomasDinges if we stick to this commit I think we should to at least mention it in the release logs (http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.76/Cycles)
I don't understand the reason of that node setup? Why would you use 2 Bump Nodes right after another?
I am fine with documenting this, however I don't see a bug here (yet). :)
Added subscriber: @nudelZ
large and small scale details for example dingto
head -> bump 1 wrinkles -> bump 2 skin pores etc
but it isn't really a bug i would say. who uses a bump node without a height value (?)
Changed status from 'Open' to: 'Archived'
Sure, you can still use 2 Bump Nodes (or more) with different values, but you need to have the Height Input connected to something.
In the screenshot example, the second bump node does nothing, it just acted as a pass through before, now it gets removed from the graph.