Topic automatically created to discuss “Missing Prefab Asset” error in a SubScene after Domain Reload
We experience the same problem and can say that this is not a preview nor experimental bug. We use Entity Component System 1.2.3 and behaviour is the same. Problem exists in editor version 2022.3.40f1, 2022.3.41f1, and 2022.3.42f1 but not in 2022.3.39f1 (and below).
Pinging this again to make sure it is noticed that this is a production bug in 1.2.3 and not just experimental or pre related.
Also it is our impression that this is not necessarily only related to Entities but could be related to Editor version or even a combination of the two. (seeing that it only happens from 2022.3.40f1 and on.)
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.
We’re seeing this same issue as well, it’s preventing us from upgrading to 2022.3.401f1 and up.
also happens in my project, Entities 1.2.3, Unity 2022.3.40+. Works fine in 2022.3.39
got the same issue here with unity 2022.3.42f1 and entities 1.2.4
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.
Why this is not instantly fixed? UNITY IS NOT USABLE BECAUSE OF THIS.
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).
Also having this issue, please fix!
This makes all editor versions >= 2022.3.40f1 completely unusable for entities development. Fix needed ASAP. Should never have been released…
This issue is blocking our development as well. Could this be prioritized for a fix? Thank you.
I am pretty sure that another related issue was introduced in 2022.3.40: Unity Issue Tracker - "MaterialMeshInfo does not point to a valid mesh" error for runtime-created entity when using mesh/material indices for multiple meshes/materials
And they all are realted to this fix: Unity Issue Tracker - Job allocator contention causes slow job execution
Still occuring on 2022.3.46.
Still occurring on 2022.3.47
this bug is crippling the progress of my project, still occurs on 2022.3.47
Unacceptable that this was released and is still an issue. Lost a whole day trying to debug this nonsense. WTF
We are also having the issue on 2022.3.48 LTS.
Excited this has a fix in review!