Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.18.4
Issue ID
ADDR-2022
Regression
No
[Addressables] LoadAssetAsync fails when FBX AnimationClip has the same name as the FBX file
Reproduction steps:
1. Open attached project "AddressableAnimClipBug" and scene "SampleScene"
2. In Addressables Groups window, Build -> New Build -> Default Build Script
3. Enter Play Mode
4. Observe Console window
Expected result: All three AnimationClips are loaded without issue
Actual result: The AnimationClip that has the same name as its FBX file fails to load (loads as GameObject)
Reproducible with: 1.18.4 (2018.4.35f1, 2019.4.29f1, 2020.3.12f1, 2021.1.12f1, 2021.2.0a20)
Workaround:
Changing the AnimationClip name to anything different from the FBX file name, then rebuilding Addressables fixes the issue
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
- Can’t delete gradient keys with Mac keyboard or context menu options
- Editor freezes for a few minutes when closing or switching a VFX window that was opened in a previous project
- UI Overlaps when switching Render Pipeline Asset for different Quality Levels in Quality Project Settings
- Ray Tracing Shader link to the documentation isn’t working
- Warning "BatchRendererGroups currently don't support override shaders" is spammed in Play mode when using H-Trace WSGI with BatchRenderGroups
Resolution Note:
Loading assets from AssetBundles is dependent on the name of the assets themselves. Having two assets named the same in an AssetBundle will always cause this to break.