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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment