Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2020.2.0a14
2020.2.0b4
2021.1
Issue ID
1281215
Regression
Yes
Scripts are showed in the Script Execution Order when they are read-only
How to reproduce:
1. Create a new project
2. Go to Edit -> Project Settings -> Script Execution Order
3. Click the '+' button to add a Script to the custom order
Expected result: read-only Scripts are not allowed to be added to the execution order and are not shown in the list
Actual result: read-only Scripts are not allowed to be added but are still shown in the list
Reproducible with: 2020.2.0a14, 2020.2.0b7, 2021.1.0a2
Not reproducible with: 2018.4.29f1, 2019.4.13f1, 2020.1.9f1, 2020.2.0a13
Notes:
1. the Scripts that are not allowed to be added belong to these namespaces: TMPro, UnityEngine.EventSystems, UnityEngine.UI, UnityEngine.Timeline, etc
2. If some Scripts are not allowed to be added to the execution order by design, then they should not be shown in the list
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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Resolution Note (fix version 2021.1):
Fixed in 2021.2.0a5