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

If the game already uses a lot of threading, would it still be faster ? Is there an option to batch instead of multithread for example (through code perhaps ?). I think batching when emitting meshes would be essential though (especially for effects that may have static particles emitted once).

The isFinite issue and the Out of view frustum issues are both happening in the water reflection script in camera.render(), so there is definitly some connection and a more global issue, so i think it is worth investigating, also now it has been creating more errors (the isFinite for example) in relation to particles, which could show both a missing check in the render() and a particle going out of bounds issue.

Thanks

 

Since webgl does not support threading, does this mean that particle system performance took a hit on that platform?

 

I have tested the new v5.3.2 with Sky Master ULTIMATE and Water 4 reflection and i still get the "!IsFinite(outDistanceForSort)" issue when particles come in the scene.

This error did not happen in Unity v5.3.0 so i hope will be solved soon.

 

It only happens when particles come in, so i suppose they could be related. (the "!IsFinite" issue) considering also the new changes in the particle system and that it did not happen before e.g. in v5.3.0

The frustum errors are not related to particles only, they point to the same code line though so there may be some connection (camera.Render() function in Water 4 reflection script) and i had those since Unity 5 release i think.

Thanks for the information, i will wait for the patched version to see if it is fixed.

Is there any way to eliminate these non destructive internal errors from appearing in the log ? So it does not create any slow downs.

 

[QUOTE="karl.jones, post: 2483824, member: 834128"The isFinite issue is an assertion that is caused when the AABB is incorrect. Seeing this message is not guaranteed to be the particle bug which was fixed in 5.3.1p1 so if you are still seeing it then it could be something else.[/QUOTE]

Why are assertions turned on in the versions you ship? Is it to enable people to submit bug reports about under the hood problems?

It would be nice if more of the assertions actually told us what was the issue, and indicated if we should report them. When my console tells me "modifications.empty()" at random intervals, that's not really helping anyone.

 

It seems the patch is now out. 5.3.2p1!!

 

Great!! Was it released ahead of schedule? Those particle issues were really annoying, thanks for the fixes!

 

It's NOT fixed in 5.3.2p1

Code (CSharp):

1. IsFinite(outDistanceForSort)
2. UnityEngine.Camera:Render()
3. UnityStandardAssets.Water.PlanarReflection:RenderReflectionFor(Camera, Camera) (at Assets/Standard Assets/Environment/Water/Water/Scripts/PlanarReflection.cs:200)
4. UnityStandardAssets.Water.PlanarReflection:RenderHelpCameras(Camera) (at Assets/Standard Assets/Environment/Water/Water/Scripts/PlanarReflection.cs:97)
5. UnityStandardAssets.Water.PlanarReflection:WaterTileBeingRendered(Transform, Camera) (at Assets/Standard Assets/Environment/Water/Water/Scripts/PlanarReflection.cs:114)
6. UnityStandardAssets.Water.WaterTile:OnWillRenderObject() (at Assets/Standard Assets/Environment/Water/Water/Scripts/WaterTile.cs:59)
7.  

 

Sigh, then can we PLEASE have a stable build!??? I had to skip all of the fixes in 5.3.1 because of bugs, now looks like I have to skip 5.3.2.

 

5.3.2p1 sadly did not fix this issue at all. What's the deal, fellas? =(

The only thing that's changed is that I actually get an additional error thrown into the mix:

Converting invalid MinMaxAABB

 

Sent a repro project and bug report.

https://fogbugz.unity3d.com/default.asp?765796_voj44q71dv7e41gl

 

DUDE!! You are da man! That was exactly the issue I had and the resolution. Can't thank you enough.

 

confirm
particles still broken
correct me if i dont right, but i thing it was.... 6 patches fixing problems with particles
all tools in asset store based on suriken is... broken...

is there alternative for completely replacing internal particles?

 

I hope v5.4 gets at least a month of public release as beta before the official release, since this version brings the most radical changes by far and has the potential to break things more than any other version imo (touching on multithreading with extra error handling, DX9 shaders etc)

There are some non Shuriken packs, one is DX11 and the other is called Particle Field i think, i read in the forum this does not use Shuriken. Also there is cool free GPU particle work by Keijiro (which i may use as base for my own GPU particle system as well that will extend my Particle Dynamic Magic system later)

Link: https://github.com/keijiro/KvantSpray

 

yes its 5.3.2p1
we are team of developers (near 15 machines with unity), we have a project with weather and rain inside. and the rain is show us finite errors. same version of unity on different machines.

unity was install from scratch in empty folder. not just replacing previous.

 

thx.
atm we have 2 machines without any problems. we trying to understand what is going on. when we find our fish, we will report.

 

Just to add my voice, I'm still seeing the same IsFinite spam in VR mode with 5.3.2p1. I don't have time to throw together a test package right now.

The only difference is before the errors occurred when my player's Y was rotated between 0 and 90 degrees, and now it's more like ~288 to ~80 degrees.

 

same thing. rotating camera in some angle stop spaming errors

 

https://fogbugz.unity3d.com/default.asp?765796_voj44q71dv7e41gl

It appears that our AABB IsFinite issue has been fixed, but not until the release of 5.4... which I'm assuming will be a month or longer, which is a long time to wait since we've already had to deal with the bad performance for a month.

Is there any way we can get this fix in a patch release? Or at the very least, a workaround that allows me to use my particle systems?

 

I have downloaded the 5.3.2p1 and it fixed my "Invalid AABB a" and other similar errors. However, I now have a different compilation error which did not occur with earlier version of Unity.

The error message I am getting is:
Assets/Daikon Forge/DFGUI/Editor/dfScriptWizard.cs(200,39): error CS0117: `UnityEditorInternal.InternalEditorUtility' does not contain a definition for `AddScriptComponentUnchecked'

I do realise that the issue is with the DFGUI asset from Daikon Forge which I bought on the Asset Store and I am also aware that this asset shows as "Deprecated" since Unity 5 was released. However, this error message did not occur prior to upgrading to 5.3.2p1. So before I re-write all my UI (which would be a ton of work for a single indie/ noobie developer ), any chance someone could let me know if they've seen such problem before and have managed to solve it. By the way, I have also emailed the Daikon Forge developer but I have yet to hear back from them.

Many thanks for your help

 

I can also confirm that 5.3.2p1 fixed all my issues with the crazy particle errors. Thanks guys!

 

5.3.2 also fixed this issue for me, merci.

 

I'm seeing this problem in 5.3.1f1 (that's the latest version I see available for download). If I set the space to Local, I get no errors, but the particles will only play once, Play() does nothing after that. If I set the space to World, it plays correctly, but I get a stream of errors in the editor and while playing.

 

