-
-
Notifications
You must be signed in to change notification settings - Fork 35.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebGLShadowmap: Handle TwoPassDoubleSide
case
#25221
Conversation
In light of this PR, does this code block need to be changed? three.js/src/renderers/webgl/WebGLShadowMap.js Lines 280 to 288 in f296f21
|
With a quick look - it seems like it should be okay? The renderer falls back to using DoubleSided renderering with non transparent materials. But maybe it's worth being explicit? three.js/src/renderers/WebGLRenderer.js Lines 831 to 847 in 87223b8
|
@@ -28,7 +28,7 @@ function WebGLShadowMap( _renderer, _objects, _capabilities ) { | |||
|
|||
_maxTextureSize = _capabilities.maxTextureSize; | |||
|
|||
const shadowSide = { 0: BackSide, 1: FrontSide, 2: DoubleSide }; | |||
const shadowSide = { 0: BackSide, 1: FrontSide, 2: DoubleSide, 3: DoubleSide }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we do { [ FrontSide ]: BackSide, [ BackSide ]: FrontSide, ... }
here?
Rephrasing my question... Is VSM handled correctly given three.js/src/renderers/webgl/WebGLShadowMap.js Lines 280 to 288 in f296f21
FYI, see related comment. |
What I'm saying is that the render behavior for shadows with |
Thanks, @gkjohnson for your reply. I still am not a fan this design, but the code needs to be fixed, so merging. |
No description provided.