Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.0.3
Issue ID
ADDR-3179
Regression
No
AssetRefererenceSprite does not track subobjects properly - the new name is not updated on the m_SubObjectName
Steps to reproduce:
1. Open the attached user's project "1421933-Customer.zip"
2. Select "MyScriptable.asset" within the Editor in the Project Window
3. Under the "Test Data field" set the "New Sprite Atlas" to the "My Test Sprite" field
4. Then, on the second asset slot set the "test Sprite test"
5. Save the project
6. Open the "MyScriptable.asset" using a text editor
7. Check the m_SubObjectName field, it should be "test Sprite test"
8. Move back to the editor and rename the "test Sprite test" asset to test "Sprite_01".
9. Repeat step 6 and 7
Expected results: the new name should be stored on the m_SubObjectName, but it is still the old one (test Sprite test).
Actual results: the old name is still stored in the m_SubObjectName and it's not updated
Reproducible in: 2020.3.44f1, 2021.3.17f1, 2022.2.3f1, 2023.1.0a25
Notes:
-AssetRefererenceSprite tracks subobjects by name. But if those subobjects are renamed, the system does not update the AssetRef. Thus, the AssetReferenceSprite points to non-existing subassets
-Issue resolves if replacing the renamed asset in "MyScriptable.asset" second asset slot
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.