Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0f3
Issue ID
980017
Regression
No
Setting invalid values in a RectTransform doesn't throw any errors and leads to new issues
It is possible for the user to set 'Inifinity' and 'NaN' values in a RectTransform which can lead to obscure behaviour.
It's pretty easy for a user to make a mistake and end up doing this by accident. However, it can be a bit of a nightmare to track down where the initial point of failure was due to a lack of error reporting and the obedience of the UI system to try and obey nonsensical sizes and positions.
Reproduction steps:
1. Download + Open StupidScene in the attached project
2. Press Play
Expected result: A very clear error telling me I set a stupid value for the size of the RectTransform (and preferably either no change to the size of the RectTransform, or a change to (0, 0))
Actual result: Obscure NaN values and an 'Invalid AABB inAABB' error (if using the 'SetInfinite' StupidTask)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Masks affect Sprite Renderers outside their range when a Light2D is present with specific Target Sorting Layers selected
- URP Lens Flare is rendered in the wrong position when Render Graph Compatibility Mode is enabled and Render Scaling is not 0
- Editor crashes on DrvPresentBuffers when loading RenderDoc while using OpenGLES 3.0 or OpenGLES 2.0 Graphics API
- [Test Runner] Incorrect name under Window > Panel after project restart
- [iOS] Crash when using fallback fonts created at runtime
Add comment