-
Notifications
You must be signed in to change notification settings - Fork 24
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
Frustum culling #3
Comments
Hi Chris, since I have no concept of views or cameras within this project I don't think we should add the functionality. But you can implement a view frustum culling around the ray intersection tests within few lines as I did for example within the texturing project starting here. Note that the code starting in line 182 does:
Thanks for the offer and the interest in the project :-) I'll leave this issue open if you have further questions - feel free to ask. Cheers, |
Even though there is no concept of cameras or views, I can still imagine an interface where clipping planes are provided and the method returns all geometry that satisfies those planes. I will take a look at the referenced code. Thanks for the response! |
Sorry for the late response :-( An culling based on clipping planes specified as point normal pairs sounds indeed like a good idea.
where the planes describe a convex subspace and all faces within that space are added to the However I am currently unsure how to efficiently check if a aabb is piercing a convex subspace. |
Yes, that's exactly how I was imagining it! I think it would need to explicitly check for a convex subspace -- it should simply return no faces if it is not possible to satisfy all plane boundaries. This would return immediately in this case since the largest BB would not satisfy the plane constraints. |
Thanks for a great app for fast ray intersections! I was wondering what needs to be done in your opinion to add functionality for view frustum culling? It seems most of the constructs are in place to do this easily. I am new to this area but would be happy to take a stab at implementing it if you can provide a bit of guidance.
The text was updated successfully, but these errors were encountered: