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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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