Search Issue Tracker
In Progress
Fix In Review for 2022.3.X
Votes
42
Found in
2022.3.40f1
Issue ID
UUM-82547
Regression
Yes
"Missing Prefab Asset" error in a SubScene after Domain Reload
How to reproduce:
1. Open the attached “IN-81743“ project
2. Enter Play Mode
3. Exit Play Mode
4. Change 'MyScript.cs' to trigger a Domain Reload
5. Observe the Unity Console Window
Expected result: No errors are thrown
Actual result: A "Missing Prefab Asset" error is thrown
Reproducible with: 1.1.0-exp.1 (2022.3.40f1, 2022.3.42f1), 1.3.0-pre.4 (2022.3.40f1, 2022.3.42f1)
Not reproducible with: 1.3.0-pre.4 (2022.3.39f1, 6000.0.14f1)
Unable to test: 0.51.1-preview.21 (2021.3.42f1) (Unresolvable package problems due to downgrading)
Reproducible on: Windows 10 (user), Windows 11 pro
Not reproducible on: No other environment tested
Notes:
* Bug regression dependent on the Engine version. Regressed version: 2022.3.40f1
* Once the error occurs, it persists until Unity is restarted
* The Background task “Import EntityScene” remains in a “Not Responding” state
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
- The Editor freezes on RenderGraphViewer.Repaint when entering too many characters in search fields without character limits
- Adding a new SubLayer in Graphics Compositor renders BaseLayer darker and makes it flicker
- DOTS Materials Not Rendering in Player When Using Entity Graphics with Custom SRP
- Sprite Pivot position in Sprite Editor and Scene View do not match when the position is custom
- [HDRP] Unchecking the "Base layer" in Graphics Compositor results in Camera view rendering over the window
Lex
Sep 02, 2024 21:40
This issue is blocking our development as well. Could this be prioritized for a fix? Thank you.
Zardify
Sep 01, 2024 11:08
This makes all editor versions >= 2022.3.40f1 completely unusable for entities development. Fix needed ASAP. Should never have been released...
KhanStone
Aug 30, 2024 04:08
Also having this issue, please fix!
kriegen
Aug 30, 2024 02:28
This issue is also entirely stopping our current development.
This occurs when a prefab either in the subscene's hierarchy or a prefab referenced in a baker in a subscene has any kind of MonoBehevior component (URPMaterialPropertyBaseColor or any other Authoring for example).
iamarugin
Aug 28, 2024 07:59
Why this is not instantly fixed? UNITY IS NOT USABLE BECAUSE OF THIS.
wgbg
Aug 26, 2024 09:50
The same here.. After more debugging, it turned out that this issue occurs when you have Baker script on your prefab object. Without baker script it's working properly.
deshalb
Aug 22, 2024 16:24
got the same issue here with unity 2022.3.42f1 and entities 1.2.4
DGX-Dino
Aug 22, 2024 12:45
also happens in my project, Entities 1.2.3, Unity 2022.3.40+. Works fine in 2022.3.39
gencontain
Aug 21, 2024 05:25
We're seeing this same issue as well, it's preventing us from upgrading to 2022.3.401f1 and up.
danielkanda
Aug 20, 2024 10:14
I can confirm this issue happens on MacOS as well using 2022.3.41f1 with N4E 1.2.4. Reverting to 2022.3.29 fixed the issue, although I did not test more recent versions.
Hoping this will get resolved quickly as it renders Entities / N4E pretty much unusable.