Bug Subscenes + UI entity header failed to load

https://issuetracker.unity3d.com/is...hen-ui-toolkit-package-is-included-in-project

Just a note, this is still occurring with p12 of the ui package and the latest entities package on 2020.2.0b11

"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 F:\Repositories\uitk\Logs. scenePath=Assets/Scenes/SampleScene/New Sub Scene.unity "

Fails in a new empty project with just packages and a subscene consisting of a cube.

 

yes(after a reimport all + restart editor)

 

@antoine-unity Hi, forum notifications didnt actually alert me to this but I appreciate the followup.

I recently got an email regarding from qa
"We successfully reproduced this issue. It seems that the issue was caused by two bugs at once, right now the issue is that the "Build(Latest git)" Script is not working properly with UI Toolkit installed. It will be possible to follow the progress on a chosen resolution in our public Issue Tracker once the report has been processed (this might take up to an hour):
https://issuetracker.unity3d.com/product/unity/issues/guid/1300294"

I'm a bit unclear what the issue with my build script would be but in any case I just tested a new blank project,
using 2020.2.0f1, p13 of uitoolkit & latest hybridrenderer and no other scripts packages added (besides what gets auto added from pacman).
Creating a cube and then converting it to a subscene(and closing the subscene) results in the entity header bug, didn't even have to build the project.

 

@thelebaron when I get the "entity header" issue with sub scenes what works for me is deleting the "SceneDependencyCache" folder.

 

unfortunately that doesnt resolve the reproduction steps I described in my previous post

 

yeah for me neither. Bug still appears

 

Any updates to this?

 

I've had this same issue. I ended up removing Hybrid Renderer entirely and just using Entities since I wasnt actually rendering anything DOTS.

However, that may have lead to another bug in actually building a project with UIToolkit + DOTS, described and a hacky workaround here:

https://forum.unity.com/threads/dot...ets-is-corrupted-in-standalone-build.1031437/

 

Experiencing the same issue using 2020.2.1f1 and UI Toolkit 1.0.0-preview.13.

Here's the import log in case that's of interest https://0bin.net/paste/gpo3wfI4#S6iGOdCz+2jR8P3giubbVIF6yunuF+S9-hcmrdmNQdf

 

same, 2020.2.2, entities 17, toolkit 13

 

Same here with bugreport : 1312659
Could not actually remove the ui package from the project has it's used a lot but did not have the same issue with other project in similar configuration without the UI pacakge.

 

@WAYN_Games did you get an issue tracker for that report? bumping this thread because upon checking the most recent tracker for what I reported, its been reported as a duplicate of an issue that doesnt really appear to have any similarities?

 

No update unfortunately. I sent back more info with some logs through the issue tracker (fogbugz) but did not get any answer yet.

 

utoolkit has been depreciated. UIDocument is a core part of the engine now in the alpha 2021.2, so you don't need the uibuilder + uitoolkit packages anymore to use uielements (and so you can use subscenes now)

 

Subscene does work in lastest alpha. I'll have to finish the upgrade because it broke some stuff but it's promissing.

 

This is happening with 2020.3.0f1 and UI Toolkit 14

 

Seem to be having the same issues with 2020.3.2f1 and UI Toolkit 14

 

Nice, thank you @mcoted3d ! Will give it a shot and let you know if it is gone.

 

I'm still getting this error on 2020.3.3f1

UIToolkit 1.0.0-preview.14
Entities 0.17.0-preview.41

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 /redacted/Logs. scenePath=Assets/Scenes/Test/testIntest.unity guid=4afeb893102c4442a86acc0ce373ab85
UnityEngine.Debug:LogError (object)
Unity.Debug:LogError (object) (at Library/PackageCache/com.unity.entities@0.17.0-preview.41/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.41/Unity.Scenes/ResolveSceneSectionUtility.cs:81)
Unity.Scenes.ResolveSceneReferenceSystem:OnUpdate () (at Library/PackageCache/com.unity.entities@0.17.0-preview.41/Unity.Scenes/ResolveSceneReferenceSystem.cs:174)
Unity.Entities.SystemBase:Update () (at Library/PackageCache/com.unity.entities@0.17.0-preview.41/Unity.Entities/SystemBase.cs:400)
Unity.Entities.ComponentSystemGroup:UpdateAllSystems () (at Library/PackageCache/com.unity.entities@0.17.0-preview.41/Unity.Entities/ComponentSystemGroup.cs:472)
Unity.Entities.ComponentSystemGroup:OnUpdate () (at Library/PackageCache/com.unity.entities@0.17.0-preview.41/Unity.Entities/ComponentSystemGroup.cs:417)
Unity.Entities.ComponentSystem:Update () (at Library/PackageCache/com.unity.entities@0.17.0-preview.41/Unity.Entities/ComponentSystem.cs:114)
Unity.Entities.ComponentSystemGroup:UpdateAllSystems () (at Library/PackageCache/com.unity.entities@0.17.0-preview.41/Unity.Entities/ComponentSystemGroup.cs:472)
Unity.Entities.ComponentSystemGroup:OnUpdate () (at Library/PackageCache/com.unity.entities@0.17.0-preview.41/Unity.Entities/ComponentSystemGroup.cs:417)
Unity.Entities.ComponentSystem:Update () (at Library/PackageCache/com.unity.entities@0.17.0-preview.41/Unity.Entities/ComponentSystem.cs:114)
Unity.Entities.ScriptBehaviourUpdateOrder/DummyDelegateWrapper:TriggerUpdate () (at Library/PackageCache/com.unity.entities@0.17.0-preview.41/Unity.Entities/ScriptBehaviourUpdateOrder.cs:333)

 

