Search Issue Tracker
Fixed
Fixed in 6000.0.50f1, 6000.1.4f1, 6000.2.0a11
Votes
1
Found in
6000.0.44f1
6000.1.0b12
6000.2.0a8
Issue ID
UUM-101710
Regression
No
UnityEvents break when a different object is assigned
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/BugReport/TestEvent.unity“ Scene
3. Enter the Play Mode
4. Observe the Console window and see the “Receiver1.Test() “ message is displayed
5. Exit the Play Mode
6. Select the “EventSender” GameObject in the Hierarchy window
7. Drag and drop the “Receiver2” GameObject to replace “Receiver1” in the UnityEvent field in the Inspector window
8. Enter the Play Mode
9. Observe the Console and Inspector windows
Expected result: The “Receiver2.Test()” message is displayed, and the event target shows as <TestEventReceiver.Test>
Actual result: No message is displayed, and the event target shows as <Missing GameObject.Test>
Reproducible with: 2022.3.60f1, 6000.0.44f1, 6000.1.0b12, 6000.2.0a8
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Workaround: Select the “No Function” first before reassigning an object, then select the target method again
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Global Volume visual details are blurred when Tonemapping mode is set to any other than 'ACES'
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
Add comment