Search Issue Tracker
Fixed in 1.12.0
Votes
1
Found in [Package]
1.2.2
Issue ID
1211792
Regression
Yes
In ScriptableObjects AssetReferenceGameObject reverts to previous value after quitting Unity when the value is set to "None"
How to reproduce:
1. Open attached project "Case_1211792"
2. Select AddressableTest ScriptableObject in the Assets folder in Project window
3. change the Reference variable in the inspector to "None"
4. Exit Unity and open the project again
5. Check AddressableTest asset again
Expected result: "None" value is saved to the Reference variable
Actual result: Reference value changes back to the one before setting it to "None"
Reproducible in: 1.2.2 (2018.4.15f1, 2019.2.19f1, 2019.3.0f5, 2020.1.0a19), 1.5.1 (2018.4.15f1, 2019.2.19f1, 2019.3.0f5, 2020.1.0a19)
Not reproducible in: 1.1.10 (2018.4.15f1, 2019.2.19f1, 2019.3.0f5, 2020.1.0a19)
Could not test with: 2017.4.36f1 (no Package Manager)
Notes: Changing to other values other than "None" saves them properly. The issue is not just visual, the value is actually provided to the script, which can be checked with the "test.cs" script (attached to Main Camera) which outputs the Reference's value to the Console. Does not reproduce with AssetReference. MonoBehavior scripts save the value correctly.
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
- "Rendering Debugger" displays incorrect overdraw count when using "Unlit/Texture" shader
- Scene and Game views break when the Editor window is snapped with the Microsoft PowerToys
- Materials do not transfer texture when the "Shader" parameter is changed from "Unlit/Texture" to "Universal Render Pipeline/Unlit"
- [Linux][Vulkan] Crash when opening searchable dialog
- The "Shader error in 'AE/Leaves': "Undefined punctual shadow filter algorithm"" error appears when build completes on a specific project
Resolution Note (fix version 1.12.0):
Fixed in Addressables 1.12.0