Ah shoot @mcoted3d that is the exact issue, how do we get this resolved?

(this seems to be a show stopper to use UI toolkit with LTS)

 

@mcoted3d great news! I'll try it out when it goes live

 

Nice, thank you @mcoted3d ! Will check it out when 2020.3.4f1 is live

 

@mcoted3d Unfortunately, it still occurs with a new sub scene in an existing project in 2020.3.4f1.

Error also occurs in this project using a brand new scene, adding a new sub scene and unloading.

Entities 0.17.0-preview.41
toolkit 1.0.0-preview.14

But....
When I create an empty project add those two packages it works though. I can unload a new sub scene with no errors.

I tried deleting the library/logs/org folders, didn't help. Not sure what else to try.

Update: I tried installing the same packages to the empty project one by one, and it was when I installed com.unity.rendering.hybrid that the error came back! it installed 0.11.0-preview.42. Interestingly, after removing the package, the error persists! Even after deleting library/logs/obj of this empty project too.

Perhaps this package is causing the issue?

 

@mcoted3d currently this bug makes it so you cannot use DOTS + 2020 LTS + UI Toolkit

This is a critical bug, Unity LTS is unusable trying to combine DOTS and UI Toolkit

 

Will do.

I will make a more clear "repro" but it is:

- Download 2020.3 LTS
- Manually add the UI Builder/Toolkit to the package manifest
- Create a SubScene
- Watch the entity header issue appear

 

I posted a bug report from an “empty” project.
Case 133163

thanks for continuing to look into this.

 

@mcoted3d are we set with the bug report to look into this issue? Would really like to be able to continue using DOTS + UI Toolkit

 

Yes, it happens in the editor, reproducibly, every time.

 

Yes

1 New 2020 LTS Project + DOTS + UI Toolkit (add to manifest manually)
2 Create SubScene
3 Get EntityHeader file issue

 

@mcoted3d here is a 5 minute video showing the bug

It really is just:
1. opening 2020 LTS
2. adding:
"com.unity.rendering.hybrid": "0.11.0-preview.42",
"com.unity.ui": "1.0.0-preview.14",
"com.unity.ui.builder": "1.0.0-preview.13",
3. Creating SubScene
4. Entity Issue

https://share.getcloudapp.com/nOuob5Ak
(cc @AdamBebko )

 

Yes, mine looks exactly the same, except on Mac, and installing via package manager.

 

Any luck on this? Been blocked on moving forward and am wondering whether I should move off of 2020 LTS

 

I don't know what the Dots Build system is, but I just wanted to confirm that this happens in the editor, without building anything at all. It's just in an empty project, no playmode, no nothing, just a sub scene that you unload.

 

@mcoted3d Are you still looking for more bug reports? Though I'm fairly certain my original report was basically along the lines of what adammpolak said, I'd be happy to make another if it has the chance of expediting narrowing down the cause, as it's has been like 8 months since I originally reported this
Though its not an issue in 2021.2, unfortunately I am(and obviously others) required now to revisit this with the recent announcement of needing to downgrade to 2020 for DOTS

 

Sorry don't mean to derail this thread, but what annoucement means that you need to downgrade to 2020 for DOTS?

 

This one :

https://forum.unity.com/threads/notice-on-dots-compatibility-with-unity-2021-1.1091800/

I am in the same situation, I still have my open bug report 1312659. I've been contacted on htat subject and I'll try to provide the necessary info but since the reproduction steps are fairly easy as we can see in the above posts and the issue is no longer present in the 2021 version. I assume a backport would not be too complicated to do.

This IMO is critical to do especcially since we'll have to stick with 2020 for a while...

 

Just submitted a new one, case 1335154

 

They closed my bug report immediately saying they already knew about it. Just FYI

Case 133163

 

I just updated my ticket with 2 identical project following the same steps described by @adammpolak.
One was made using latest 2020 version and one with the latest 2021.1 version.
The first one has the error, the second one does not.

@mcoted3d given the number of users having the issue and the number of ticket probably created by said users. Maybe someone should link those ticket together somehow to avoid multiple unity ressource working on the subject.

 

Just marked here in case is solved

------------------------------Edit--------------------------------

Well, I've got a good news and a bad news

Bad news is, subscene + UIToolKit is still bumping and renders nothing with 2020.3.9f.

Good news is, I figured out a way to keep both Subscene & UIToolKit working simultaneously at runtime. The trick is, modify your subscene with UIToolKit package removed, save your subscene, reinstall UIToolKit package, done.(strange as it sounds but works for me)

Tips:
1. Subscene stays integrated as long as you do not change subscene with UIToolKit package installed.
2. You need to use Scripting Define Symbols to avoid error logs and error codes while UIToolKit is missing(If is necessary).