Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
1
Found in
6000.0.59f1
6000.3.0b4
6000.4.0a1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-121344
Regression
No
Some UI Toolkit pixels are transparent when not all corners are rounded
How to reproduce:
- Open the “Reproductions.zip“ project
- Open the “SampleScene“
- Create a “UI Document” GameObject in the Hierarchy
- Assign the appropriate Panel Settings and “WindowTemplate“ UXML as Source Asset
- Unpause the Play Mode
- Slowly resize the Game view horizontally and observe the header bar at the top
Expected result: All pixels are always rendered
Actual result: Sometimes 1 or more pixels fail to render when the Game view is at a certain width
Reproducible in: 2023.1.0a1, 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- The pixels are not the physical screen pixels, but the pixels that are rendered by the UI Toolkit
- The behavior can be observed in the UI Builder window as well
- Reproducible in Play Mode, but not reproducible in the Player
- The issue can be tedious to reproduce, but it will almost always reproduce
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment