Search Issue Tracker
Fixed
Fixed in 6000.0.51f1, 6000.1.5f1, 6000.2.0b4, 6000.3.0a1
Votes
0
Found in
2022.3.62f1
6000.0.48f1
6000.1.3f1
6000.2.0a10
Issue ID
UUM-104854
Regression
Yes
References placed in a UnityEvent change to the same reference when multi-selecting their GameObjects
How to reproduce:
1. Open the “AudioClipReplaceBug.zip“ project
2. Open the “SampleScene“
3. In the Hierarchy, select the “Audio1“ GameObject, and then in the Inspector, observe the Audio Clip in the Test Script Component
4. In the Hierarchy, select the “Audio2“ GameObject, and then in the Inspector, observe the Audio Clip in the Test Script Component (it is different from the “Audio1” GameObject)
5. Select both GameObjects in the Hierarchy
6. Repeat steps 3-4
Expected result: Both Audio Clip references are different
Actual result: Both Audio Clip references are the same
Reproducible in: 2022.3.62f1, 6000.0.0b16, 6000.0.48f1, 6000.1.3f1, 6000.2.0a10
Not reproducible in: 2021.3.51f1, 6000.0.0b15
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Not reproducible with the default Button’s OnClick events (or likely any other default events)
- Reproducible with other types of objects as well, but not the default types (int, float, bool, string, etc.)
- Usually the references change to the first selected GameObject’s reference
- Afterward the scene becomes dirty and the change can be undone
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment