Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.2.17f1
2018.3.0a1
Issue ID
1104874
Regression
Yes
AssetDatabase.LoadAllAssetsAtPath fails to load built in assets
In Unity 2018.2, when attempting to use the "AssetDatabase.LoadAllAssetsAtPath" to load the assets from either "Library/unity default resources" or "Resources/unity_builtin_extra", a Object[] is returned populated with the corresponding assets stored within. However, if you attempt to do this in Unity 2018.3, the returned Object[] is empty.
To reproduce:
1. Download attached project "2018.2 - LoadDefaultandBuiltinResources.zip and open in Unity
2. Press the Menu item labelled "Tests" and execute both functions "Library > unity default resources" and "Resources > unity_builtin_extra"
3. Observe that the text printed to the Console states that no objects were loaded
Expected behavior: Using LoadAllAssetsAtPath to load the paths would load the objects stored at the path
Actual behavior: Using LoadAllAssetsAtPath to load the paths does not load objects stored at paths, and leaves the expecting Object[] empty
Notes:
- This issue appears on both Windows and macOS
Reproduced on Unity 2018.3.0a1, 2018.3.0f1 and 2019.1.0a11
Not reproduced on Unity 2018.2.19f1
Regression on Unity 2018.3.0a1
Comments (2)
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
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
TiagoTFG
Feb 28, 2019 01:39
Is this coming for 2018.3.x anyhow?