fresnel and layer weight are producing inverted output on bump/normal #87211
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#87211
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?
System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92
Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-03-31 07:46, hash:
645fc0c767Worked: (newest version of Blender that worked as expected)
Short description of error
geometry is white for grazing angles, and black for facing when using fresnel or layer weight nodes. bump is black for grazing and white for facing (inverted).
fresnel inverted on bump.blend
Added subscriber: @3di
Added subscriber: @mano-wii
I'm not sure I understand the problem. The bump value in the example shown is very strong, and for me the result is the expected one.
It would be interesting if you could show in image how it should be.
i've exagurated the bump so it's more obvious which bit is facing the camera (the flat bit). So here the flat part of the bump is white. It should be black. Only the sides of the bump should be white, but they're black.
Added subscriber: @fu5ha
Looking closely at the output, it looks 100% correct to me. The "flat" part of the bump is simply following how fresnel looks for a sphere, as it should. The sides of the bump which are facing back towards the camera are therefore black. And the sides that are facing away from the camera fall off steeply enough that you cannot see them properly from the camera's view. The areas where you can see them look as expected.
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Needs User Info'
Here are two renders of the same part with an annotation marking the ridge (Local maximum value of the height map). The right part of the ridge is facing the camera and the left is facing away from it. So the shading is correct. Does that sound reasonable?
Just checked in 3.1 and yes, the issue now appears to have been resolved:
Changed status from 'Needs User Info' to: 'Archived'