Search Issue Tracker
Active
Under Consideration for 1.3.X
Votes
27
Found in [Package]
1.3.0-pre.4 - Entities
Issue ID
ECSB-1283
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
- Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
iamarugin
Sep 04, 2024 15:51
I am pretty sure that another related issue was introduced in 2022.3.40: https://issuetracker.unity3d.com/issues/materialmeshinfo-does-not-point-to-a-valid-mesh-error-for-runtime-created-entity-when-using-mesh-slash-material-indices-for-multiple-meshes-slash-materials
And they all are realted to this fix: https://issuetracker.unity3d.com/issues/job-allocator-contention-causes-slow-job-execution
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.