Closed eric963 closed 6 years ago
Need help to check all these, sorry, no chance anyone will likely do it unless it's handed on a plate, if you know what I mean.
Ok, retested this with both release and dev version.
This was using DETECTION_AREAS
Both release and dev version works correctly only if there is only just the SEAD unit in the detection area or the SEAD unit and one other unit.
If the detection area contains more then 2 units, once the sead unit is destroyed a CAS task for the remaining units is never generated.
detectiontgts3.zip dcs.log file dcs.zip
ok. will check in 2.4.
@eric963 ok, checking this at the moment ...
@eric963 so, the split of tasking in a task "planned" state is still working. So a SEAD task with other vehicles is split into a SEAD and a CAS task when the units move out of areas radius. So that is still working, which is good.
@eric963 Now here's the discussion that we need to have. I had intended ONLY to split tasks when these tasks were "planned". Not when "assigned"! In assigned mode, the player will have to execute the task, that is, destroy all units in the task scope. So let me test now the SEAD scope. Because when all units in scope are destroyed, then the task should become complete and indeed, then a CAS task should be created for the remaining units. So, i am testing this now ...
@eric963 So, this is fixed ... a new CAS task is generated after the SEAD targets have been destroyed and the SEAD task is flagged as completed. See the attached picture.
Please test again, i will close this issue and will flag this as tested.
FAC detects a group of ground units containing a SAM and 2 tanks. Task SEAD.001 mission gets created. Join the task and destroy the SAM unit. Get he message Task SEAD.001 is successful. Good Job!
After that no task is generated for the remaining 2 tanks. Attached is my simple test mission. Does this in SP, Client hosted and dedicated.
A2GSispatcherseadgroup.zip