I still hit this bug, now I will need to understand why, which is frankly an issue for me. The bug doesn’t reproduce immediately, but once I hit it, it’s for ever. I need to figure out how to solve this, probably I will revert to the asset database v1 (which is a shame)
Sucking it up, I can tell you that this is where it gets stuck:
this where it gets stuck (apparently the file can change)
The parallel stacks are not telling me much honestly:
BTW I can create a dump if it helps
created: Unity.zip - Google Drive
Edit: I started from scratch and I asked to not update the assets to V2, I will see how it goes like this.
Unity ECS seems to need V2. Now we can downgrade to the 2019.2 ECS version honestly, so it’s not a big issue. However I am not sure if the crash is a blocking one (the game works anyway):
[Error] [0.120] [3] System.InvalidOperationException: com.unity.entities requires Asset Pipeline Version 2. Please enable Version 2 in Project Settings / Editor / Asset Pipeline / Mode
at Unity.Scenes.Editor.TypeDependencyCache…cctor () [0x0004a] in E:\Robocraft_2019.3\Library\PackageCache\com.unity.entities@0.5.0-preview.17\Unity.Scenes.Editor\TypeDependencyCache.cs:48
UnityEditor.EditorAssemblies:processInitializeOnLoadAttributes(Type[ ])
I’m sorry to hear that you’re still seeing this error. I’d suggest getting an up to date bug report sent in. You can find the process on how to do this here: Unity QA: Building quality with passion
ok I will try with the email thanks
Deleting the projectsettings.asset file fixed the issue. I uploaded the project for you to repro so that you can fix it for other people. So something went wrong with the back compatibility of the projectsettings.asset file. NO clue why the problem presents only when switching to AssetDatabase V2
@UnityMaru can I talk to someone who know more about this?
The bug is here: https://fogbugz.unity3d.com/default.asp?1215703_nmd4h7sqc90dc7mp
as I wrote I fixed it deleting the projectsettings.asset the first time.
however lately the bug is resurfacing again and deleting the projectsettings is not helping, although in this specific case, deleting the library folder fixed it. I can’t really imagine how this is happening only to me, someone else must be able to experience it.
The good news is that there is always a work around, but deleting the Library folder and reimporting everything takes time.
@sebas I am getting it on 2019.3.8f1
I already tried deleting the library and .meta files and it didn’t work. Just tried deleting projectsettings.asset and re-imported again and still not fixed.
I stopped experiencing the problem for a while now. Still getting for you must be frustrating, however in my case reverting to asset database v1 used to fix it (now it works with v2 too for me)
@sebas771 I fixed it by deleting assets until it was gone to narrow it down. Turns out it was a tool I had called Height Mapper that I had used to import real world heightmap data.
