Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4.1f1
2020.2
Issue ID
1257654
Regression
No
BoundsInt.xMin and BoundsInt.yMin are confusingly clamped to xMax and yMax
How to reproduce:
1. Download the tester-attached script(BoundsTest.cs)
2. Create a new Unity project and import the script
3. Attach the script to any GameObject
4. Enter Play Mode
Expected result: after setting boundsInt.xMin to 2, its logged value is 2
Actual result: after setting boundsInt.xMin to 2, its logged value is 0
Reproducible with: 2018.4.24f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a16
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2020.2.X):
The Unity Scripting API Documentation has been updated to make this behaviour clearer.