collapse_all

expand_all

collapse_allexpand_alldropdowndropdownHovercopycodecopycodeHighlight

collapse_all Collapse AllExpand All     dropdown Code: All Code: Multiple Code: C# Code: Visual Basic Code: Visual C++

[TCheckBoxFormControlObj]C#

[TCheckBoxFormControlObj]Visual Basic

[TCheckBoxFormControlObj]
Visual C++

DPSF API Documentation

AutoMemoryManagerModes Enumeration
gradient
The possible Modes the Automatic Memory Manager can be in

Namespace: DPSF

Assembly: DPSF (in DPSF.dll) Version: 2.5.0.0

collapse_allSyntax

C#

[SerializableAttribute]

public enum AutoMemoryManagerModes

Visual Basic

<SerializableAttribute>

Public Enumeration AutoMemoryManagerModes

Visual C++

[SerializableAttribute]

public enum class AutoMemoryManagerModes

collapse_allMembers


Member name

Value

Description


Disabled

0

Do not use the Automatic Memory Manager. The Number Of Particles Allocated In Memory will not be changed dynamically at run-time. This is the best option if performance is critical, as it can be expensive to allocate and release large chunks of memory at run-time. If using this mode you should be sure that the Number Of Particles Allocated In Memory is large enough to accommodate the particle system, but small enough that it does not waste large amounts of memory.


DisabledWithEarlyRecycling

1

This is the same as Disabled, except that if a particle is trying to be added and there is no more memory available for a new particle, the particle at the end of the ActiveParticleList will be hard-killed and recycled and used for the new particle.

NOTE: If using Disabled mode instead of this mode, if a new particle tries to be added and no more memory is available, the new particle simply will not be added.

NOTE: If trying to add a new particle, but the number of Active Particles has already hit the MaxNumberOfParticlesAllowed, the particle will not be added. This setting only takes effect when trying to add a new particle and we have reached the NumberOfParticlesAllocatedInMemory, but not the MaxNumberOfParticlesAllowed. This means that in order for this setting to be effective, the MaxNumberOfParticlesAllowed must be greater than the NumberOfParticlesAllocatedInMemory.

NOTE: When a particle is hard-killed, no more processing at all is performed on it. For example, if the particle is supposed to trigger some other event to happen when it dies (e.g. by using a NormalizedTimedEvent), that event will not be triggered.

NOTE: Typically the oldest particles are at the end of the ActiveParticleList and the youngest ones are at the front, so the oldest particles (i.e. the ones with the greatest ElapsedTime and a Lifetime greater than zero) will be recycled first.


IncreaseAndDecrease

2

Allow the Automatic Memory Manager to allocate more memory when needed, and reduce it when not needed.


IncreaseOnly

3

Only allow the Automatic Memory Manager to allocate more memory when needed (cannot reduce space).


DecreaseOnly

4

Only allow the Automatic Memory Manager to reduce the amount of memory allocated when it is not needed (cannot increase space).

collapse_allSee Also

DPSF Namespace

footer

Send comments on this topic to

Dan@DansKingdom.com