Conversation
* AABB vs AABB * AABB vs Point * AABB vs Sphere * AABB contains AABB
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
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.
AABB functions:
New features for sphere:
I used
glm_aabb_aabbfor testing intersection, it could beglm_aabb_intersectorglm_aabb_intrbut since for instanceglm_aabb_pointis used instead ofglm_aabb_intersect_pointsame convention is also used for aabb.Sphere Representation in cglm is vec4: [center.x, center.y, center.z, radii], functions will accept vec4 instead of two parameter for each sphere e.g . vec3 for center and float for radius. It is combined into vec4 in cglm.
If you have better idea or don't like this design please let me know.