Observed behavior:
When a player gets within a set distance of an enemy CAP flight, the CAP flight will commit and target the player. This commit/targeting range seems to be about 30NM, with very little variation, causing enemy CAP flight behavior to be somewhat predictable. Furthermore, for WW2 aircraft and 3rd gen aircraft it would be preferable to have commit/targeting ranges set closer to WVR.
Desired behavior:
As a mission creator I want to be able to adjust the commit/targeting range, allowing for more control over the enemy CAP response. I would also like for the commit/targeting range Rcommit to be randomly picked by the enemy CAP between a minimum Rmin and maximum Rmax range, such that the predictability of the enemy CAP flight behavior can be minimized. It would be acceptable for each enemy flight to choose their Rcommit range upon spawning, such that this range does not need to be updated mid-flight.
**Affected version:**
0.12.0 and earlier
**Observed behavior:**
When a player gets within a set distance of an enemy CAP flight, the CAP flight will commit and target the player. This commit/targeting range seems to be about 30NM, with very little variation, causing enemy CAP flight behavior to be somewhat predictable. Furthermore, for WW2 aircraft and 3rd gen aircraft it would be preferable to have commit/targeting ranges set closer to WVR.
**Desired behavior:**
As a mission creator I want to be able to adjust the commit/targeting range, allowing for more control over the enemy CAP response. I would also like for the commit/targeting range Rcommit to be randomly picked by the enemy CAP between a minimum Rmin and maximum Rmax range, such that the predictability of the enemy CAP flight behavior can be minimized. It would be acceptable for each enemy flight to choose their Rcommit range upon spawning, such that this range does not need to be updated mid-flight.
While Spearhead doesn't manage the targeting range directly.
It does pass the targeting range in the given CAP Tasking.
DCS then manages the targeting itself, but based on the range and other configuration Spearhead added into the task.
This is still relevant.
While Spearhead doesn't manage the targeting range directly.
It does pass the targeting range in the given CAP Tasking.
DCS then manages the targeting itself, but based on the range and other configuration Spearhead added into the task.
However, the issue may remain open in order to address different flights/types having different config as this is currently not built in
Addressed in #29
However, the issue may remain open in order to address different flights/types having different config as this is currently not built in
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Affected version:
0.12.0 and earlier
Observed behavior:
When a player gets within a set distance of an enemy CAP flight, the CAP flight will commit and target the player. This commit/targeting range seems to be about 30NM, with very little variation, causing enemy CAP flight behavior to be somewhat predictable. Furthermore, for WW2 aircraft and 3rd gen aircraft it would be preferable to have commit/targeting ranges set closer to WVR.
Desired behavior:
As a mission creator I want to be able to adjust the commit/targeting range, allowing for more control over the enemy CAP response. I would also like for the commit/targeting range Rcommit to be randomly picked by the enemy CAP between a minimum Rmin and maximum Rmax range, such that the predictability of the enemy CAP flight behavior can be minimized. It would be acceptable for each enemy flight to choose their Rcommit range upon spawning, such that this range does not need to be updated mid-flight.
@dutchie031 clarified that Spearhead CAP flights use the DCS targeting rather than a dedicated Spearhead targeting. Disregard the above.
This is still relevant.
While Spearhead doesn't manage the targeting range directly.
It does pass the targeting range in the given CAP Tasking.
DCS then manages the targeting itself, but based on the range and other configuration Spearhead added into the task.
Addressed in #29
However, the issue may remain open in order to address different flights/types having different config as this is currently not built in