Assertion failed on expression: 'ps->array_size()' is still reproduced at v4.7.0

[LenbaSun]

NOTE: Your issue may already be reported! Please search on the issue tracker before creating one.

Describe the bug

This bug still exits at v4.7.0
#278 (comment)

To Reproduce

Same steps this person mentioned
#278 (comment)

Expected behavior
No assertion

Environment (please complete the following information):

• Version 4.7.0
• Platform: Editor(Windows/Mac), Standalone(Windows/Mac)
• Unity version: 2022.3.56f1
• Build options: Not built

[mob-sakai]

Thank you for your reporting!
Could you please attach a minimal project (included Assets, Packages and ProjectSettings directories) that reproduces the issue?
Of course, you don't need to include any secret assets from your project. Feel free to use free assets instead.

[mob-sakai]

@mitay-walle said in the issue:

I've done more tests and find out that in my case reason was in Noise module + prewarm.
No specific parameters, but module enabling itself.
only disabling noise or prewarm helps.

Do this advice help you?

[LenbaSun]

Thanks for your reply.
Here is the minimal project prj_ui_particle_report.zip ,

reproduce by the following steps:

1. Open Assets/Scenes/SampleScene.unity.
2. Press play button to enter play mode.
3. Press play button to exit play mode.
4. Show assertion error messages on the console.

• Play mode screenshot
  

• Console messages screenshot
  

[mob-sakai]

Thank you!

[LenbaSun]

@mitay-walle said in the issue:

I've done more tests and find out that in my case reason was in Noise module + prewarm.
No specific parameters, but module enabling itself.
only disabling noise or prewarm helps.

Do this advice help you?

Yes, disabling either prewarm or the noise module will stop the assertion from happening. But prewarm is a really common feature, and it's hard for me to tell artists not to use it.

In my current project, a lot of particle systems have already been created, and we need to upgrade the UI particle plugin to fix some issues.

If we disable prewarm, that would mean going back to review the visual output of every single particle system and tweaking them again—which is extremely difficult and pretty much not an option.

[mob-sakai]

Umm, the issue is not reproduced on my environment...

Here is the minimal project prj_ui_particle_report.zip ,

• 2022.3.56f1 (Apple sillicon/Windows)
• Editor(Mac/Windows), Standalone(Mac/Windows)
• Mac OSX 14.7.5 M1 Max/Windows 11

[LenbaSun]

Umm, the issue is not reproduced on my environment...

Here is the minimal project prj_ui_particle_report.zip ,

• 2022.3.56f1 (Apple sillicon/Windows)
• Editor(Mac/Windows), Standalone(Mac/Windows)
• Mac OSX 14.7.5 M1 Max/Windows 11

That sounds frustrating.............T_T

[mob-sakai]

By the way, if you update UIParticle to the latest version (v4.11.2) in your environment, does this issue get resolved?

[LenbaSun]

By the way, if you update UIParticle to the latest version (v4.11.2) in your environment, does this issue get resolved?

The good news is that this issue does not occur in version 4.11.2.
However, after upgrading to 4.11.2, another issue appears — the size of the particles changes.
The attached images and mini-sample projects show a comparison between the two.

4.11.2 snapshot & mini-project

prj_ui_particle_report_scale_v4_11_2.zip

4.7.0 snapshot & mini-project

prj_ui_particle_report_scale_v4_7_0.zip

Steps to reproduce in the sample project:

1. Open Assets/Scenes/SampleScene.unity.
2. You can directly see the size difference between the two in Editor mode, or enter Play mode by pressing Play — the size difference is visible in both modes.