Packing result is worse when rotation allowed about free-tex-packer-core HOT 10 CLOSED

Ok. OptimalPacker now check all combos with/without rotation.

from free-tex-packer-core.

I don't think so...

Could you please give me you test assets and pack options?

from free-tex-packer-core.

I'm also seeing this, not always but often. Using MaxRectsPacker and Smart method. Can supply assets if needed privately

from free-tex-packer-core.

@odrick Sorry I can't supply assets because it's private assets, and currently have no time to give a minimal test case.

from free-tex-packer-core.

Here is one example of the gitlab diff for such a case:

Tagging @qtiki to see if he may be able to shed any light.

from free-tex-packer-core.

i've emailed source assets

from free-tex-packer-core.

Thanks. I will investigate this problem next week.

from free-tex-packer-core.

Any update here?

from free-tex-packer-core.

Ok, this is a maxrects-packer bug. Reported: soimy/maxrects-packer#14

from free-tex-packer-core.

Sorry guys for the radio silence, I've been quite busy with other stuff.

I don't think this is a bug as such. The way that these packing algorithms work is that they sort the bins based on some arbitrary rules and then try to guess the best fit locally (first-fit) to any given area. The problem is that while the guess might be a good thing locally it might cause problems later on in the packing. If the algorithm were to try all the possible combinations to find the "perfect" match it would become exponentially slower. If you're interested in more details I recommend reading the Wikipedia page Bin packing problem.

In regards to the free-tex-packer I think the best option would be to extend the OptimalPacker to try all the packing methods with and without rotation allowed (for those that support rotation that is). That would make the packing a bit slower again but will at least give the same results as manually trying to tweak every parameter. In the end the more variations we test the better the result will be, however trying to reach a "perfect" outcome is not really feasible. This is basically why I implemented the OptimalPacker that tries all the combinations instead of trying to make an exact method that solves this problem perfectly for all cases.

from free-tex-packer-core.