Harpoon Out-of-Zone Conditions

[AvroLanc]

While clearly WIP, I've been having fun with the Harpoon. I've been surprised to discover that the 9 or so Out of Zone Conditions have been modeled pretty well already.

 

These are the cues you get in the HUD and Stores DDI to advise of problems with launch parameters / geometry. They are not detailed at all in the early access guide. Nor did Wags mention them. Some might find this useful:

 

ALT - Aircraft altitude is less than the recommended absolute minimum launch altitude. This is 2500 ft AGL.

OFF AXIS - The bearing to the target, search area, or Harpoon turnpoint is greater than 90°.

HPTP ANG - The total turn angle at the Harpoon turnpoint is too large.

A/C HPTP - The aircraft is too close to the Harpoon turnpoint.

TGT/HPTP - The Harpoon turnpoint is too close to the search area/target.

SCH/DSTR - The distance between the entered search and destruct range is too small (BOL mode only).

DSTR RNG - The destruct range is greater than Rmax (BOL mode only).

INV TGT - The total distance to the target is greater than 172 nm, which is invalid (R/BL Mode only).

INV SRCH - The total search range is greater than 105 nm which is invalid (BOL Mode only).

 

They seem to indicate as intended. However I've not been able to generate a INV SRCH caution yet. Seems to be not working.

 

What is the max range of the AGM-84D as modeled in DCS?

Also, I'm pretty sure a pickle hold of a few seconds in needed, rather than the instant release we have at the moment. (The same applies to JDAMs, but again not correct yet).

[AvroLanc]

Only partially wish list... I was actually being complementary, most of the above seems to be in.

[blunt_waco]

While clearly WIP, I've been having fun with the Harpoon. I've been surprised to discover that the 9 or so Out of Zone Conditions have been modeled pretty well already.

 

These are the cues you get in the HUD and Stores DDI to advise of problems with launch parameters / geometry. They are not detailed at all in the early access guide. Nor did Wags mention them. Some might find this useful:

 

ALT - Aircraft altitude is less than the recommended absolute minimum launch altitude. This is 2500 ft AGL.

OFF AXIS - The bearing to the target, search area, or Harpoon turnpoint is greater than 90°.

HPTP ANG - The total turn angle at the Harpoon turnpoint is too large.

A/C HPTP - The aircraft is too close to the Harpoon turnpoint.

TGT/HPTP - The Harpoon turnpoint is too close to the search area/target.

SCH/DSTR - The distance between the entered search and destruct range is too small (BOL mode only).

DSTR RNG - The destruct range is greater than Rmax (BOL mode only).

INV TGT - The total distance to the target is greater than 172 nm, which is invalid (R/BL Mode only).

INV SRCH - The total search range is greater than 105 nm which is invalid (BOL Mode only).

 

They seem to indicate as intended. However I've not been able to generate a INV SRCH caution yet. Seems to be not working.

 

What is the max range of the AGM-84D as modeled in DCS?

Also, I'm pretty sure a pickle hold of a few seconds in needed, rather than the instant release we have at the moment. (The same applies to JDAMs, but again not correct yet).

 

 

I did, thank you very much. There is no chance I could have figured out why I was getting TGT if it wasn't for your post.

God bless you.

[blunt_waco]

By the way, I don't think it works anymore. I don't know if you have chance to try it but after I set a waypoint and the Harpoon UFC parameters. Once fired, the harpoon will follow the BRG even though the HSI shows the harpoon traveling to WP1 then steer toward BRG and search for targets!!

[Harker]

By the way, I don't think it works anymore. I don't know if you have chance to try it but after I set a waypoint and the Harpoon UFC parameters. Once fired, the harpoon will follow the BRG even though the HSI shows the harpoon traveling to WP1 then steer toward BRG and search for targets!!

HPTP isn't working right now, it's a reported bug.

[blunt_waco]

HPTP isn't working right now, it's a reported bug.

 

 

Thank you.