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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1140186