"Infinity or nan floating point numbers appear when calculating matrices for collider"

Questions & Answers
1

We are seeing a ton of these errors in our log but we have no idea how to reproduce them and there’s no information to be found online as to what this error means.

Unity support please help us!!!

2

We’ve seen this happen in our project after updating it from 4.6 to 5.1

I’m not sure why this happens to you, in our case, we had scenes that needed to be re-opened and re-saved.

3

same for me,

I ran a linux headless server for a multiplayer game with bots spawning and the spawning all the time.

After an undefinied number of hour (4 hours the less, one day the most) I get the lo filled with:

*Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path * and no user can log in.
Tried doing on an islated server, with no user that ca log in (so local bots only spawning and de-spawning) and happens the same.
No clue what causes the issue.

4

Solved.

Turns out, I was setting the float parameter in the Animator instance (in unity’s Mechanim StateMachine) to a NaN. I was doing this from inside a StateMachineBehavior, which was sitting on one of the AnimationStates of that animator

Of course, that occurred as a result of division by zero. After I unpaused the game, delta time was 0.0 for 1 frame, and I was dividing by it.

As a result, was getting these errors:

Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "MainChar/MainCharKnightPelvis"
        
Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "MainChar/MainCharKnightPelvis/MainCharKnightSpine1/MainCharKnightSpine2/MainCharKnightRibcage"
        
Invalid AABB result

Invalid AABB a
    
Assertion failed on expression: 'IsFinite(outDistanceForSort)'

Assertion failed on expression: 'IsFinite(outDistanceAlongView)'

Invalid AABB aabb
Invalid AABB rkBox
5

Had the same problem when there was a float-parameter dependent transition between two nodes in the animator and they were both empty (no clip assigned).

Assigning the clips fixed the problem.

The problem occurred only on one of two computers.

In Unity 5.6.0b3 and 5.6.0b9.

6

it only happened when i swtiched to 2018.4.26
do you know why it happens only on some computers?