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.

Sign up for GitHub

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

Jump to bottom

VBO capacity is hardcoded #3

Open
sheaconlon opened this issue Jul 19, 2017 · 2 comments
Open

VBO capacity is hardcoded #3

sheaconlon opened this issue Jul 19, 2017 · 2 comments
Labels
major bug
Milestone
Version 0.01

Comments

@sheaconlon
Copy link
Owner

The capacity of the FloatBuffers underlying VertexBufferObjects should not be hardcoded. Instead, some sort of quad limits and entity limits should be imposed.
@sheaconlon sheaconlon added this to the Version 0.01 milestone Jul 19, 2017
@sheaconlon
Copy link
Owner Author

Actually, rather than imposing limits on the number of Quads a WorldObject can have and the number of Entitys a Chunk can have, the Prerenderer can split vertex data for a Chunk across multiple VertexBufferObjects when needed. This will avoid the problem of arbitrary limits.

@sheaconlon
Copy link
Owner Author

Defer until #5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
major bug
Projects
None yet
Milestone
Version 0.01
Development

No branches or pull requests
1 participant
@sheaconlon