Possible bug with atlas?

[eddieone]

I noticed an atlas was showing an extra pixel below but the json file seems correct. Is this a bug or am I missing something? I have attached examples, so it's clear what I am talking about.

{
	"filename": "potter.png",
	"frame": {"x":0,"y":0,"w":60,"h":27},
	"rotated": false,
	"trimmed": false,
	"spriteSourceSize": {"x":0,"y":0,"w":60,"h":27},
	"sourceSize": {"w":60,"h":27}
}

 

 

There's an older post where someone reported a similar issue. Maybe padding is a workaround, I will try that.

[rich]

This is a common issue with texture atlases (in all game frameworks, not just Phaser) where pixels from other frames in the atlas bleed through, because they're packed too tightly, and the bilinear filtering samples other pixels along with the actual frame you want. Texture Packer, and apps like it, have padding and border features built-in to mitigate it.

[eddieone]

oh I see. Thanks