Search Issue Tracker
Fixed
Fixed in 6000.3.0a2
Votes
0
Found in
2021.3.39f1
2022.3.32f1
6000.0.6f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
7000.0.0a1
Issue ID
UUM-73759
Regression
No
Unity Events added to a ScriptableObject are not invoked if they are added in Edit mode and their Call State is set to "Runtime Only"
Reproduction steps:
1. Open the attached “BugRepro.zip” project
2. Open the “EventTestScene”
3. Make sure that in the “EventTest1” ScriptableObject, the OnTrigger() event calls an “EventTest.DoSomething” function on the “EventTest2” ScriptableObject
4. Make sure the Inspector window is showing anything other than the “EventTest1” ScriptableObject
5. Enter Play Mode
6. Observe the Console Window
Expected results: “EventTest2.DoSomething” is called
Actual results: “EventTest2.DoSomething” is never called
Reproducible with: 2021.3.39f1, 2022.3.32f1, 6000.0.6f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- If the Inspector is showing the “EventTest1” ScriptableObject, the “EventTest2.DoSomething” is called after the “EventTestBehavior.Start” calls the “Trigger” function
- If the Event’s Call State is set to “Editor And Runtime”, this behavior does not reproduce
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note:
Events execute as per user's expectations.