Unity 5.3.1f1 - Particle system errors - Invalid AABB result / IsFinite(d)

Some particle systems are causing the Debug.Log to flood with Invalid AABB / IsFinite messages.

Test scene attached.

Steps to reproduce

1) Load Test scene
2) Press play
3) activate particle system "Stretch"

Bug report submitted:
755423 - https://fogbugz.unity3d.com/default.asp?755423_a1621g7nsq609m0g

Anyone else have the same problem?

R

Edited: Removed comment about meshes. Looks like it's particle systems that are active with no active particles.

 

Thanks for submitting a bug, could we have the number?

 

No worries, it's 755423

 

Same for me

 

Exact same issue happening for me after updating today as well

 

Yep, happenning to us too.

 

Might be particle systems that are active with no active particles (which is a very common pattern, either when effects end or for systems that are triggered by code).

I uploaded a simple particle system that exhibits the issue from our project as case 755491. Has this attached video showing the issue:

 

I have the same errors. They happen when Stop() is called on the ParticleSystem or if I turn looping off and it ends. The Render Mode is set to Billboard. Unchecking the Renderer section, stops the errors.

 

Here's a super dirty workaround, which is to count live particles and then disable the renderer if it's zero.

In our project, effects are passing through a central system already, so it's easy to glue this on in the short term. Not happy about the issue overall, though :/

Code (csharp):

1.  
2. using UnityEngine;
3.  
4. [ExecuteInEditMode]
5. public class DisableInactiveParticles : MonoBehaviour
6. {
7.     ParticleSystem.Particle[] unused = new ParticleSystem.Particle[1];
8.  
9.     void Awake()
10.     {
11.         GetComponent<ParticleSystemRenderer>().enabled = false;
12.     }
13.  
14.     void LateUpdate()
15.     {
16.         GetComponent<ParticleSystemRenderer>().enabled = GetComponent<ParticleSystem>().GetParticles(unused) > 0;
17.     }
18. }
19.  
20.  
21.  

 

I have the same issue. It can be repeated with the tank tutorial. I don't even have to play the game, just select the dust trail for the tank in the editor and the console starts logging errors. Happens in 5.3.1f1. What an annoying bug to track down. You don't expect the particle system itself to break.

 

Yeah same problems here and completely makes my project unusable. (yes, I have backups)

But what I'm concerned about is that are we going to have to wait until next friday for a non-supported patch update (5.3.1p1) to work around this? Or are they going to issue a supported fix (like 5.3.1f2) that will then be supported?

Again, a rather huge problem with a non-beta release. Where is the QA guys?

 

Doh! that freaked me out when I first ran 5.3.1 today

 

Lets hope gets fixed in the next patch release.. +1 have issue

 

If I set the Simulation Space to Local, the errors seem to disappear. Unfortunately I need to use World Space

 

Same issue here

 

Oh sheesh, I just installed this latest version this morning. Luckily I have backups to 5.1 and can load that. So selecting particles in the editor now spams the log console and there's no way to turn that off? How on earth did Unity QA team miss something like that or even let that through to public release?

 

I have this problem too (

 

Now, I can't work with my project on unity 5.3.1 because it spam the error console

 

same here :<
ULTRAFLOW 2 looks sad without the usual ton of particles

 

Deleting the library solved the problem for me.

 

Same here.

 

Same errors! And it make my game running very lag in editor....

 

Tried this on my end, did not solve it.

I get 999+ errors in less than a second as I have several things that manually emit/stop particle systems. Framerate goes to 8FPS as it never stops spamming those warnings/errors.

 

OMG...I'm still trying delete my library, hope it will works for me.
This is crazy, looks I have to switch back to old version now

 

I got the same errors and managed to fix it by creating a new GameObject and copy / pasting the particle system there as a new component. Removed the old GameObject and renamed the new one. The errors were gone!

 

I think it's time Unity starts printing additional details for these error messages. "Invalid AABB", "Error: OnDockGUI", "Error: IsFinite". These errors have been going on since 5.1.
I go to the bathroom, and come back and there are 5,000 error messages in the console, with no information.

It's impossible to troubleshoot these errors when no information is given. Instead a thousand bug reports have to be submitted because the users can't troubleshoot the problem is.

Example: I have asked for months now what "Error: Odd Tag in Cleanup" means.


j

 

Wow. A have a millions of errors.
Play a new game - try to stop a console!

PS. I'm downgrading Unity version now.

 

Same here but I also got a problem with a one shot particle which i activate through script particleSystem.Play() and it works only once it worked before the update!

 

Same problem here. If the particle system is not Looping and the Simulation Space is the 'World' (render mode: billboard) I get many error message. If I turn on the Looping, or I changed the Simulation Space to 'Local', the error messages disappear.

 

For me I have found no solution other than to completely delete the particle systems. If I just disable them, I get spammed with hundreds of "Odd tag in cleanup" error in console even when the entire hierarchy is disabled. So I have no choice but to delete the particle systems from the scene. These are basic Asset Store particle systems, no modifications done. Not controlled by any scripts.

Trying to troubleshoot this I came across another bug in Unity 5.3.1:
The Undo operation in the file menu is broken.
If you delete a gameobject, then hit play, then exit playmode, then go to file->Undo Delete Gameobject, the references to gameObjects/components are not being restored in the scripts.

 

is there any way to avoid the particle error?
we have dropped from 60 fps to 68- fps!!

 

Did you try this workaround:
http://forum.unity3d.com/threads/un...d-aabb-result-isfinite-d.374926/#post-2429887

 

This workaround is pretty desperate. You're still going to lose a lot of performance (for us we're just using it to try to get back some editor performance so we can keep working, but lots of errors are still there somehow)...

 

I have these errors too, related to RPC but didn't point to any place in my code

 

Oh man this was driving me crazy before i found this thread. Was running around trying to find where i did a mistake in the scenes.

 

Hello,
have also this bug here and the Editor is slow and buggy on Mac too!!!
If i open a bigger scene zoom in and out takes several minutes...
No Problem with Unity 5.2.x
Damn... still so many bugs in the releases....

 

Same here.
I've just filed a bug report.

 

Same problem here.
Deleting Library folder didn't helped.

 

Funny thing is that I get the same errors when playing on the editor, but when built for Android or iOS, the problems vanish.

 

This bug has been assigned to a developer and a fix is on the way.

 

good news , experiencing the issue as well

 

Disappointed that this bug wasn't picked up before release. It's put a big delay on dev

 

Do we have an ETA on the fix? I need to release a build tomorrow at the latest - and one of our plugins requires 5.3...

 

Hi,
Do we have an ETA on the fix? I can't go back to version 5.3 because performance issue.

 

I have the same issue, for me when I checked the offending particle systems in the inspector there is a little white ! next to the plus sign under the main particle settings. Hovering over says "Automatic culling is disabled because: 'insert list of reasons' " most commonly I found being "Word space simulation is used", changing/removing whats listed seems to fix the issue. This isn't ideal, but for me means I don't have to revert back to 5.2 and just have to deal with it until 5.3.1p1.

 

Awesome dude! Thank you for the update.