Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Votes
0
Found in
2021.3.39f1
2022.3.32f1
6000.0.6f1
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PropertyField with range attribute triggers change event when the value didn't change
- [Android] Soft keyboard is missing the "OK" button on Android
- The Profiler ignores a modified targetFrameRate when profiling Edit mode
- [General] Package manager takes 15 minutes to load
- Asset's Inspector information is no longer displayed when docking the Search Window
Add comment