Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.1f1
Issue ID
1118281
Regression
No
Setting Canvas Plane distance to 0 and a Render mode to Screen Space - Camera breaks its elements and sets some values to NaN
How to reproduce:
1. Download and open my attached repro project "118281.zip"
2. Notice the Canvas in the Hierarchy and make sure that the Render mode is set to "Screen Space - Camera"
3. Set Canvas Plane distance to "0"
4. Create some UI element inside the Canvas (exp UI -> Button) and notice that some values turn into NaN
Expected result: NaN values should not be displayed
Actual result: Some values of Canvas and its child elements turn to NaN
Reproducible with: 2018.3.7f1, 2019.1.0a1, 2019.2.0a1, 2019.2.0a4
Not reproducible with: 2019.1.0b5, 2019.2.0a6
Note: This happens with Standalone and other platforms
Errors like these are being thrown out: transform.localPosition assign attempt for 'Button' is not valid. Input localPosition is { NaN, NaN, 0.000000 }.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (2019.2.X):
Low priority defect for the moment. This bug is unlikely to be fixed in the near future.