Search Issue Tracker
Fixed
Fixed in 2022.3.8f1, 2023.1.9f1, 2023.2.0b5, 2023.3.0a1
Votes
0
Found in
2022.2.19f1
2023.1.0b18
2023.2.0a16
2023.3.0a1
Issue ID
UUM-36753
Regression
No
Transparent gaps between repeated textures of Visual Element background in Game view
Reproduction steps:
1. Open the attached project “UI_Builder“
2. Look at the Background of “VisualElementTest“ in the UI Builder
3. Look at the Background of “VisualElementTest“ in Game view when it’s set to Free Aspect
Expected result: The background looks the same in UI Builder and Game view
Actual result: In the Game view, the background has transparent lines between the repeated textures
Reproduced with: 2022.2.19f1, 2023.1.0b18, 2023.2.0a16
Couldn’t test with: 2020.3.47f1 (UI Builder not implemented), 2021.3.26f1 (can’t repeat texture)
Reproduced on: macOS 13.0.2 (Intel), macOS 13.3 (M1)
Notes:
- Transparent gaps are not visible in Player nor when Game view is set to a specific resolution
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Resolution Note (fix version 2023.3.0a1):
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.
Resolution Note (fix version 2023.2.0b5):
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.
Resolution Note (fix version 2023.1.9f1):
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.
Resolution Note (fix version 2022.3.8f1):
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.