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

I am using a different ocean system in our main project and didn't get the error until 5.3.1p1 (maybe even 5.3.1, but the AABB error was spamming me out)

I was able to recreate it and send a case for it using water4 though, so it has something to do with using a second camera, possibly rendertextures like you say

 

I've got the same issue. Really hard to trouble shoot without a reference to the thing that's a problem

 

@Alabatross, I think i isolated the issue. If you set the reflection/refraction cameras not to render the layer where the particles belong to, the error stops to appear. It happened on my end.

 

Oh, & the patch fixes it!

 

Thanks for the quick turnaround on that fix, guys. You made my Christmas.

Hope you guys have a good holiday.

 

Same errors here... just tried to run the sample scenes and they lag extremely bad, stretch images on the screen, and give me loads of errors. Everything worked great in 5.1.1f1 before I updated.

 

Which version did you try?

 

Having some extra logs...
a mix of particles and raycast? ...

 

Dito same thing over here, as soon that an particle emitters particles die it causes problems, in my case the main dir light toggles worked fine with 5.2.3 now with 5.3.1f1 it's a mess.

 

I had several errors in 5.3.1f1 that were fixed in 5.3.1p1. Have you tried the latest patch?

 

Same happening here. Getting:

aabb.IsFinite()
IsFinite(d)
UnityEditor.DockArea:OnGUI()
IsFinite(outDistanceForSort)
UnityEditor.DockArea:OnGUI()
IsFinite(outDistanceAlongView)
UnityEditor.DockArea:OnGUI()
IsFinite(outDistanceForSort)
UnityEditor.DockArea:OnGUI()
IsFinite(outDistanceAlongView)
UnityEditor.DockArea:OnGUI()
IsFinite(d)
IsFinite(outDistanceForSort)
IsFinite(outDistanceAlongView)
​

Nice to see that I'm far from being the only one and great if a fix is under way. But regarding errors like this, wouldn't it be nice for the editor to point out the component that's causing the issues? Would it be possible to change it like that.

And as a sidenote: I just wish there were others having this issue as well:
http://forum.unity3d.com/threads/un...rd-and-viking-village-sample-projects.375643/


ed: oh...

What you posted there actually resembles the random effed'upness I'm having with eg. the CourtYard demo (in the above linked thread). Is that demo working fine for you?

 

For everyone posting errors, make sure you're running 5.3.1p1, available to download here:

http://unity3d.com/unity/qa/patch-releases

 

Ah right, sorry. Not getting that error any more, although still curious about what I said in that post:

But regarding errors like this, wouldn't it be nice for the editor to point out the component that's causing the issues?​

I'm also still getting these errors when loading the Viking Village demo project:

Failed reading from: '04/049385954893a938cd297f9b46f42dd0.rpc.sse'.
Failed loading probe set data for hash: 0x049385954893a938cd297f9b46f42dd0
Error adding system: Data not available.
​

And still suffering from the graphical issues mentioned here: http://forum.unity3d.com/threads/un...rd-and-viking-village-sample-projects.375643/

 

Yeah I agree, this would be ideal. These kinds of errors are probably asserts much farther into the pipeline, though--like some piece of rendering code that's just checking the data it's about to render. Tracing that all the way back to the GameObject/Component it came from is probably a bit of work on Unity's end :/

 

Yep, that is very likely true. Every now and then things like this still probably happen, so unless it would require a serious renovation or added complexity throughout the codebase, it would be something to consider putting some effort into. For now of course the main thing is that the bug itself got fixed.

 

Yeah, I can confirm this. I did a repro on this with Unity 5.3.1p1.

You use the WaterProDaytime shader from the Standard Assets Package. You put the water Plane to 0 or near 0. You put the Scene view to ortho cam. You align with the Y axis (from above view). Now you align with Z (side view). The console gets spammed with

Code (csharp):

1.  
2. Screen position out of view frustum (screen pos 0.000000, 0.000000, 47194.425781) (Camera rect 0 0 1024 1024)
3. UnityEngine.Camera:Render()
4. UnityStandardAssets.Water.Water:OnWillRenderObject() (at Assets/Standard Assets/Environment/Water/Water/Scripts/Water.cs:108)
5. UnityEditor.DockArea:OnGUI()

messages. If you exclude the TransparentFX layer from the water Reflect/Refract layers the problem does not occur. In my repro scene the only object using that layer is a ParticleSystem game object.

 

