Search Issue Tracker
Fixed in 5.3.2
Votes
0
Found in
5.3.1f1
Issue ID
755423
Regression
Yes
[Particles] Invalid AABB / InFinite errors in 5.3.1
When (some) particle systems are activated the Debug.Log spews Invalid AABB result / InFinite(d) errors. It seems to be only with particle systems manipulating meshes. Only started happening in 5.3.1
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Undertaker-Infinity
Jan 10, 2018 00:54
Hi
I've set a new particle system's Start lifetime to Infinity and got these errors.
Changing it to a number stops the errors.
Both in editor (start simulating gives the errors, stopping stops them) and in game (via play).
JotaRata
Oct 28, 2017 18:19
It still happens in 5.5, I think it may occur when you have a particle system with small particles far from the camera, and the render cannot process them because they have a size of 0
I suggest to make a script which disable/enable emission when the particls are close or far from the camera
Mijail_Bitboys
Jul 22, 2017 15:17
This is not fixed. Unity 2017.1 patch 1. This error appears when try to scale particles with hierarchy scale type selected.
BigDave66
Jul 20, 2017 16:27
Okay, since I had just made slight modification to my code before getting this error, I went back and took another look at what I did. I had accidentally //'d the line where I calculate the denominator for the velocity calculation. Since I Mathf.Clamp the velocity before assigning it, the game continued to play in spite of the error, though presumably always at maximum velocity.
Once I fixed it, those errors disappeared.
My bad. Hopefully this little bit of information will help someone else find their error faster.
BigDave66
Jul 20, 2017 16:12
I use Unity 5.6, I have made no major changes to my code, and I just started getting these errors.
The game seems to run okay, but the console is becoming loaded with these messages.
I have no particle systems in my game.
With most errors, you can click on it to find out where it's occurring. This tells you NOTHING! I don't even know what it MEANS!
If this is a bug in Unity, I can wait for a fix. If there is actually something wrong with my code, I have to be able to fix it before I can publish my game.
lucasmontec
Jun 24, 2017 19:53
Not fixed.
timothy92
Mar 02, 2017 07:58
Just had what looks like this error, spat out 214 console errors and my FPS went down to 2 for a few seconds, heres a screenshot: http://prntscr.com/eezrbq
This is unity version 5.50f3! :/
CinnoMan
Jan 31, 2017 20:55
I just got this error in 5.5.0f3!
Last change to project was adding Steamworks.NET. No idea why it suddenly happens.
kalineh
Dec 12, 2016 19:30
I'm having troubles getting a clear repro, but I think this still might exist in 5.5.0b11. Will try and narrow it down a bit more (maybe objects w/ scale = 0 issues).
Vitalii_lab
Aug 31, 2016 08:48
Reproduced on 5.4f3