Search Issue Tracker
Won't Fix
Votes
1
Found in
2023.2.16f1
6000.0.0b13
Issue ID
UUM-68099
Regression
Yes
GUIDPresistentManager reports Loads of Object Missing Errors when specific diagnostics settings enabled
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the Preferences window (macOS: Unity > Settings; Windows: Edit > Preferences)
3. Enable the "AssetLoadStateValidation" option inside Diagnostics > AssetDatabase
4. Restart the Editor
5. Observe the Console
Expected result: No errors are present
Actual result: Hundreds of “Loaded object missing in GUIDPersistentManagerV2: …“ errors are present
Reproducible with: 2023.2.0a17, 2023.2.16f1, 6000.0.0b13
Not reproducible with: 2021.3.36f1, 2022.3.22f1, 2023.2.0a16
Reproducible on: M1 MacOS 14.3.1
Not reproducible on: No other environment tested
Comments (1)
-
AetherCLion
Apr 15, 2024 17:30
This is reproducible on Windows
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
- Inconsistent "Mock HMD Loader" naming in the "Project Settings"
- Search Field breaks when deleting a Search Expression that has been converted to a Visual Query Block
- Outdated documentation page is linked when clicking on the Help icon for "Virtual Texturing" Module in Profiler Window
- [Linux] No “File already exists” pop-up thrown when saving Shader Variants with an already existing name from Build Profiles or Project Settings window
- Bounding Box Size of Light Probe Proxy Volume and Settings.Max Interaction Distance of Panel Input Configuration Components cannot be added as Properties in Animation window
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.