Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
4
Found in
5.0.0f4
Issue ID
681493
Regression
No
[StateMachineBehaviour] Inconsistent Start() usage in StateMachineBehaviour scripts
Steps to reproduce:
1. Create new Unity project
2. Create new C# script
3. Change the inheritance from MonoBehaviour to StateMachineBehaviour
4. Try to use Start() function in it, notice no errors are thrown
5. Try to add parameters in Start function, e.g. Start(int x), notice an error is throw as in MonoBehaviour script, though the Start function is not being called in SMB scirpts
Comments (1)
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
oddurmagg
Sep 04, 2015 18:12
This clashes with the callback names used in the nodecanvas asset