Search Issue Tracker
Fixed in 4.5.X
Votes
0
Found in
4.6.0b1
Issue ID
589281
Regression
Yes
Non-monobehavior classes break the script execution order window
To reproduce:
1. Open attached project, it contains a hefty amount of scripts
2. Open the script execution order window and add the Actuator script. It's a non-monobehavior class
3. Keep adding other scripts, around 6-7 scripts three errors should be thrown in console and the script execution order window should break (see screenshot)
Regression since 4.3.4f1
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
Add comment