-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Fix: Culler not accurately culling objects #10123
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 1e0896f:
|
// dont process children if not needed | ||
if ( | ||
!container.cullableChildren | ||
|| !container.visible |
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.
I think this is incorrect. Even when a container is culled with container.visible = false, it's children's visibility must still be set independently for culling to work correctly.
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.
heya! thanks for pointing out - this should be fine - as visibility is cascaded down the scene graph when we do the transform update.
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.
looks good to me!
// dont process children if not needed | ||
if ( | ||
!container.cullableChildren | ||
|| !container.visible |
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.
heya! thanks for pointing out - this should be fine - as visibility is cascaded down the scene graph when we do the transform update.
No description provided.