I could not run my project on p1 lot's of error trying to load it - didn't screenshot them though probably some 3rd party stuff issues so I turned back to f1

 

it's not really random - it is somehow bound to the particles - once an emitter has 0 alive particles it seems to be happening

 

I just installed Patch 5.3.1p1 and it runs the same errors...

 

5.3.1p1 - Water4 Advanced, as soon as I press play and look at water console gets spamed with IsFinite() message. Haven't much time to investigate yet, but it looks like something wrong with reflections in water.

 

Yeah I'm getting IsFinate errors too. For me, it's being caused by a WaterProDaytime and many particle systems.
No fix yet?
I'll just use unity 5.2.4

 

The Tanks demo recreates its nicely - guys at Unity, just run your demo code on Unity 5.3.1 to see the problem.

 

5.3.1 and then the latest patch. I think it was 5.3.1p1

 

I tried 5.3.1p1 and unfortunately still received tons of the AABB type errors. The lag was gone and everything was playable again, but lots of errors. I'm running this on an iMac 27 inch late 2014 mode if that helps. I was in a rush to complete something and switched down to 5.2 at the time, so unfortunately I don't have more helpful info than that.

I'll try again on a future version and see how it goes.

 

Hello, I'm on 5.3.1f1 and I encounter this bug after upgraded from 5.3.0. The AABB errors occur whenever I emit particles. What information can I collect for you?

 

When will you release the next updated version of Unity ?

 

I'm guessing after new year's day. They also need a rest

 

I think half of the problems are people not understanding 5.3.1f1 and 5.3.1p1. Perhaps this can be further clarified for people who typically miss small details (for the bounding error).

 

I do agree, I'm not sure why people still confused about what a patch release is also.
We may never understand, but that's why its so so so critical whenever Unity do a major release 5.3 etc that in the first week or two weeks of upgrading it has to be hardcore tested release with no major bugs.

As you can see whats happened, 5.3 came out bugged up and although Unity quickly released 5.3.1 and then 5.3.1patch1 the forums already flooded with issues from the original 5.3 release. Really 5.3.1patch1 should have been the 5.3 release.

Hence hope lessons been learn t, now people just need to monitor patch releases each week, although can be a pain and not good for customers, some of them really do contain Critical fixes and I recommend people read release notes at least before decision been made to upgrade.

@subzer0 Did you read the Unity blog on patch releases, really joke question to ask really considering they just released a major update week or two ago.

 

@MrEsquire, I want to build my game on webplayer, and patches cannot build or release a Web Player game. I asked because I wanted to know, before rolling back to previous version, if any update will be released soon.

 

Well you not asking the correct question, if a update is released next week, what exactly you expect in it, web player support or bug fixes, maybe best to start a new thread.
Because this is related to the particle issues in 5.3

 

Ok sorry..

 

QA much?

 

the unity5.3.1P1 get this error `System.IO.File' does not contain a definition for `WriteAllLines'

 

Is this with the 5.3.1f1, or with 5.3.1p1?

 

Oh man same problem here... okay ill update patch and report back if i still have this issue. I'm rotating Particles in world space. Hope its not crashing Android as i just pushed out an apk file for some people to test guess i should check real quick on my phone.

Edit: Okay patched fixed it for me. i did not see any issues on android with the error but who knows whats happening in the back ground and i didn't setup the debug environment to see. Thanks Unity for the patch.

 

The patch (5.3.1.P1) seems to have only fixed some of the issue for me.
The AABB issue is gone but I am still being flooded with IsFinite(outDistanceForSort) error messages.

 

Hack that worked for me: If you are using any render Textures (for reflection and such) put all your particles in a layer where the render texture camera does not render them.

 

Thanks for the hack. It was useful and I started to do this, which on thinking about it, was probably a good idea anyway for a bunch of the particles, however some of them will not work. For example, if you have a burning boat on water, the reflection will look strange if the particle based flames are not reflected too.

I guess I need to wait for a Unity fix in the next patch hopefully.

 

I see a new patch has been released, but it seems no mention of this spamming IsFinite(outDistanceForSort) particle error message bug.

 

I have this problem too (

 

I have the same issue with unity 5.3.1f1

It happens when my fireworks particle count gets to 0

 

The issue is not solved in 5.3.1f1. It is solve in the patch release 5.3.1p1.

 

Ahhhh.. Thanks for that. I was unsure of what the p stood for. Furthermore, I didn't realize there was a whole page dedicated to patches

Thanks for that... its installing now. I'll let everyone know asap my results..