Search Issue Tracker

Won't Fix

Votes

0

Found in

2018.4

2019.4

2019.4.5f1

2020.1

2020.2

Issue ID

1279809

Regression

No

[x86] Custom function with float return Type returns NaN values in Build when built to Windows x86 release

Windows

-

Important - the issue is only reproducible when Windows x86 release architecture is selected

How to reproduce:
1. Open the attached project named "ReturnValueBug_all"
2. Open the "BezierTest" Scene
3. Enter Play mode and observe the expected result
4. Set the Architecture to Windows x86 and Build the project
5. Launch the build and observe the game screen

Expected result: The build behaves exactly the same way as in the Editor
Actual result: The Bezier curve is not rendered and the Debug log shows that CubicBezier.EvaluateTangent is returning NaN values

Reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.8f1, 2020.2.0b4

Notes:
1. Does not reproduce when the project is built using Windows x86 + Development mode
2. Does not reproduce with Windows x86_64 and MacOS

  1. Response avatar

    Resolution Note:

    This was fixed by large floating point optimization (float32) in Mono that is a breaking change. As such, we won't be backporting a fix. However, the next Mono upgrade will contain these changes and thus fix this behavior.

    Upstream Mono Issue: https://github.com/mono/mono/issues/20458

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.