bump node doesn't work with SSS shader #47681

Closed
opened 2016-03-04 02:39:18 +01:00 by Bubble Bobble · 12 comments

System Information
Windows 7, nvidia Quadrio 1000m

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: 2.76 at least, possibly previous daily builds before 2.77 RC1

Short description of error
SSS shader is not affected by bump node

Exact steps for others to reproduce the error
make an object with an SSS shader, put some kind of bump node into it

attached blend showing problem: bump SSS.blend

Also to mention, I went into this wanting to replicate a problem I saw with SSS reflecting black spots into glossy shaders, that's why there is a glossy plane below the SSS sphere. I think that problem may still be there also but in attempting to make a test file to show the issue, I noticed that SSS bump is not working. The other issue that I noticed before RC1 was that SSS objects with normal displacement reflect black spots into glossy shaders.

**System Information** Windows 7, nvidia Quadrio 1000m **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) Worked: 2.76 at least, possibly previous daily builds before 2.77 RC1 **Short description of error** SSS shader is not affected by bump node **Exact steps for others to reproduce the error** make an object with an SSS shader, put some kind of bump node into it attached blend showing problem: [bump SSS.blend](https://archive.blender.org/developer/F287032/bump_SSS.blend) Also to mention, I went into this wanting to replicate a problem I saw with SSS reflecting black spots into glossy shaders, that's why there is a glossy plane below the SSS sphere. I think that problem may still be there also but in attempting to make a test file to show the issue, I noticed that SSS bump is not working. The other issue that I noticed before RC1 was that SSS objects with normal displacement reflect black spots into glossy shaders.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @JimCantley

Added subscriber: @JimCantley
Author

Sorry guys, I can't seem to edit my post. The version this happens on is 2.77 RC b594b25 branch: HEAD. If anyone can edit my post, feel free. Many thanks in advance for the hard work.

"You do not have permission to edit this object.
Users with the "Can Edit" capability:

Members of the project "Moderators" can take this action.
The owner of a task can always view and edit it."

Can I have permission to edit my own posts? I've wanted to go back to clarify before but am never able.

Sorry guys, I can't seem to edit my post. The version this happens on is 2.77 RC b594b25 branch: HEAD. If anyone can edit my post, feel free. Many thanks in advance for the hard work. "You do not have permission to edit this object. Users with the "Can Edit" capability: Members of the project "Moderators" can take this action. The owner of a task can always view and edit it." Can I have permission to edit my own posts? I've wanted to go back to clarify before but am never able.

Added subscriber: @Sergey

Added subscriber: @Sergey
Sergey Sharybin self-assigned this 2016-03-04 08:49:33 +01:00

This is more like a SVM vs. OSL shading difference. I don't see regression in behavior, but i do see following issues:

  • OSL does not support bump mapping
  • Both SVM and OSL have fireflies

Those issues i'm looking into now.

As for permission to edit reports (it's not a forum, we don't have posts ;) it's a bit tricky to grant you ability to edit only own tasks, but it's on a TODO. You can search for a corresponding task here.

This is more like a SVM vs. OSL shading difference. I don't see regression in behavior, but i do see following issues: - OSL does not support bump mapping - Both SVM and OSL have fireflies Those issues i'm looking into now. As for permission to edit reports (it's not a forum, we don't have posts ;) it's a bit tricky to grant you ability to edit only own tasks, but it's on a TODO. You can search for a corresponding task here.

Fireflies are caused by changed default for the light -- it is now uses MIS by default. In order to have same behavior as in 2.76 you can simply disable MIS for now. Surely those fireflies are to be investigated still. It's not a regression tho, so not a stopper for RC2.

Fireflies are caused by changed default for the light -- it is now uses MIS by default. In order to have same behavior as in 2.76 you can simply disable MIS for now. Surely those fireflies are to be investigated still. It's not a regression tho, so not a stopper for RC2.
Author

Sergey, thank you very much! I don't use OSL for all projects but sometimes it is helpful. I have it turned on in my default blend file.

Turning it off fixes things up. I didn't think it would work like that, I thought it was more of an addition rather than an overall change. Surely this is some kind of problem though, no? For people that want to use OSL and bump on SSS that is a bit of a dilemma.

Either way, I appreciate the response and help to fix things, thank you!

Sergey, thank you very much! I don't use OSL for all projects but sometimes it is helpful. I have it turned on in my default blend file. Turning it off fixes things up. I didn't think it would work like that, I thought it was more of an addition rather than an overall change. Surely this is some kind of problem though, no? For people that want to use OSL and bump on SSS that is a bit of a dilemma. Either way, I appreciate the response and help to fix things, thank you!

Added subscriber: @brecht

Added subscriber: @brecht

The fireflies when enabling MIS are from caustics, sharp highlights in the glossy floor visible through diffuse reflections. The solution there is to disable caustics or use filter glossy, that's not a bug.

The fireflies when enabling MIS are from caustics, sharp highlights in the glossy floor visible through diffuse reflections. The solution there is to disable caustics or use filter glossy, that's not a bug.

This issue was referenced by 5adfdd965a

This issue was referenced by 5adfdd965a3a9e7f52fa282a892a123f8ed66c5a

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

This issue was referenced by blender/cycles@8c49cd604b

This issue was referenced by blender/cycles@8c49cd604be706e8835b91c3171384064e5cce6d
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#47681
No description provided.