-
Notifications
You must be signed in to change notification settings - Fork 409
-
Notifications
You must be signed in to change notification settings - Fork 409
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
TextureAtlas
isn't using space efficiently
#5986
Labels
Comments
The algorithm that's chosen here should also consider being able to remove areas from the atlas. This is something that blocks us from using these atlases for larger more-ephemeral textures like avatars and beatmap/carousel backgrounds. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suppose we have 2 textures to be added into the atlas: one is wide and another is tall (images 1 & 2). Now if we want to add another texture - it should be very small to fit with the current implementation (3), otherwise new atlas will be created (4).
The issue is that the huge empty atlas area is being unused.
Implementing some sort of packing algorithm would probably be an overkill, but there should be at least some simple approach to make things better.
Relevant code
Test scene to play around with
The text was updated successfully, but these errors were encountered: