Switch PROJECTILE
to use PagedEntityContainer<PROJECTILE>
as backing storage
#3675
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The game still uses
psProjectileList
to maintain stable and predictable order of iteration for projectiles, but the individualPROJECTILE
instances are allocated from the globalPagedEntityContainer<PROJECTILE>
instance.Optimize
proj_UpdateAll()
by removing additional checks inside the tight loop, which enumerates all projectiles currently in play, thus considerably speeding up this frequent and expensive operation.Brief summary for the performance impact of this PR: on my machine this PR yields ~5-10 FPS improvement in stress-test conditions (e.g. horde of units with Seraph weapons, simultaneously firing lots of projectiles in one direction).
Signed-off-by: Pavel Solodovnikov [email protected]