Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2023.3.0a9
Issue ID
UUM-52188
Regression
Yes
Scripts derive from StateMachineBehaviour instead of MonoBehaviour when creating new C# Scripts
How to reproduce:
1. Create a new project
2. Create a new C# Script
3. Open the C# Script
Expected result: The newly created C# script derives from MonoBehaviour
Actual result: The newly created C# script derives from StateMachineBehaviour
Reproducible with: 2023.3.0a9
Not reproducible with: 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Reproduced on: macOS Ventura 13.5 (Intel), Windows 11 (User reported)
Not reproduced on: No other environment tested
Notes:
- The reporter has noted that - “Likely cause: Scripting submenu has Playables submenu under it with two items, likely there should be three there (another for mentioned state machine).”
- The same happens if using C# Script from the Scripting submenu.
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:
There are no fixes planned for this Bug
Resolution Note (2023.3.X):
There are no fixes planned for this Bug