Clarification of the padding parameters - No difference at all?

[alexdesander]

In the cli tool, there's -pxpadding and -outerpxpadding.

Now, when I compare images generated with:

./msdf-atlas-gen -font OpenSans-Regular.ttf -imageout atlas.png -json atlas.json -size 128 -charset charset.txt -pots -pxpadding 4 -pxrange 4

and

./msdf-atlas-gen -font OpenSans-Regular.ttf -imageout atlas.png -json atlas.json -size 128 -charset charset.txt -pots -outerpxpadding 4 -pxrange 4

The difference in the resulting pngs seems to be non existent. By checking the difference visually on https://www.diffchecker.com/image-compare/, I see no change at all.

Is it supposed to be that way?

Also, is there some way to get true padding in the atlas? By true padding I mean, real NULL value segments between glyphs. Currently, there seems to be no way to do that. I am asking because I'm debug-showing the whole msdf atlas and the bleeding is pretty apparent when using a linear interpolation texture sampler.

[alexdesander]

Mhh, thinking about it, could it be that the paddings only modify the output json (in my case)?

[alexdesander]

Update: Yes, the paddings modify only the associated atlas bounds in the output json. This will also fix the bleeding when actually rendering glyphs (rendering the whole atlas is not something you need to be perfect anyway).

Now it also is apparent to me why the shapes in the distance field atlas "grow" and why there's no real NULL borders - probably because this could ruin the sampling or something.