Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2021.3.30f1
2022.3.8f1
2023.1.12f1
2023.2.0b8
2023.3.0a4
Issue ID
UUM-48124
Regression
No
[UI Builder] Rendering artifacts when resizing UI Builder Inspector window
How to reproduce:
1. Open the attached "UIBuilderBug" project
2. Make sure that the UI Builder tab is open
3. Try resizing the Inspector window in the UI Builder window
Expected results: No rendering artifacts are visible when resizing the UI Builder's Inspector window
Actual results: Rendering artifacts are visible when resizing the UI Builder's Inspector window
Reproducible with: 2021.3.30f1, 2022.3.8f1, 2023.1.12f1, 2023.2.0b8, 2023.3.0a4
Platforms tested/reproducible with: macOS Apple M1 Max (Ventura 13.4.1)
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
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future. In this specific case, we made sure that there was no data loss, and that the unintended result did not cause more visual (or non-visual) damage beyond the artifact.
Resolution Note (2023.3.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future. In this specific case, we made sure that there was no data loss, and that the unintended result did not cause more visual (or non-visual) damage beyond the artifact.