Fix Bugs around Particle System in Release/2.10.0

[WUCJ638]

Summary

This PR fixes several particle system bugs in Axmol 2.10.0, specifically related to:

• SpawnFadeIn / SpawnScaleIn:

  • Memory not reallocated after setTotalParticles(), causing null pointer crashes.
  • New values ignored after initial allocation.
  • Particles become invisible if _spawnFadeIn or _spawnScaleIn is set to 0.0f.

• Loop Animation crash:

  • After setTotalParticles(), _particleCount wasn’t set to 0, leading to invalid access in _animations.at(_particleData.animIndex[i]).

Changes

• Reallocate attribute memory (fade/scale/HSV) in ParticleSystemQuad::setTotalParticles() if enabled.
• Allow updating spawn fade/scale values even after allocation.
• Skip fade/scale logic when value is 0.0f to avoid invisible particles.
• Reset _particleCount = 0 in setTotalParticles() and resetSystem() to prevent stale animation indices.

Testing

• Verified on Windows 10 with Visual Studio 2026 (MSVC 19.50).

• ParticleTest from 42 to 55 pass without crash; emission shape unaffected, by simply adding

      this->runAction(Sequence::create(
          DelayTime::create(3.0f),
          CallFunc::create([this](){
              _emitter->setTotalParticles(2000);
              }),
          nullptr
      ));

  at the end of onEnter()

• HSV & advanced animations not fully tested (because I haven't used them in my projects).

Note:

1. Huge comments (//// BUG from WUCJ638... //) are removed to reduce space.
2. Since I'm a student who is occupied with heavy academic tasks and preparing for final exam, delayed response may be unavoidable. Thanks for your understanding!

[j-jorge]

(I'm not a maintainer)

Note: Huge comments (//// BUG from WUCJ638... //) can be removed, since they occupy a lot of space.

I believe you should remove them indeed. Explanations for the bug and the fix are welcome in a commit message, comments about the current code's behavior are great in the code. And no need for so may slashes :)

[WUCJ638]

I believe you should remove them indeed. Explanations for the bug and the fix are welcome in a commit message, comments about the current code's behavior are great in the code. And no need for so may slashes :)

Got it, I'll erase them away later on because now it's time for me to go to bed. 🛏