Pixel-perfect positioning of hardmask & softmask atlas about msdf-atlas-gen HOT 5 CLOSED

I'm curious to know why the plane bound construct exists.

I looked at this thread:
#47

I notice your suggested solution is to simply add planeBound (*size) to the atlasBound for each glyph to get quad placement. If I understand this math correctly, doesn't this mean calculation could be done for every single glyph once to reduce it to a single atlasBound rectangle??

The fact that there are two separate structures makes me wonder if there is a case where they would need to be handled independently at runtime. ???

from msdf-atlas-gen.

Where did I suggest to add plane bounds to atlas bounds? Plane bounds = world coordinates, atlas bounds = texture coordinates.

from msdf-atlas-gen.

I'm an idiot. I totally misread the code from the other thread, which colored my question poorly.

Ok now I see. The planeBounds is used to offset the quad in worldspace. I was previously only thinking about locating atlas position of the glyph.

Thank you!

from msdf-atlas-gen.

A fix for this issue is now available in the branch pixel-alignment. Before merging, I need to add the choice between the old and new method so that users can choose between more consistent pixel alignment and slightly more compact atlases. I'd like to also add a way to only lock alignment for just one axis as it makes much more sense to pixel-align the baseline since the glyph advances (and therefore all horizontal positions) will almost always be fractional.

from msdf-atlas-gen.