Search Issue Tracker
Fixed in 2022.2.12f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a6
Votes
0
Found in
2022.2.7f1
2023.1.0b5
2023.2.0a3
Issue ID
UUM-27561
Regression
Yes
UnityEvent listener execution state is Off by default
Reproduction steps:
1. Open the “OffByDefault” project
2. Open the “SampleScene“ scene
3. Select the “Test” GameObject
4. In Inspector click the “+” button to add a listener the “TestEvent” UnityEvent
5. Observe the execution state (top left) of the added listener
Expected result: the state is “RuntimeOnly“
Actual result: the state is “Off“
Reproduced in: 2022.2.0a9, 2022.2.7f1, 2023.1.0b5, 2023.2.0a3
Not reproduced in: 2020.3.45f1, 2021.3.19f1, 2022.2.0a8
Reproduced using: macOS 13.0.1 (Intel), Windows 10 (by the reporter)
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note (fix version 2023.2):
Adding a new PersistentCall to a UnityEvent is added with the default value UnityEventCallState.RuntimeOnly instead of UnityEventCallState.Off