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
35
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
- [2020.3] Play Mode has visual artifacts when Graphics API is set to DirectX12 with Dynamic Resolution enabled
- White texture appears when setting “RenderTextureFormat.Depth” to “RenderTexture” on the Camera
- Cursor is visible when using “Cursor.lockState = CursorLockMode.Locked” and “Cursor.visible = false”
- Material.SetOverrideTag setting LightMode tag has no effect
- Decal is not rendered when in Camera component Culling Mask dropdown field Default is unselected
mayasarii876
Mar 09, 2022 08:26
http://103.56.148.201/
http://103.56.148.201/newmpo
http://103.56.148.201/mpo17
http://103.56.148.201/mpomm
http://103.56.148.201/mpotower
http://103.56.148.201/parisklub
http://103.56.148.201/juraganslot
http://103.56.148.201/mpo500
http://103.56.148.201/mpokick
http://103.56.148.201/mpoyes
http://103.56.148.201/xyzklub
http://103.56.148.201/betmpo
http://103.56.148.201/ogslot88
http://103.56.148.201/hoki777
http://103.56.148.201/mpojuta
http://103.56.148.201/299slot
http://103.56.148.201/mpo188
http://103.56.148.201/mpogacor
http://103.56.148.201/mpo300
http://103.56.148.201/rgo365
http://103.56.148.201/kingdom288
http://103.56.148.201/wigompo
http://103.56.148.201/mpo8899
http://103.56.148.201/mpopelangi
http://103.56.148.201/mpo555
http://103.56.148.201/dutampo
http://103.56.148.201/klik368
http://103.56.148.201/388hero
http://103.56.148.201/19dewa
http://103.56.148.201/mpoxl
http://103.56.148.201/mpoas
http://103.56.148.201/mposun
http://103.56.148.201/qqslot
http://103.56.148.201/mposport
http://103.56.148.201/dewa234
http://103.56.148.201/mesinmpo
pazenkin
Jul 28, 2021 07:24
The methods presented in the comments here did not help me. Here is my option that helped and does not affect the FPS: https://github.com/pazenkin/RigidbodyFixer
pazenkin
Jul 26, 2021 23:01
The error is relevant in 2019.4.6. Is there any solution?
pazenkin
Jul 26, 2021 23:01
The error is relevant in 2019.4.6. Is there any solution?
Butterweich
Jun 04, 2020 13:21
I had the same problem with Unity 2017.4.40f1.
My solution:
Mesh Collider Convex off.
I have a platform that rises and falls. The player goes on the platform and the first person controller everything on NaN.
Mesch Colider of the platform (with sloping and protruding elements) had Convex on.
Many thanks to the answers here!
firstuser
Feb 26, 2019 23:18
Still happens in Unity 2018.2.19f1 and above, super frustrating
Adam-Bailey
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.
danger726
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.
s_a_l_v_a_t_i_o_n
Nov 10, 2018 11:33
still happening in 2018.2.15f1 =(
tBurger
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.