You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebGLMultisampleRenderTarget was removed in #23455 and the functionality was added to WebGLRenderTarget with the new samples property. However, when using a DepthTexture attachment on a render target with multisampling enabled, the depth texture remains empty because depth is being invalidated for performance reasons regarding WebXR. This behaviour was the same with WebGLMultisampleRenderTarget, but that class had an undocumented ignoreDepthForMultisampleCopy property that allowed to preserve depth. I don't think this property was carried over in r138.
To Reproduce
Steps to reproduce the behavior:
Render a scene into a multisample render target that has a depth texture attachment.
Render the contents of the depth texture to screen.
Describe the bug
WebGLMultisampleRenderTarget
was removed in #23455 and the functionality was added toWebGLRenderTarget
with the newsamples
property. However, when using aDepthTexture
attachment on a render target with multisampling enabled, the depth texture remains empty because depth is being invalidated for performance reasons regarding WebXR. This behaviour was the same withWebGLMultisampleRenderTarget
, but that class had an undocumentedignoreDepthForMultisampleCopy
property that allowed to preserve depth. I don't think this property was carried over in r138.To Reproduce
Steps to reproduce the behavior:
Live example
Uncomment line
60
inindex.js
: SandboxExpected behavior
Depth should be preserved if the multisample render target has a depth texture attachment.
Platform:
The text was updated successfully, but these errors were encountered: