Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2023.2.0b3
2023.3.0a1
Issue ID
UUM-44310
Regression
Yes
”Button.clicked” has no effect when being used in the Editor's Play Mode
How to reproduce:
1. Open the user’s attached “button-click-bug.zip” project
2. Enter the "menu" Scene (Assets > Scenes)
3. Enter Play Mode
4. Press the “Play” button and observe the result
Expected result: A new Scene is loaded
Actual result: New Scene is not loaded
Reproducible with: 2023.2.0a19, 2023.2.0b3
Not reproducible with: 2021.3.29f1, 2022.3.6f1, 2023.1.7f1, 2023.2.0a18
Reproduced on: macOS 13.4.1 (Intel)
Note: not reproducible in the Standalone Player (macOS)
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:
This is by design. You need to register all events in the OnEnable(), not Awake(). The UI is instantiated in OnEnable(). See the docs below:
https://docs.unity3d.com/Manual/UIE-get-started-with-runtime-ui.html#define-behavior
Resolution Note (2023.3.X):
This is by design. You need to register all events in the OnEnable(), not Awake(). The UI is instantiated in OnEnable(). See the docs below:
https://docs.unity3d.com/Manual/UIE-get-started-with-runtime-ui.html#define-behavior