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
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Add comment