Parallax Occlusion Mapping #68477
Open
opened 2019-08-09 17:20:12 +02:00 by Clément Foucault
·
59 comments
No Branch/Tag Specified
blender-v4.0-release
main
temp-sculpt-dyntopo
blender-v3.6-release
universal-scene-description
blender-v3.3-release
asset-browser-frontend-split
brush-assets-project
asset-shelf
anim/armature-drawing-refactor-3
temp-sculpt-dyntopo-hive-alloc
tmp-usd-python-mtl
tmp-usd-3.6
blender-v3.5-release
blender-projects-basics
blender-v2.93-release
temp-sculpt-attr-api
realtime-clock
sculpt-dev
gpencil-next
bevelv2
microfacet_hair
xr-dev
principled-v2
v3.6.4
v3.6.3
v3.3.11
v3.6.2
v3.3.10
v3.6.1
v3.3.9
v3.6.0
v3.3.8
v3.3.7
v2.93.18
v3.5.1
v3.3.6
v2.93.17
v3.5.0
v2.93.16
v3.3.5
v3.3.4
v2.93.15
v2.93.14
v3.3.3
v2.93.13
v2.93.12
v3.4.1
v3.3.2
v3.4.0
v3.3.1
v2.93.11
v3.3.0
v3.2.2
v2.93.10
v3.2.1
v3.2.0
v2.83.20
v2.93.9
v3.1.2
v3.1.1
v3.1.0
v2.83.19
v2.93.8
v3.0.1
v2.93.7
v3.0.0
v2.93.6
v2.93.5
v2.83.18
v2.93.4
v2.93.3
v2.83.17
v2.93.2
v2.93.1
v2.83.16
v2.93.0
v2.83.15
v2.83.14
v2.83.13
v2.92.0
v2.83.12
v2.91.2
v2.83.10
v2.91.0
v2.83.9
v2.83.8
v2.83.7
v2.90.1
v2.83.6.1
v2.83.6
v2.90.0
v2.83.5
v2.83.4
v2.83.3
v2.83.2
v2.83.1
v2.83
v2.82a
v2.82
v2.81a
v2.81
v2.80
v2.80-rc3
v2.80-rc2
v2.80-rc1
v2.79b
v2.79a
v2.79
v2.79-rc2
v2.79-rc1
v2.78c
v2.78b
v2.78a
v2.78
v2.78-rc2
v2.78-rc1
v2.77a
v2.77
v2.77-rc2
v2.77-rc1
v2.76b
v2.76a
v2.76
v2.76-rc3
v2.76-rc2
v2.76-rc1
v2.75a
v2.75
v2.75-rc2
v2.75-rc1
v2.74
v2.74-rc4
v2.74-rc3
v2.74-rc2
v2.74-rc1
v2.73a
v2.73
v2.73-rc1
v2.72b
2.72b
v2.72a
v2.72
v2.72-rc1
v2.71
v2.71-rc2
v2.71-rc1
v2.70a
v2.70
v2.70-rc2
v2.70-rc
v2.69
v2.68a
v2.68
v2.67b
v2.67a
v2.67
v2.66a
v2.66
v2.65a
v2.65
v2.64a
v2.64
v2.63a
v2.63
v2.61
v2.60a
v2.60
v2.59
v2.58a
v2.58
v2.57b
v2.57a
v2.57
v2.56a
v2.56
v2.55
v2.54
v2.53
v2.52
v2.51
v2.50
v2.49b
v2.49a
v2.49
v2.48a
v2.48
v2.47
v2.46
v2.45
v2.44
v2.43
v2.42a
v2.42
v2.41
v2.40
v2.37a
v2.37
v2.36
v2.35a
v2.35
v2.34
v2.33a
v2.33
v2.32
v2.31a
v2.31
v2.30
v2.28c
v2.28a
v2.28
v2.27
v2.26
v2.25
Labels
Clear labels
This issue affects/is about backward or forward compatibility
Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports
Apply labels
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
This issue affects/is about backward or forward compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
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
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
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
Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports
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 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 & 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
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
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
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Set Project
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
52 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#68477
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Using the same thechnique as High Quality Bump, we should be able to implement Parallax Occlusion Mapping.
This could be done auto-magically when plugging nodes to the displacement socket or by using a new node.
Details to be decided.
Estimate : 2 weeks
Added subscriber: @fclem
Added subscriber: @Jeroen-Bakker
Added subscriber: @zebus3dream
Added subscriber: @Blendork
Added subscriber: @Reoxur
Added subscriber: @bent
Added subscriber: @ucupumar
Added subscriber: @MACHIN3
Added subscriber: @lemenicier_julien
Added subscriber: @RosarioRosato
Added subscriber: @MD.FahadHassan
Added subscriber: @AntonioJavierTorralbaMoreno
Added subscriber: @Firepal
Added subscriber: @mastajappa
Added subscriber: @Nakara
Added subscriber: @KenzieMac130
I'm curious as to how this feature would work with arbitrary geometry. Parallax occlusion is a trick that relies heavily on proper tangents and faking depth with UV distortion, a system that does it automatically would need to know the context behind how a texture is mapped and how geometry is set up to clip for silhouette, plus offsetting fragment depth to fix flat intersections.
Maybe an automatic system to do this could work, but I'm not sure how wise it would be given the complex nature of this (hacky) effect.
It seems to me like a better solution might be to:
This approach would also allow the user to combine parallax mapping to create deep layered materials (ice frozen over rock, crystals with internal structure, etc.) and reduce the software engineering burden of creating another "smart" black-boxed feature that fails to satisfy additional needs.
Added subscriber: @temeddix
@astrand130 I don't see how the simplified workflow version is orthogonal to the implementation you suggest.
The "magic" implementation I suggest is just adding some invisible node and replace all UV links by the deformed UV. This is what we do for the displacement socket.
Of course we would still have a dedicated parallax node to only modify certain texture coordinates.
That's something I'm still thinking about. Since we can use any mapping we don't need tangents and normals unless we are using UVs but in this case the dFdx ones should suffice. But the arbitrary mapping is a hard one to figure out.
To my knowledge silhouette clipping is just a depth offset of 1 making the fragment always fail the depth test.
I think the silhouette clipping and depth offset are a secondary target that should be considered after the initial POM implementation.
Just to be clear it is the displacement technique used in Marmoset Toolbag .
Added subscriber: @ZackMercury-2
Added subscriber: @ViktorJamrich
Added subscriber: @Lolme3
Added subscriber: @Grady
This feature would also be pretty useful to have in Cycles too. Even though one could in theory render for example a brick path with displacement maps and a heavily subdivided piece of geometry, being able to use a lower polygon flat piece of geometry with just an illusion of depth would be much more efficient. And if Eevee is going to get this feature at some point, having it in Cycles too would allow for more consistency between the two render engines for switching back and forth between them.
Added subscriber: @Kdaf
Added subscriber: @YegorSmirnov
Added subscriber: @rogper
Added subscriber: @TakingFire
Added subscriber: @RedMser
Added subscriber: @imad
Added subscriber: @AlexanderWilms
Added subscriber: @Hyudan
Added subscriber: @mmoeller
Added subscriber: @juang3d
This comment was removed by @juang3d
Added subscriber: @JacobMerrill-1
https://www.youtube.com/watch?v=LPs1RW1QKG0
I can't wait !
I used the method by Ben and it's expensive resource wise for realtime but fun to work with !
https://www.blendernation.com/2020/10/11/realtime-shader-displacement-for-eevee/
Added subscriber: @Low_Polygon42
Added subscriber: @SeanLewis
Added subscriber: @mortom_ckm
Added subscriber: @Emi_Martinez
Added subscriber: @gintszilbalodis
Added subscriber: @MaciejMorgas
Added subscriber: @EDAN
Added subscriber: @softyoda
Added subscriber: @Defka
Added subscriber: @GeorgiaPacific
Added subscriber: @moth3r
Added subscriber: @intracube
Added subscriber: @LinoThomas
Added subscriber: @pauanyu_blender
Added subscriber: @Macilvoy
Added subscriber: @Guilherme-Emerich-Setubal
Added subscriber: @Max-49
Added subscriber: @dursunumit
thank you :)
Added subscriber: @htuncay-4
Added subscriber: @Nika-Kutsniashvili