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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment