Feature #11086

Make it possible to have a weapon able to lock air units only.

Added by Myke over 5 years ago. Updated almost 4 years ago.

Status:Assigned Start date:06/08/2010
Priority:Normal Due date:
Assignee:- % Done:


Target version:-
Affected ArmA II version: First affected ArmA II version:
Reproduced by another DH user:No Single / Multi Player?:
I am using some Mods:No BIForumURL:
I am using: NGUrl:
Reproducible for you:No WIKIurl:
Related to content of DLC:


This problems relate to all air-to-ground weapon systems that can lock targets.

To determine what kind of target can be locked, there are 3 config settings which can be switched:
  • laserLock
  • airLock
  • irLock

While laserLock and airLock successfully switches those lock-capabilities on and off, irLock doesn't.

It remains active no matter what is it set to, resulting that air-to-air missiles, like AIM-9 and R-73,
always can lock on ground targets.

When i set irLock = 0, then the weapon shouldn't be able to lock on ground targets.

  1. Open up editor.
  2. Place yourself as pilot of a SU-34 or a AV-8B flying.
  3. Also place some enemy manned vehicles.
  4. Switch to AA weapons (R-73 or AIM-9) and lock onto ground targets.

Related issues

related to ARMA2 Community Issue Tracker - Feature #5750: more realistic fire control for missiles Assigned 11/08/2009
related to ARMA2 Community Issue Tracker - Bug #7578: Aircraft AI should not use AA missiles for ground attacks Feedback 12/31/2009
related to ARMA2 Community Issue Tracker - Feature #8890: Vikhr Missiles CfgAmmo should be changed to make the Vikh... Assigned 02/07/2010
related to ARMA2 Community Issue Tracker - Bug #37331: Radar targets and locking should to be limited by object ... Assigned 07/17/2012
related to ARMA2 Community Issue Tracker - Bug #46368: irScanGround = 0/false does not limit radar/target identi... Assigned 09/09/2012
related to ARMA2 Community Issue Tracker - Bug #15980: Airplanes survive too many AA missile hits Assigned 12/16/2010


Updated by kju over 5 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from Config entry "irLock" non-functional. to Make it possible to have a weapon able to lock air units only.
  • Status changed from New to Assigned
  • Priority changed from High to Normal

While I fully agree, this is more like a feature request.

irLock is needed (irLock = 1;) from what I recall to have
airLock and even laserLock to work at all.
So it is somewhat a design issue, rather than a bug.

Updated by Myke over 5 years ago

With all due respect, for my opinion this isn't a feature request. Might be that the engine needs it that way right now, but if i see a configentry named "irLock" and i set it to 0 (false), i expect that the weapon can't lock ground targets anymore. Else irLock would be meaningless, even more as the config entry "canLock" already deals the general lock capabilities.

I would call it a feature request if i would have asked to introduce more lock classes, like shipLock or radarLock (lock only radar emitting sources) which isn't the case (yet).

It is called irLock, it is meant to switch off lock on ground target which it doesn't, therefor it is a bug.

OT: thanks for formatting my OP, much appreciated. And i hope you don't get offended, just stating my position, mate.

Updated by kju over 5 years ago

it is meant to switch off lock on ground target

The point is, it does not matter what we think. BI decides.
We may like that or not. As per discussion this probably would have be rejected as
"intended behavior" (in the view from BI design POV).

So instead we settled to make these kinds of disagreements as features requests instead.
This allows the community to vote the issue at hand and therefore show its interest to
get this addressed.

You can see it also this way:
Currently there is no way to make air lock only. So it would be an addition, aka feature.
Or the type (bug vs feature) does not matter much anyway. It is the type of issue (CTD, FPS,
stability etc vs other requests) and the votes that matter (most).

Updated by Myke over 5 years ago

Thanks for the explanation. Although i'm not fully happy with how it has to handled (IMHO a bug is a bug is a bug) but at least now i see why it has to be handled that way. And if i'm happy with or not is not the matter.

I just hope BIS will "add this feature" (fix this bug) in one of the upcoming patches...the sooner the better.

Thx again, kju.

Updated by kju over 5 years ago

As info. It seems irLock = 1; is required to make AI use weapons only vs vehicles (and not vs infantry).

Updated by kju over 5 years ago

  • Affected ArmA II version changed from 1.06 BETA to Please select...
  • Audio card set to Please specify!
  • Size of OS swap file set to Please specify!

Updated by kju over 4 years ago

  • Operating system deleted (Vista 64 bit)
  • Graphics card deleted (HD5870)
  • Affected ArmA II version deleted (Please select...)
  • CPU deleted (AMD Phenom II X4 965)
  • Mainboard chipset deleted (790X)
  • Audio card deleted (Please specify!)
  • Size of OS swap file deleted (Please specify!)

Updated by kotov over 4 years ago

somewhere on youtube video where stinger hit ground vehicle - imho no issues in game or broken game-play.

Updated by Myke over 4 years ago

Aye, youtube is a excellent knowledge base. :rolleyes:
Anyway, one wouldn't exclude the other:
canLockAir = true;
canLockGround = true;

Problem solved.

Finally i would like to expand this "feature request" to more diversity in defining lock abilities:
canLockShip //to make a difference between Groundvehicles and vessels
canLockRadar //to realistically have a base for a AGM-88 HARM missile, of course the radar should be able to be switched off by it's crew. No emmissions but also no radar info.

Updated by 77 over 4 years ago

Voted yes but mean NO.

The heat of an engine is the heat of an engine.... it matters what engine?

Just because its primarily designed to strike from air to air... it can (if you choose) be use ineffectively on ground units.

Far more important issues to deal with first than nit-picky target/weapon selection.

Updated by Myke over 4 years ago

As said in the BI Forum thread: put your hands on a running car engine, then in the backblast of a jet engine and feel the difference.

And from my very own point of view this IS a important issue. But i don't say "it has to be done asap" although i would like to say that. I know there are other issues that weights more than this but anyway, i would like to see this feature and if it is possible, please BIS, do it.

Updated by BigDawgKS over 4 years ago

Just having the functionality available for addons would open up many possibilities. Typically, more configuration options is always good.

Updated by Suma about 4 years ago

Instead of a discussion, what I would prefer is a simple repro situation which would show AI depleting its AA missiles on a ground target. Such behaviour can be considered a bug and perhaps could be fixed. I suggest creating such issue (if it does not exist yet) and gathering enough votes for it.

Updated by kju about 4 years ago

Fair point.

This ticket is mostly about human actions I'd say.

Updated by Myke about 4 years ago

Disregard everything. Please change the ticket to the following:

Update the BIWIKI
here http://community.bistudio.com/wiki/CfgAmmo_Config_Reference#airLock
here http://community.bistudio.com/wiki/CfgAmmo_Config_Reference#irLock
and here: http://community.bistudio.com/wiki/CfgAmmo_Config_Reference#laserLock

Obviously those definitions seems to be utterly wrong. So please explain what those config settings are really supposed to do.

Updated by kju about 4 years ago

The BIKI descriptions are correct.

Description: Declares if ammo can lock on air targets.

You want airLock to be air lock ONLY.
This is not what the BIKI says nor how it currently works.

I agree though it should be air lock only. This is what this ticket is for.

Updated by Myke about 4 years ago

I want to be able to control what the missiles i've created can lock on and what not, not more but not less either. It could be that simple:
canLockAir = true/false;
canLockGround = true/false;
canLockShip = true/false;
canLockRadarEmmissions = true/false;

The whole targetting aspect of missiles is broken by design.

Updated by kju about 4 years ago

Suma we have a good ticket for your request: #7578

Aircraft AI should not use AA missiles for ground attacks

Updated by Fireball almost 4 years ago

This feature is more to prevent issues like described in #25767.

Also available in: Atom PDF