Transparent gaps between repeated textures of Visual Element background in Game view

The bug has been patched but the underlying issue remains to be fixed. Scenarios that are fixed: * The container is aligned with the pixel grid (e.g. constant pixel size, or integer scaling of 1x, 2x, 3x, etc) and the repetitions also match the pixel grid. Scenarios that are not fixed yet: * The container is not aligned with the pixel grid (e.g. a transform offsets the element by a fraction of a pixel or scales it in a way that the corners don't match the pixel grid anymore). * The panel scaling is not an integer (e.g. constant physical size does not match the pixel grid) * The repetitions don't match the pixel grid Workaround: The underlying problem is that the junctions between the repetitions currently use blending, so if they are out of alignment with the pixel grid, the junctions blend with the background. To avoid this problem, you can use a custom element that repeats the texture with the Mesh API in generateVisualContent. Alternately, if you exclude the texture from the atlas, you could also generate a single quad and use gpu tiling with UVs that are beyond the 0..1 range.

The bug has been patched but the underlying issue remains to be fixed. Scenarios that are fixed: * The container is aligned with the pixel grid (e.g. constant pixel size, or integer scaling of 1x, 2x, 3x, etc) and the repetitions also match the pixel grid. Scenarios that are not fixed yet: * The container is not aligned with the pixel grid (e.g. a transform offsets the element by a fraction of a pixel or scales it in a way that the corners don't match the pixel grid anymore). * The panel scaling is not an integer (e.g. constant physical size does not match the pixel grid) * The repetitions don't match the pixel grid Workaround: The underlying problem is that the junctions between the repetitions currently use blending, so if they are out of alignment with the pixel grid, the junctions blend with the background. To avoid this problem, you can use a custom element that repeats the texture with the Mesh API in generateVisualContent. Alternately, if you exclude the texture from the atlas, you could also generate a single quad and use gpu tiling with UVs that are beyond the 0..1 range.

The bug has been patched but the underlying issue remains to be fixed. Scenarios that are fixed: * The container is aligned with the pixel grid (e.g. constant pixel size, or integer scaling of 1x, 2x, 3x, etc) and the repetitions also match the pixel grid. Scenarios that are not fixed yet: * The container is not aligned with the pixel grid (e.g. a transform offsets the element by a fraction of a pixel or scales it in a way that the corners don't match the pixel grid anymore). * The panel scaling is not an integer (e.g. constant physical size does not match the pixel grid) * The repetitions don't match the pixel grid Workaround: The underlying problem is that the junctions between the repetitions currently use blending, so if they are out of alignment with the pixel grid, the junctions blend with the background. To avoid this problem, you can use a custom element that repeats the texture with the Mesh API in generateVisualContent. Alternately, if you exclude the texture from the atlas, you could also generate a single quad and use gpu tiling with UVs that are beyond the 0..1 range.

The bug has been patched but the underlying issue remains to be fixed. Scenarios that are fixed: * The container is aligned with the pixel grid (e.g. constant pixel size, or integer scaling of 1x, 2x, 3x, etc) and the repetitions also match the pixel grid. Scenarios that are not fixed yet: * The container is not aligned with the pixel grid (e.g. a transform offsets the element by a fraction of a pixel or scales it in a way that the corners don't match the pixel grid anymore). * The panel scaling is not an integer (e.g. constant physical size does not match the pixel grid) * The repetitions don't match the pixel grid Workaround: The underlying problem is that the junctions between the repetitions currently use blending, so if they are out of alignment with the pixel grid, the junctions blend with the background. To avoid this problem, you can use a custom element that repeats the texture with the Mesh API in generateVisualContent. Alternately, if you exclude the texture from the atlas, you could also generate a single quad and use gpu tiling with UVs that are beyond the 0..1 range.