Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0f3
Issue ID
945620
Regression
No
Transform component values can be set to NaN in Build but not in Editor
Steps to reproduce:
1.Open attached ‘InconsistentNaNBehaviour.zip' Unity project
2.Enter Play mode
3.Press Space
4.Build and run project
5.Press Space in Build
Expected results:
Editor and Build behavior is identical
Actual results:
Invalid input errors appear in Editor and Transform values are not set to NaN, whereas in Build the values are set to NaN
Reproduced in: 2017.3.0a7, 2017.2.0b10, 2017.1.1f1, 5.6.3p2, 5.5.4p4
By design: In the editor and development builds of players we provide additional error messages to help diagnose issues. These are disabled in release players to reduce any overhead they might cause.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment