Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2018.4.X, 2019.4.X, 2020.2.X
Votes
0
Found in
2018.4
2020.1.5f1
2021.1
Issue ID
1282571
Regression
No
int.MinValue is treated as largest value when sorting List<IOrderedCallback>
How to reproduce:
1. Open the user's attached project("IOrderedCallback.callbackOrder.zip")
2. Open Test Runner window
3. Select the EditMode tab
4. Press Run All
Expected results: When sorting with int.MaxValue or int.MinValue the sort is correct
Actual results: When sorting with int.MaxValue or int.MinValue, int.MaxValue is treated as larger than int.MaxValue
Reproducible with: 2018.4.28f1, 2019.4.13f1, 2020.1.10f1, 2020.2.0b8, 2021.1.0a1
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
- Crash on block_remove when a scene is opened in a specific project
- The GameObject with a Hinge Joint Component does not return to the initial position when the Use Motor property is toggled off
- The construction of a specific class breaks the binding Bool references and does not allow them to be toggled on back by hand when working in the Custom Editor window
- AssetReferenceAtlasedSprite creates a copy of the Sprite during Addressables.LoadAssetAsync<TObject> which does not release when Addressables.Release is used
- Crash on TryToRegisterMonoScriptToHashMap when importing a specific .unitypackage
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0a8 and above
Resolution Note (fix version 2020.2):
Fixed in Unity 2020.2.2f1 and above
Resolution Note (fix version 2019.4):
Fixed in Unity 2019.4.19f1 and above
Resolution Note (fix version 2018.4):
Fixed in Unity 2018.4.32f1 and above