WebXR: Frustum culling consistency #31677
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add FrustumArray usage to WebGLRenderer Previously, per-camera was the default in Renderer
… combination in tact
📦 Bundle sizeFull ESM build, minified and gzipped.
🌳 Bundle size after tree-shakingMinimal build including a renderer, camera, empty scene, and dependencies.
|
harryhjsh
force-pushed
the
webxr-frustum-culling
branch
from
4525ad5 to
e09503c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue: #31672
Description
Allow per-view culling for XR content on
WebGLRendererby backportingRendererchanges from #30830.Allow
ArrayCamerato dictate whether it should be frustum-culled per-camera, or based on its own projection matrix, withperCameraCulling. This allows XR devices with 2 views to continue using the combined projection matrix of those views for culling in a single pass in both renderers, as they did prior to #30830.More discussion in #31672.