Search Issue Tracker
Fixed
Votes
1
Found in [Package]
7.3.1
Issue ID
1236166
Regression
Yes
Two errors are thrown in the Console window when creating a new HDRP template project
How to reproduce:
1. Create and open a new HDRP template project
2. Observe the Console window
Expected result: no errors are thrown
Actual result: two errors are thrown
Reproducible with: 2019.3.8f1, 2019.3.9f1 (7.3.1), 2020.1.0b2, 2020.1.0b5, 2020.2.0a7 (8.0.1)
Not reproducible with: 2018.4.21f1 (4.1.0 - preview), 2019.3.7f1 (7.3.1), 2020.1.0b1 (8.0.1)
Could not test with: 2017.4.39f1, 2020.2.0a1 (HDRP template not available)
Thrown errors:
1) GetLoadedImportedAssetsAndArtifactIDs called with invalid artifactID
2) Assertion failed on expression: 'it->second.IsValid()'
-
xT1TANx
Nov 16, 2022 00:02
GetLoadedImportedAssetsAndArtifactIDs called with invalid artifactID for guid {} for asset {}
2022.1.22F1 MAC
-
Vaupell
Oct 12, 2022 20:59
found in 2022.1.20f1
-
huulong
Jul 26, 2022 14:55
Still present on 2022.1.10f1, Core RP Library / High Definition RP and Universal RP v13.1.8 on Linux, at least during build.
-
uholst
Apr 13, 2022 13:33
I also have the version 2020.3.32f1 and have this problem. And cannot open any already existing project.
-
Faris_RA
Apr 05, 2022 03:28
still experiencing this in 2020.3.32f1.
also cannot open any project at all.
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
- [Android][Vulcan] "UNITY_DISPLAY_ORIENTATION_PRETRANSFORM" is always 0 when the render pipeline is URP
- Editor loads for a long time when doing an Undo action in a large Shader Graph
- Memory leak when building AssetBundles
- [Asset Bundle] AudioSource output field not staying connected correctly when loaded from Asset Bundle
- [Android] Duolashock4 controller is not detected after disconnecting and reconnecting controller while the Player is running in the background
Resolution Note:
Fixed in 2020.2.0a8
Resolution Note:
Fixed in 2020.1.0b10
Resolution Note:
Fixed in 2019.3.14f1