Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.3.17f1
Issue ID
UUM-60282
Regression
Yes
The Editor is all white when a project with a lot of textures is opened after deleting the Library folder in the project folder
How to reproduce:
# Open the “WhiteScreen.zip“ project
# Open the “SampleScene”
# Launch the attached script from the top toolbar (Tools > Create Textures) (The Editor will close itself afterward)
# In the project folder, delete the Library folder
# Open the project again
# Observe the Editor
Expect Result: The Editor opens as usual
Actual Result: The Editor shows only white
Reproducible in: 2022.2.0a19, 2022.3.17f1
Not reproducible in: 2021.3.34f1, 2022.2.0a18, 2023.2.6f1, 2023.3.0b3
Fixed in: 2023.1.0a1
Reproduced on: Windows 11 Pro
Not reproduced on: No other environment tested
Notes:
* It takes around 30 minutes to load the project with the created textures
* The reporter notes that “The issue may be related to the hardware, if it doesn't reproduce, change the "num" in CreateFiles.cs to a bigger one”
* To reproduce the issue, the textures do not have to be regenerated each time. It is enough to delete the Library folder before launching the project
* The project loads normally if the Library folder is not deleted
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
- Lens Flare occlusion is slightly delayed when Anti-aliasing is set to TAA
- [Windows] Error ArgumentException: Illegal characters in path logged when creating a VFX Graph
- [VFX Graph] Flipbook Size upgrade issue
- [Windows] Shortcut Command Names are cut off when hovering over Keys in the Keyboard Preview
- Unity.TextMeshPro reference is missing when trying to add it in the Assembly Definition References
Resolution Note:
Thank you for reporting a bug to Unity.
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.