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

Individual Meshes #14

Closed
TheNeikos opened this issue Sep 14, 2020 · 2 comments
Closed

Individual Meshes #14

TheNeikos opened this issue Sep 14, 2020 · 2 comments

Comments

@TheNeikos
Copy link
Contributor

TheNeikos commented Sep 14, 2020

Currently, each chunk uses its own mesh. Could this be optimized? Depending on Orientation the mesh stays the same. Right now the position is also encoded in the mesh itself, this seems rather wasteful in terms of memory transfer+usage to me.

Is there a way to reuse parts of this across chunks, and decouple the offset from the mesh itself? (Related to #3?)

@StarArawn
Copy link
Owner

Ideally we have a better way of specifying number of chunks and the size of the chunks. For really large maps or maps that are changed quite frequently I can see it being beneficial to chunk things up, but for smaller maps or maps that don't ever change having a single draw call/mesh would be much more ideal. As for positioning the only position that gets "encoded" in the mesh is the local position of each vertices. I don't see a way of improving the memory usage there.

@dmtaub
Copy link
Collaborator

dmtaub commented Mar 15, 2021

The best way to do this would be leveraging the work put into bevy_tilemap. Issue here: #40

@dmtaub dmtaub closed this as completed Mar 15, 2021
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

No branches or pull requests

3 participants