Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
0
Found in
2020.1.a15
Issue ID
1318602
Regression
No
Artifact Dependency not setup when used with LazyLoadReference<>
Artifact Dependency is not registered, when setup when using LazyLoadReference. In the attached project, a ScriptedImporter (for ".test" assets) is setting up an artifact dependency to asset reference that is to Hello.txt. The ScriptedImporter is configured to import before .txt assets and therefore the reference to Hello.txt isn't available during first import. In order to still be able to setup the artifact dependency, a LazyLoadReference to Hello.txt is used.
Repro steps:
1) Open project in attached project 'ArtifactDependencyAndLazyLoadRef.zip'
2) Notice unexpected warning in console "Import of asset 'Assets/World.test' setup artifact dependency to 'Assets/Hello.txt' but dependency isn't used and therefore not registered in the asset database."
3) Change Hello.txt outside unity and give back unity focus.
4) Notice the World asset doesn't get reimported - dependency hasn't be setup.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
Add comment