Search Issue Tracker
Won't Fix
Votes
3
Found in
2017.3.1f1
Issue ID
1037497
Regression
No
During heavy calculations, NaN values appear and cause a lot of various errors
To reproduce:
1. Open the project, attached by the user (Cell Damage.zip)
2. Open the "Cena01" scene
3. Enter Play mode
4. Wait a few seconds until the errors appear in the console
Expected: the assertion errors do not appear in the console
Reproduced in 2017.1.4f1, 2017.2.3f1, 2017.3.1f1, 2017.3.2f1, 2017.4.3f1, 2018.1.0f2, 2018.2.0b4, 2018.2.0b11, 2018.3.0a1, 2018.3.0a3
Comments (2)
-
xTyler73
Jan 12, 2019 22:45
Workaround script for the root object:
void LateUpdate() {
foreach (Transform child in transform)
if (float.IsNaN(child.transform.localPosition.x))
Destroy(child.gameObject);
}From this post: https://forum.unity.com/threads/the-dreaded-invalid-aabb-errors.463144/
Deleting the root object and spawning the children separately may work for some, but didn't for me. -
xTyler73
Sep 24, 2018 15:38
Any ineffecient / hack workarounds for the time being?
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.