Skip to content
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

Implement hierarchical depth culling for meshlets #87

Merged
merged 12 commits into from
Aug 3, 2024

Conversation

sndels
Copy link
Owner

@sndels sndels commented Jul 29, 2024

No description provided.

@sndels sndels force-pushed the cluster-depth-culling branch 2 times, most recently from b882fd1 to bb9b176 Compare August 3, 2024 07:56
sndels added 2 commits August 3, 2024 11:30
Makes it easier to grep where it's being used and cleans up ctor
interfaces to the bare essentials.
@sndels sndels force-pushed the cluster-depth-culling branch 2 times, most recently from e3114f6 to 1be8a90 Compare August 3, 2024 08:54
@sndels sndels force-pushed the cluster-depth-culling branch from 1be8a90 to 9c635e8 Compare August 3, 2024 08:56
Isn't conservative for disocclusion yet. That needs the two-pass setup
from Aaltonen.
@sndels sndels force-pushed the cluster-depth-culling branch from 9c635e8 to fe956d6 Compare August 3, 2024 10:48
sndels added 3 commits August 3, 2024 13:51
Also move meshlet culler as a init input to the geometry renderers
because the same instance is always passed in. Similarly, have the
geometry renderers own hierarchical depth history to keep it contained
where it is needed.
Can't modify a value twice between sequence points.
Link times go from almost 10s down to 1.5s
@sndels sndels force-pushed the cluster-depth-culling branch from fe956d6 to 608b198 Compare August 3, 2024 10:51
@sndels sndels merged commit 608b198 into master Aug 3, 2024
6 checks passed
@sndels sndels deleted the cluster-depth-culling branch August 3, 2024 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant