Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.




Found in


Issue ID




Transform.position() values becomes to NaN when one GameObject rotates while colliding the edge of another GameObject




Priority: 4Not yet prioritized for a release


Severity: 2Core functionality majorly impacted

To reproduce:
1. Open repro project
2. Play scene
3. Using arrow keys (or w,a,s,d) move cube to the corner of ground

Expected: when cube('player' game object) collides with 'ground' corner, player's position values should not be set to NaN

Regression started in 5.5

Reproduced on: 5.5.0a6, 5.5.2p1, 5.6.0b11, f1, 2017.1.0a3
Not reproduced on: 5.4.4p3

Comments (21)

  1. 5a88d05f7ca6be7d914f8bb69ab7b1d5?d=mm


    Dec 05, 2018 05:33

    In 2017.3.0f3 this error was killing the game both in the editor and a build, fixed it by following the suggestion of changing physics contacts generation to legacy.

  2. 17ff582e78fbc004af5d616e53a11645?d=mm


    Nov 22, 2018 23:14

    I was having this problem happening all the time (in 2017.4.15, editor and builds), but as was suggested in an earlier comment, switching contacts generation from PCM to legacy in the physics manager does seem to avoid the issue.

  3. C07dea1c1b907ae4fa425668bb834c11?d=mm


    Nov 10, 2018 11:33

    still happening in 2018.2.15f1 =(

  4. 812cc0df82ac3c53e228096c728b68cc?d=mm


    Oct 30, 2018 08:46

    This might only be loosely related and pretty specific, but, if you're using MeshColliders, check the collider mesh for vertex doubles (vertices at almost the same position) and remove them.

    I had the AABB issues and removing doubles in the Collission Mesh fixed them.

  5. 376bb5de57ba9f9a9bcc8035c03768f1?d=mm


    Oct 04, 2018 21:42

    Update: I dug in some more to see if there was a workaround. Turns out it wasn't Physics.OverlapSphere(), that was just where the error was appearing... In very specific conditions Physics.ComputePenetration() was sending back the "out Vector3 direction" with direction.z being NaN. This gradually infected the entire data until the position of the collider itself was all NaN and the Physics.OverlapSphere() generated the game-crashing error.

    The error seemed to be that the point of collision was positioned EXACTLY at z=0 in world space. I was finally able to fix it by sanitizing the data immediately after my Physics.ComputePenetration() call:

    Physics.ComputePenetration(coll1,coll1.transform.position,coll1.transform.rotation, coll2, coll2.transform.position, coll2.transform.rotation, out direction, out distance);

    direction.x = 0f;
    direction.y = 0f;
    direction.z = 0f;

    If you're not using code and this is just happening within the physics engine, you might try making the place where the problematic collision is happening just a little bit "off." Rather than (0,0,0) make it (.001,.001,.001) or tweaking the angle a little bit.

    Ultimately I'm guessing this is a problem with PhysX, but maybe Unity can sanitize the data in it's wrapper functions?

  6. 376bb5de57ba9f9a9bcc8035c03768f1?d=mm


    Oct 04, 2018 19:32

    We just ran into this in 2017.4.3f1

    Isolated it down to a Physics.OverlapSphere() call which generates the error message(s). Works 99.9% of the time, but when that .01% happens the game completely crashes on Android.

    I realize this is likely something wrong on the PhysX side of things, but still really need at least a workaround. Tried PCM and Legacy in the Physics Manager. Both generated the same error:

    10-04 13:04:54.331 20229 20251 I Unity : Trying Overlap Sphere
    10-04 13:04:54.331 20229 20251 I Unity : (Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)
    10-04 13:04:54.331 20229 20251 E Unity : Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "SceneCameraColliders/HeadCollider"
    10-04 13:04:54.331 20229 20251 E Unity : (Filename: Line: 210)

  7. 88f26214912f58c19e2d840933db8655?d=mm


    Sep 24, 2018 21:29

    Still happens in 2017.4.8, pretty much 1.5 years later...

    Noticed in the editor and not checked builds

  8. Afa6042b0e85e863b04ecd61c0ef72f3?d=mm


    Jul 24, 2018 02:43

    FYI, I can confirm that this error still occurs in 2018.2.0b8

  9. 815b84a27579d9780435b96d7677c557?d=mm


    Mar 29, 2018 21:02

    I just noticed this issue in 2017.3.1, only in the builds (not in the editor).

  10. 63cd3c0a302c34f9519f06f08812bd0f?d=mm


    Mar 11, 2018 08:27

    Solution was easy. Simply disable PCM in PhysicsManager!

All about bugs

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