Search Issue Tracker

Not Reproducible

Votes

5

Found in [Package]

2020.2.0b12

Issue ID

1298111

Regression

Yes

Entity subscene loading fails with "Loading Entity Scene failed because the entity header file couldn't be resolved" error

Package: Entity Component System (ECS)

-

How to reproduce:
1. Open the user's attached project ("sampleproject.zip")

Expected result: Entity subscene is loaded
Actual result: "Loading Entity Scene failed because the entity header file couldn't be resolved." error is thrown

Reproducible with: ECS 0.17.0-preview.37 (2020.2.0b12, 2020.2.0b14)
Does no longer reproduce with: ECS 0.17.0-preview.37 (2020.2.0b15, 2020.2.3f1, 2021.1.0b5, 2021.2.0a3)
Not reproducible with: ECS 0.17.0-preview.37 (2018.4.31f1, 2019.4.20f1, 2020.2.0b11)

Error thrown:

Loading Entity Scene failed because the entity header file couldn't be resolved. This might be caused by a failed import of the entity scene. Please take a look at the SubScene MonoBehaviour that references this scene or at the asset import worker log in C:\Users\asmi\Experimental.Multiplayer\sampleproject\Logs. scenePath=Assets/Scenes/Asteroids/GhostCollection.unity guid=786e57b5191e248069790dde644d7e1a
UnityEngine.Debug:LogError (object)
Unity.Debug:LogError (object) (at Library/PackageCache/com.unity.entities@0.17.0-preview.37/Unity.Entities/Stubs/Unity/Debug.cs:13)
Unity.Scenes.ResolveSceneSectionUtility:ResolveSceneSections (Unity.Entities.EntityManager,Unity.Entities.Entity,Unity.Entities.Hash128,Unity.Entities.RequestSceneLoaded,Unity.Entities.Hash128) (at Library/PackageCache/com.unity.entities@0.17.0-preview.37/Unity.Scenes/ResolveSceneSectionUtility.cs:81)
Unity.Scenes.ResolveSceneReferenceSystem:OnUpdate () (at Library/PackageCache/com.unity.entities@0.17.0-preview.37/Unity.Scenes/ResolveSceneReferenceSystem.cs:174)
Unity.Entities.SystemBase:Update () (at Library/PackageCache/com.unity.entities@0.17.0-preview.37/Unity.Entities/SystemBase.cs:400)
Unity.Entities.ComponentSystemGroup:UpdateAllSystems () (at Library/PackageCache/com.unity.entities@0.17.0-preview.37/Unity.Entities/ComponentSystemGroup.cs:472)
Unity.Entities.ComponentSystemGroup:OnUpdate () (at Library/PackageCache/com.unity.entities@0.17.0-preview.37/Unity.Entities/ComponentSystemGroup.cs:417)
Unity.Entities.ComponentSystem:Update () (at Library/PackageCache/com.unity.entities@0.17.0-preview.37/Unity.Entities/ComponentSystem.cs:114)
Unity.Entities.ComponentSystemGroup:UpdateAllSystems () (at Library/PackageCache/com.unity.entities@0.17.0-preview.37/Unity.Entities/ComponentSystemGroup.cs:472)
Unity.Entities.ComponentSystemGroup:OnUpdate () (at Library/PackageCache/com.unity.entities@0.17.0-preview.37/Unity.Entities/ComponentSystemGroup.cs:417)
Unity.Entities.ComponentSystem:Update () (at Library/PackageCache/com.unity.entities@0.17.0-preview.37/Unity.Entities/ComponentSystem.cs:114)
Unity.Entities.ScriptBehaviourUpdateOrder/DummyDelegateWrapper:TriggerUpdate () (at Library/PackageCache/com.unity.entities@0.17.0-preview.37/Unity.Entities/ScriptBehaviourUpdateOrder.cs:333)

  1. Resolution Note:

    Does no longer reproduce with Unity 2020.2.0b15 and up
    SubScenes created in 2020.2.0b12 - 2020.2.0b14 will still throw the same error, but new SubScenes will work fine.

Comments (6)

  1. Thygrrr

    Jul 29, 2023 21:09

    Error still frequently occurs in 2022.3.5f1 - at least 3 or 4 times a day.
    Seems to be loosely related to unrelated errors stopping the build process.

    e.g. stopping play mode while a Subscene is being streamed in may cause an error message that interferes with the subsequent error import.

  2. unity_8C87D0CEAC1B4AD56CC5

    Nov 21, 2022 08:06

    using unity 2022.0b16 and this issue still persist.

  3. Cachete

    Nov 21, 2022 01:13

    happens to me ALL THE TIME in 2022.2.0b16 and is VERY annoying - to fix it, you have to restart Unity, clear entity cache and reload the subscene

  4. jennal

    Nov 07, 2022 11:40

    still exists in 2022.2.0b13

  5. lclemens

    Jul 20, 2022 20:14

    I fixed it by closing unity and deleting the Library folder and re-opening it.

  6. Harry-Wells

    Dec 15, 2020 13:24

    I got the same error and I have logs for it.
    https://gist.github.com/24c83c7f7f9e125072ce4181fc061d56

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.