GCICAP & sloppy AI pilots question

[Stonehouse]

I haven't been able to figure out why the CAP groups head off for the horizon yet but while working on it I have found that it seems the AI pilots hit the bar before flying. I've retrieved the waypoints being generated and via cut and paste put them into a dummy mission and checked that they are all within the CAP zone and watched a plane fly them perfectly. I have also double checked that the zone radius is being reported correctly and changed the waypoints from turning points to fly over points and this last has improved things but...they still end up flying to the border of the zone even though the waypoints are within 50% of the radius from the center of the zone. eg

 

 

 

local _WPz = actualCAPzoneposz + math.random(actualCAPzone.radius * -0.5, actualCAPzone.radius*0.5)

local _WPx = actualCAPzoneposx + math.random(actualCAPzone.radius * -0.5, actualCAPzone.radius*0.5)

 

 

 

and

 

 

CAPPatrolpointstable =

{

["alt"] = CAPalt + land.getHeight{x = _WPx, y = _WPz},

["type"] = "Turning Point",

["action"] = "Fly Over Point",

["alt_type"] = "BARO",

["formation_template"] = "",

["properties"] =

{

["vnav"] = 1,

["scale"] = 0,

["angle"] = 0,

["vangle"] = 0,

["steer"] = 2,

}, -- end of ["properties"]

["ETA"] = 230.54689194991,

["y"] = _WPz,

["x"] = _WPx,

["speed"] = Patrolspeed,

["ETA_locked"] = false,

["task"] =

{

["id"] = "ComboTask",

["params"] =

{

["tasks"] =

{

}, -- end of ["tasks"]

}, -- end of ["params"]

}, -- end of ["task"]

["speed_locked"] = true,

}

 

 

 

Is it just that a 50km radius zone is too small for the Ai in a Mig15 and they can't turn fast enough to follow the route? But then why did the plane in the cut and paste mission fly the points exactly?

 

Other than that they seem to stay roughly within the zone but it is weird that they are so sloppy.

 

Any suggestions to get them to sober up?

[Pikey]

This happens with infantry units that are spawned under certain conditions. I'm just off to work but I think its both searchable and a ME "thing". Maybe its a timing issue.