Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a4
2018.4
2019.2
2019.3
2020.1
2020.1.0a14
Issue ID
1201929
Regression
Yes
Script Execution Order does not save other values when edited before the first value is applied
How to reproduce:
1. Open attached project "Case_1201929"
2. Open Edit -> Project Settings -> Script Execution Order
3. Edit value of "NewBehaviourScript"'s order
4. Click on the "NewBehaviourScript1"'s order with the first one still in editing mode
5. Change "NewBehaviourScript1"'s order and click "Apply"
Expected result: both execution order values are applied
Actual result: the second value is reverted back to the original value
Reproducible with: 2018.3.0a4, 2018.4.14f1, 2019.2.15f1, 2019.3.0f2, 2020.1.0a15
Not reproducible with: 2017.4.35f1, 2018.3.0a3
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
- 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
Resolution Note (2020.1.X):
By-Design. When the text field related to execution order is being edited, the editor believes that the reorderings are incomplete and hence doesn't save them. To persist the values, the user has to either hit return or shift focus away from the text field that is being edited.