Search Issue Tracker
Duplicate
Votes
0
Found in
2017.4.23f1
Issue ID
1151866
Regression
Yes
Multiple Assets with the same Name but different Types cannot be individually loaded from an Asset Bundle
The first Asset of that name in the Manifest can be loaded, but any additional Assets sharing the name (but not type) are not returned by either Synchronous or Asynchronous Load methods. All Assets are still returned by LoadAllAssets.
To reproduce:
1. Download attached “New Unity Project.zip" project and open in Unity
2. Open "BugExample" scene
3. Enter to Play mode
4. In Console, You will see a Warning that the Texture, which shares a name with a Scriptable Object, fails to load
Notes:
- This issue appears both on Windows Standalone, macOS Standalone, iOS, and Android
Reproduced on Unity 2017.4.23f1, 2017.4.26f1, 2018.3.14f1, 2018.4.0f1, 2019.1.2f1, 2019.2.0a14 and 2019.3.0a2
Not reproduce on Unity 2017.4.22f1
Regression on Unity 2017.4.23f1
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
This is a duplicate of issue #1140186