Search Issue Tracker
By Design
Votes
1
Found in
5.3.0f4
Issue ID
752123
Regression
No
Script Execution Order not respected across scenes, each scene has its own Script Execution Order
Steps to reproduce:
1) open the attached project
2) open 'BaseScene' and drag 'AdditiveScene' into hierarchy
3) play
4) observe console for execution order
Actual behavior(attached image): Ordering is separate for every scene
Scene1: Highest -> lowest -> Scene2: Highest -> lowest
Expected behavior: Ordering should be independent to scene
Highest -> lowest
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
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
Resolution Note:
This is by design