Use modern functions for VAO attributes - #1702
Merged
Merged
Conversation
…nctions and single vao per vertex type when available
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
1 participant
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.
Use modern functions for VAO attributes when supported. Refactors VAO/VBO combinations into VertexPipeline class. Requires 4.5 or GL_ARB_direct_state_access. This allows Helion to only allocate one VAO per vertex type instead of needing to allocate a VAO for every VBO. Support is checked and will fallback to the old VAO for every VBO that was used previous so older GPUs will still function.
Moves debug label creation to a debug flag since it's really only required for debugging in RenderDoc.