Region taken from AtlasTexture is inaccurate if taken from edge

[jgodfrey]

Godot version: 3.2.stable.official

OS/device including version: Windows 10

Issue description: I've seen a few instances where extracting a manually defined region from an AtlasTexture "extends" pixels found at the edges of the texture. See attached image for an idea of what I mean here.

Steps to reproduce: Add a Sprite to a scene and then manually define a region from an AtlasTexture for the sprite's texture. Be sure the defined region is at the top edge of the atlas. Now, manually extend the region above the (apparent) top edge of the atlas. The sprite will show a smear of pixels extending from the ones that touch the top edge (I think?).

Minimal reproduction project:

[jgodfrey]

Actually, in the attached image, you'll notice a similar smear off the 9'oclock position, as that edge of the region also extends slightly off the left-edge of the atlas...

[dankan1890]

Can you provide a minimal reproduction project? to speed up the resolution of the issue :)

[tom-jk]

Can reproduce in 3.2.2.stable on linux mint 18.3.

Screenshot:

Minimal reproduction project: 36059.zip

Is this a bug in practice? You can avoid the smear by ensuring you properly frame the subsprites (or have a pixel width's clearance), which normally you would do anyway, or alternatively choose one of the repeat/mirror modes.

[Calinou]

We should find a suitable place to document this limitation (which tends to be common to all 2D renderers out there, not just Godot). Which page/class should this information be added to?

[KoBeWi]

Region editor now displays texture bounds:

(although it's poorly visible with grid enabled)

What happens when you exceed that region is a typical behavior when texture is sampled beyond its size. Depending on settings, it can result in stretching or repeat. You can observe the same behavior with Sprite2D's region etc. I wonder if we could have something like clamped mode, where the texture is simply cut at the edges.