Search Issue Tracker
Duplicate
Votes
31
Found in
5.3.1f1
Issue ID
754687
Regression
Yes
Errors about "Invalid AABB result" appear in console while running a scene
Regression from Version 5.3.0f4 (2524e04062b4)
Repro steps:
1. Open attached project
2. Run the "Level" scene
==>
aabb.IsFinite()
IsFinite(outDistanceForSort)
IsFinite(outDistanceAlongView)
Invalid AABB result
Invalid AABB a
-
mayasarii876
Mar 09, 2022 03:02
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 -
zarex7
Feb 16, 2020 06:46
in 2020.1.23 bug "Invalid AABB a" after open project exist
-
Skjalg
Oct 11, 2017 08:29
I had a SkinnedMeshRenderer with Bounds (Center and Extents) set to NaN, Infinity and -Infinity. Resetting these fields to actual valid numbers made the error go away
-
Kurius
May 22, 2017 00:49
For what it's worth, I experienced the error "UNITY Invalid AABB a" when I was trying to dynamically change localPosition of Content beyond the verticalNormalizedPosition of a ScrollRect of a ScrollView. In other words if you have a hierarchy of Canvas -> Scroll View -> Viewport -> Content. If you try to move that Content beyond the boundaries of the Scroll View, then the localPosition of the Content may contain values of NaN, and then throw the aforementioned error. To avoid this, prior to moving the Content, temporarily set verticalNormalizedPosition to either 0 or 1. Those are the boundaries of the Scroll View. When set to 0 or 1, check the resulting localPosition of the Content. Were you going to try to move the content beyond the value of that localPosition? If yes, that means you were about to experience the aforementioned error.
-
anton22
Mar 31, 2017 03:25
unity 5.6 have this bug
-
salex100m
Jan 12, 2017 17:23
Also started getting a flood of AABB invalid errors related to adding a Trail Renderer to moving object (fast moving, fast turning).
The Trail Renderer has the particle/additive (soft) shader attached to it.
-
BubbaRichard
Jul 16, 2016 04:45
although this is an old post, everywhere I've gotten these errors there is a NaN value in a float or double.
Regards -
tbrewerart
Jan 25, 2016 03:54
1000+ of the above errors in 5.3.1 in a math asteroids kind of game but not a single one in last iteration of Unity.
Collisions seemed to set it off. No obvious problems with transforms, scale, colliders. etc. Performance seems fine. Went back to 5.3.0f4. Spent a 1/2 day looking for issueWaiting with baited breath for patch, or next release. Thanks
-
rjmyth
Jan 20, 2016 10:03
Hey guys. I fixed this by updating the Unity 3.1.3p3 patch
-
irfan_omi22
Jan 08, 2016 18:53
Problem is seriously effects performance. But if you Build and then Run the game, there seems to be no problem at all. It runs smooth and fine.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
This is a duplicate of issue #755423