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.
Postponed
Votes
36
Found in
5.5.0f3
Issue ID
891250
Regression
Yes
Transform.position() values becomes to NaN when one GameObject rotates while colliding the edge of another GameObject
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
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Graphics.Blit() performs the operation only to the last display when a multi-display environment is used
- [Windows] Multiple Separation Lines are present in the Light Create Menu
- Warning "Item m_LightProbeSystem not found in window PC_RPAsset" logged when navigating to RP Asset from Probe Volume Component
- Editor UI is pink when a project has builtin_shaders-2021.3.11f1
- Tessellation has poor performance in URP when rendered using Metal
CageyKG
Oct 14, 2017 01:03
Is there any source of info we can follow for updates or roadmaps on this issue? It's severely impacting my game and (sounds like) many others'.
AndersMalmgren
Sep 14, 2017 08:37
This needs to be addressed now along with other Rigidbody related bugs like the
INVALID PARAMETER POS IN RIGIDBODY.TRANSFORMCHANGED BECAUSE IT WAS INFINITY OR NAN
and
Infinity or nan floating point numbers appear when calculating the transform matrix for a collider
Our game is released on Steam and the customers and not happy!
Malkin8
Jul 01, 2017 19:16
This is ridiculous! This renders my game unplayable until a fix is made. Why has this still not been sorted out?
jkraptor
Jun 19, 2017 16:19
I had the same problem in Unity 5.5. Disabling colliders before the translation/rotation and then enabling them after (in a delayed co-routine) was a workaround. In Unity 5.6.0f3 this is no longer a problem for me. Appears to have been fixed. Can anyone else confirm?
JoeHoran
May 15, 2017 19:55
Still an issue in 5.6.0f3
Getting the errors:
Invalid parameter pos in Rigidbody.TransformChanged because it was infinity or NaN
Invalid AABB a
Assertion failed on expression: 'IsFinite(d)'
Assertion failed on expression: 'IsFinite(outDistanceForSort)'
Assertion failed on expression: 'IsFinite(outDistanceAlongView)'
Invalid AABB aabb
Invalid AABB rkBox
mQe
Apr 18, 2017 09:22
How can this not have more votes? This error crashes my game or causes severe fps drops because I have lots of rigidbodies that get NaN in position. This makes my game completely unstable and I can't release a new build before this is fixed :/