diff options
| author | Sheikh Dawood Abdul Ajees <[email protected]> | 2018-12-02 13:31:57 -0600 |
|---|---|---|
| committer | Sheikh Dawood Abdul Ajees <[email protected]> | 2018-12-02 13:31:57 -0600 |
| commit | 326e24039dd3f063afd211fad770e15bdd5ff4ea (patch) | |
| tree | 94c7bcc15191736f263739c107d0a253b1629b0a /PhysX_3.4/Documentation/PhysXGuide/Manual/Particles.html | |
| parent | PhysX 3.4, APEX 1.4 patch release @25256367 (diff) | |
| download | physx-3.4-326e24039dd3f063afd211fad770e15bdd5ff4ea.tar.xz physx-3.4-326e24039dd3f063afd211fad770e15bdd5ff4ea.zip | |
PhysX 3.4, APEX 1.4 patch release @25354359v3.4.2-bsd
Diffstat (limited to 'PhysX_3.4/Documentation/PhysXGuide/Manual/Particles.html')
| -rw-r--r-- | PhysX_3.4/Documentation/PhysXGuide/Manual/Particles.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/PhysX_3.4/Documentation/PhysXGuide/Manual/Particles.html b/PhysX_3.4/Documentation/PhysXGuide/Manual/Particles.html index 893a1a8b..2bb529a3 100644 --- a/PhysX_3.4/Documentation/PhysXGuide/Manual/Particles.html +++ b/PhysX_3.4/Documentation/PhysXGuide/Manual/Particles.html @@ -87,7 +87,7 @@ and can be added to a scene.</p> </div> <div class="section" id="particle-management"> <h2>Particle Management<a class="headerlink" href="#particle-management" title="Permalink to this headline">ΒΆ</a></h2> -<p>Particle systems reserve memory for a fixed number of particles - <em>PxParticleBase::getMaxParticles</em>. Each of these particles can be addressed with a fixed index throughout it's lifetime. The given range of indices is [0, <em>PxParticleBase::getMaxParticles</em>]. In order to support a dynamic amount of particles, particles are marked as being valid or invalid. This is achieved by two means: The valid particle range indicates the range within which particles may be valid. Outside that range all particles are defined as being invalid. Within that range valid particles are marked with the flag <em>PxParticleFlag::eVALID</em>. Alternatively PhysX provides a bitmap with each bit set corresponding to a valid particle within the valid particle range. The bitmap consists of an array of 32-bit unsigned integers with enough elements to cover the valid particle range.</p> +<p>Particle systems reserve memory for a fixed number of particles - <em>PxParticleBase::getMaxParticles</em>. Each of these particles can be addressed with a fixed index throughout its lifetime. The given range of indices is [0, <em>PxParticleBase::getMaxParticles</em>]. In order to support a dynamic amount of particles, particles are marked as being valid or invalid. This is achieved by two means: The valid particle range indicates the range within which particles may be valid. Outside that range all particles are defined as being invalid. Within that range valid particles are marked with the flag <em>PxParticleFlag::eVALID</em>. Alternatively PhysX provides a bitmap with each bit set corresponding to a valid particle within the valid particle range. The bitmap consists of an array of 32-bit unsigned integers with enough elements to cover the valid particle range.</p> <div class="figure align-center"> <a class="reference internal image-reference" href="../_images/ParticleValidScheme.png"><img alt="../_images/ParticleValidScheme.png" src="../_images/ParticleValidScheme.png" /></a> <p class="caption">Figure 2: Scheme showing how valid particles are tracked</p> |