Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.2.12f1
2023.3.0b9
Issue ID
UUM-64597
Regression
No
Visual artifacts can be observed in the Editor when using “OpenGLES3”, “OpenGLES2”, and “OpenGLCore” Graphics APIs on AMD GPUs
How to reproduce:
1. Open the “Black Editor“ project
2. Make sure to switch the Graphics API to “OpenGLES3”, “OpenGLES2”, or “OpenGLCore” for the platform that the Editor is running on (File > Build Settings > Player Settings > Player > Other Settings)
3. Observe the Editor
Expected result: The Editor renders without any visual artifacts
Actual result: Some windows are rendered as a black texture while other components flicker
Reproduced with: 2021.3.35f1, 2022.3.20f1, 2023.2.12f1, 2023.3.0b9
Reproduced on: Windows 10 (by reporter), Windows 11
Not reproduced on: macOS 14.1.1 (M2), Ubuntu 20.04
GPU Reproduced with: AMD Radeon RX 7900 XTX (Windows 11), AMD Ryzen 3 5425U with Radeon Graphics (Windows 10)
GPU Not Reproduced with: NVIDIA GeForce RTX 3050 Ti Laptop GPU (Windows 11), Apple M2 Ultra (60 cores) (macOS 14.1.1 (M2)), AMD Radeon PRO WX 5100 (Ubuntu 20.04), AMD Ryzen 3 5425U with Radeon Graphics (Linux) (by reporter)
Notes:
1. A video is attached in the internal comments showcasing the issue
2. This seems to affect AMD GPUs
3. Not reproducible with “Direct3D11”, “Direct3D12”, “Vulkan”, and “Metal” Graphics APIs
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
Thank you for reporting the bug. We would recommend using DirectX11, 12 or Vulkan on Desktop PCs. Please let us know if you have an issue with any of these APIs.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.