@John B

The current unity version is actually 5.3.2
https://unity3d.com/get-unity/download?ref=personal

Try 5.3.2p1

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

 

This issue 756786 was closed as being fixed but it is not fixed in the latest build 5.3.2.P1
Shown here https://issuetracker.unity3d.com/issues/isfinite-error-spam-with-particles-and-second-camera
Mind you title does say 2 camera setup which is not correct as it happens with single camera also. Anyway the issue is not fixed as claimed for IsFinite(outDistanceForSort) so issue 756786 should still be open.

 

When I download from that first link, I get an installer called: UnityDownloadAssistant-5.3.2f1.dmg, which is what I already have. I'll try the patch release.

Oops, I misread the numbers. I saw the "f" and didn't notice the 2 in front of it.

Update: 5.3.2p1 seems to have fixed the problem. The particles now play more than once, and there's no errors when I switch to World space.

 

I still see IsFinite() errors in both 5.4.0b3 and 5.4.0b4 when my player's rotation is from roughly 10 to 90 degrees.

Plus there's a nice "flip the player upside-down" bug if you re-parent it.

It would be excellent if a proper bug-fix for IsFinite made its way into 5.3.2, as there's no telling what other issues 5.4.0 will include. (Every release in the past 12 months has seemed to fix one thing and introduce a new breakage somewhere else!)

 

I'm assuming the "p" in the patches means it's for the Pro version or does it mean "patch"? I'm awaiting a fix on the personal version for the AABB dump. Seems a member above was able to apply it to the free version.

 

Thanks. The patch fixed the problem for my project too!

 

I can happily confirm that in 5.3.2p2 my problems seem to be solved

 

I have the same problem! In the Tank tutorial.Do you fixed it?

 

I have the same problem

 

Good news. i will download 5.3.2p1.
thanks share this information.

 

This issue is resolved with version 5.3.2f1

 

I was still having troubles with 5.3.2p1 with the AABB spam.

Weirdly, I recreated the troublesome particle systems from scratch, and NO errors have been popping up. I have no idea why that'd be the case since it's identical to the original prefab, but I'm not complaining. Many thanks for the fixes.

 

This is NOT fixed in 5.3.2f1, and neither in 5.3.2p1.

 

same errors going if we using mirror from wiki http://wiki.unity3d.com/index.php/MirrorReflection3
if camera see that mirror and paticles, then errors appear.

 

Have you tried 5.3.2 PATCH 4?

 

i didnt. will test it in time, but i doubt that problem gone.