Change Details

Please provide the following when creating the Ticket: **Game Version number: ** 1.4.0.29 **Modded?:** No If modded, please list the mods: **Issue Description: ** Check source of `SCR_AmbientPatrolSystem::UpdateCheckInterval`. The tickrate increases the more patrol spawns there are to process every spawn over 3sec and each tick on an inactive spawner does a distance check for each connected player. Vanilla Everon Conflict has 355 ambient patrol spawners, that's a 0.0084s tickrate for the system with up to 15,146 distance checks being performed per second in a worst-case scenario on a 128 player server w/ no patrols spawned yet. The tickrate for this system should really be set to a configurable (via WB so map/scenario devs can find what suits their world best) int that results in reasonable AI spawn rates w/o run-away performance issues on maps with lots of spawns.

**Game Version number: ** 1.4.0.29 **Modded?:** No If modded, please list the mods: **Issue Description: ** Check source of `SCR_AmbientPatrolSystem::UpdateCheckInterval`. The tickrate increases the more patrol spawns there are to process every spawn over 3sec and each tick on an inactive spawner does a distance check for each connected player. Vanilla Everon Conflict has 355 ambient patrol spawners, that's a 0.0084s tickrate for the system with up to 15,146 distance checks being performed per second in a worst-case scenario on a 128 player server w/ no patrols spawned yet. The tickrate for this system should really be set to a configurable (via WB so map/scenario devs can find what suits their world best) int that results in reasonable AI spawn rates w/o run-away performance issues on maps with lots of spawns.

Please provide the following when creating the Ticket: **Game Version number: ** 1.4.0.29 **Modded?:** No If modded, please list the mods: **Issue Description: ** Check source of `SCR_AmbientPatrolSystem::UpdateCheckInterval`. The tickrate increases the more patrol spawns there are to process every spawn over 3sec and each tick on an inactive spawner does a distance check for each connected player. Vanilla Everon Conflict has 355 ambient patrol spawners, that's a 0.0084s tickrate for the system with up to 15,146 distance checks being performed per second in a worst-case scenario on a 128 player server w/ no patrols spawned yet. The tickrate for this system should really be set to a configurable (via WB so map/scenario devs can find what suits their world best) int that results in reasonable AI spawn rates w/o run-away performance issues on maps with lots of spawns.