Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0b9
Issue ID
970029
Regression
No
"UnityEvent" doesn't work with multiple instances of the same "Monobehaviour" at the same time
Reproduction steps:
1. Open "UnityEventMultipleComponent.zip" project
2. In the Hierarchy window click on "Fixed"
3. In the Inspector window click on "Invoker (Script)" cog image in the right -> "Execute"
4. See the output in the Console window:
"First - 1
Second - 2"
5. In the Hierarchy window click on "Broken" **Fix this first
6. In the Inspector window click on "Invoker (Script)" cog image in the right -> "Execute"
7. See the output in the Console window:
"First - 1
First - 2"
Expected Result: The "Broken" prefab should output like the "Fixed" prefab
Actual Result: The "Broken" prefab outputs the same prefix both times
Reproduced with: 2018.1.0a7, 2017.3.0f2, 2017.2.1f1, 2017.1.2p4, 5.6.4p4
Note:
** To fix the "Broken" prefab for the repro steps to work, you have to drag "Debug Action String Component" in the second slot of the "Invoker" script -> "No Function" -> "Debug Action String Component -> Execute". (Shown in video)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.