Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
Issue ID
1162016
Regression
Yes
EnumField control shows parts of another texture (may [not] be related to slicing in UIR)
There is a visual artifact in the UIElements' EnumField control with the latest NorthStar build. May/may not be related to slicing, which is used by the control. The arrow shows correctly (thanks to slicing), but the rest of the control background also shows strange stuff that seems to come from another portion of the cached texture. See attached image for an example (showing some green stuff behind the enum field value).
There is no easy workaround for end users.
Repro steps using Visual Scripting:
1) https://github.cds.internal.unity3d.com/unity/com.unity.visualscripting (download or clone using ssh git@github.cds.internal.unity3d.com:unity/com.unity.visualscripting.git)
The package is also a Unity project. So you can load the project directly.
2) Choose Window > Visual Script to display the Visual Scripting window
3) Click on the "Create ECS Graph" button & follow instructions
4) In the newly created graph, right-click on the graph and select "Create Node" from the contextual menu
5) Enter "Stack" in the create node search box, press Enter
6) Right-click on the stack and select "Create Node" once more
7) Enter "Instantiate" in the create node search box, press Enter
8) Press the "+ Add Component" button in the Instantiate node
9) Select any component type from the available types, press Enter
Depending on the try, you should see something in the back of the added component's enum field, as shown in the attached image. Sometimes the texture is not as bad as the attached example, but you can see something.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Add comment