Search Issue Tracker
Fixed
Fixed in 2021.3.38f1, 2022.3.25f1, 2023.2.20f1, 6000.0.0b15
Votes
0
Found in
2021.3.37f1
2022.3.21f1
2023.2.12f1
6000.0.0b13
7000.0.0a1
Issue ID
UUM-68128
Regression
No
UI Toolkit is not rendered in the editor when using Mesa LLVMpipe
How to reproduce:
1. Create a new project with any template
2. Open the Scene view
3. Oberve the toolbar
Expected result: The toolbar is rendered
Actual result: A black rectangle filling the toolbar is rendered
Reproduced with: 2022.3.21f1, 2023.2.12f1
Not reproduced with: 2021.3.16f1
Could not test with: 6000.0.0b13 (Issue not reproduced locally)
Reproduced on: Ubuntu 22.054 (by reporter)
Not reproduced on: Windows 11, Ubuntu 20.04
GPU reproduced with:
- NVIDIA A100 with LLVMpipe (by reporter)
- Freshly installed Ubuntu 22.04 VM with VirtualBox (LLVMpipe)
GPU not reproduced with: Radeon PRO WX 5100, Nvidia GTX 1080, Nvidia RTX 2080, NVIDIA GeForce RTX 3050 Ti Laptop GPU
Notes:
1. CQA could not reproduce the issue locally
2. Could not find regression point as the issue is not reproducible locally
3. Even though the toolbar is not rendered the menus can still be clicked and used
Workaround: In Project Settings/Quality, set Anisotropic Textures to "Per Texture" instead of "Forced ON", or make sure you're using a quality level that doesn't use "Forced ON".
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 6000.0.0b15):
Text might still look blurry when Anisotropic Filtering is forced in the Quality Settings because of the implementation in LLVMpipe.