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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment