Switch PROJECTILE to use PagedEntityContainer<PROJECTILE> as back…

…ing storage

The game still uses `psProjectileList` to maintain stable and
predictable order of iteration for projectiles, but the
individual `PROJECTILE` instances are allocated from the
global `PagedEntityContainer<PROJECTILE>` instance.

`proj_SendProjectileAngled()` now doesn't automatically
add the spawned penetrating projectile to `psProjectileList`,
which is a little step back in terms of ease of use (need
to additional code so that spawned projectiles are added
to the `psProjectileList` manually in relevant cases).

But it allows to remove additional checks inside the
tight loop in `proj_UpdateAll()`, which enumerates all
projectiles currently in play, thus considerably speeding
up this frequent and expensive operation.

Signed-off-by: Pavel Solodovnikov <[email protected]>

src/combat.cpp

@@ -319,7 +319,8 @@ bool combFire(WEAPON *psWeap, BASE_OBJECT *psAttacker, BASE_OBJECT *psTarget, in
 	CLIP(predict.x, 0, world_coord(mapWidth - 1));
 	CLIP(predict.y, 0, world_coord(mapHeight - 1));
 
-	proj_SendProjectileAngled(psWeap, psAttacker, psAttacker->player, predict, psTarget, bVisibleAnyway, weapon_slot, min_angle, fireTime);
+	auto* psProj = proj_SendProjectileAngled(psWeap, psAttacker, psAttacker->player, predict, psTarget, bVisibleAnyway, weapon_slot, min_angle, fireTime);
+	proj_AddActiveProjectile(psProj);
 	return true;
 }
 

src/multistruct.cpp

@@ -243,7 +243,9 @@ bool recvLasSat(NETQUEUE queue)
 		}
 
 		// Give enemy no quarter, unleash the lasat
-		proj_SendProjectile(&psStruct->asWeaps[0], nullptr, player, psObj->pos, psObj, true, 0);
+		auto* psProj = proj_SendProjectile(&psStruct->asWeaps[0], nullptr, player, psObj->pos, psObj, true, 0);
+		proj_AddActiveProjectile(psProj);
+
 		psStruct->asWeaps[0].lastFired = gameTime;
 		psStruct->asWeaps[0].ammo = 1; // abducting this field for keeping track of triggers