[FR]customDepthMaterial support for `onBeforeRender`
See original GitHub issueIs your feature request related to a problem? Please describe.
Possibility to use a shared material for customDepthMaterial
while changing uniforms on a per object basis
Describe the solution you’d like
add support for onBeforeRender
to WebGLShadowMap
You would expect onBeforeRender
to work just like it does for normal object rendering.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
Object3D: Introduce onBeforeShadow(). · Issue #14921 - GitHub
Right, but each object can clone the custom depth material, correct? ... [FR]customDepthMaterial support for onBeforeRender #22937.
Read more >Object3D#onBeforeRender – three.js docs
Custom depth material to be used when rendering to the depth map. ... Note: This method does not support scene graphs having non-uniformly-scaled...
Read more >Unreal Engine 4 Tutorial - Custom Depth - YouTube
In this game art episode I explain what scene depth is and how we can use custom depth in our games. Support me...
Read more >Custom Depth in Unreal Engine - Tom Looman
Get the material files for immediate use in Unreal Engine! Supports up to 4 colors out of the box (theoretically 255 colors supported...
Read more >Render Custom Depth on Nanite enabled not working
The material I am using is a basic highlight/outline material I found while following a tutorial. I will look into the custom depth...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Agree. Sorry i did not find the other issue first. Will reply there to mention i need it too
Just because the discussion in #14921 is stalled does not mean the feature request is not accepted. It’s in general better to post at existing open issues than creating a new one for the same topic.