sbrl/SpritePacker
1
0
Fork 0
Code Issues 2 Pull requests Activity

Algorithm Improvements #1

New issue
Open
opened 2016-05-21 14:54:58 +00:00 by sbrl · 1 comment
sbrl commented 2016-05-21 14:54:58 +00:00
Owner
Copy link

Although the current packing algorithm is OK, we need to improve it to make it even better.

Currently, the algorithm uses X and Y scanlines that radiate out from (0, 0). It checks the X scanline first, and then it checks the Y scanline. It should instead find and store the first place found on both axes, and pick best one out of the two.

Here's an example packing result:

Example result

It might be worth noting that normally, you wouldn't give it so many different awkwards shapes.

It might also be worth noting that the algorithm hasn't been check to make sure it handles non-square images correctly. Some of the placement errors may have occurred due to the fact that the input images were not square.

Although the current packing algorithm is OK, we need to improve it to make it even better. Currently, the algorithm uses X and Y scanlines that radiate out from (0, 0). It checks the X scanline first, and then it checks the Y scanline. It should instead find and store the first place found on both axes, and pick best one out of the two. Here's an example packing result: ![Example result](http://i.imgur.com/M8byahl.png) It might be worth noting that normally, you wouldn't give it so many different awkwards shapes. It might also be worth noting that the algorithm hasn't been check to make sure it handles non-square images correctly. Some of the placement errors may have occurred due to the fact that the input images were not square.
sbrl commented 2016-05-21 14:59:27 +00:00
Author
Owner
Copy link

I've just noticed that the 48x32 image near the bottom is potentially overlapping with the 80x128 image. We can't be having that! We definitely need to test this thing some more.

I've just noticed that the 48x32 image near the bottom is potentially overlapping with the 80x128 image. We can't be having that! We definitely need to test this thing some more.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v0.1
Labels
Clear labels   
Bug

   
Enhancement
No labels
Bug
Enhancement
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: sbrl/SpritePacker#1
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?