Confirmation on AA locking distance?

[dtacs]

To my knowledge the maximum range of all anti-air locking distance was between 900m and 1000m. This meant that on maps such as Muttrah and Kashan, CAS crews could stay at a significant altitude without having to worry about Gopher's, Patriot's, stationary AA, MANPADS and so forth.

However, according to this image on Wicca's Karez Offensive the locking distance is over 1 kilometer.



Is this something that is solely confined to Karez or is this a change that has been totally unmentioned in the .97 changelog as with so many other gameplay edits? I'd appreciate it if someone could find this out in-game.

[LieutenantNessie]

To my knowledge the maximum range of all anti-air locking distance was between 900m and 1000m. This meant that on maps such as Muttrah and Kashan, CAS crews could stay at a significant altitude without having to worry about Gopher's, Patriot's, stationary AA, MANPADS and so forth.

However, according to this image on Wicca's Karez Offensive the locking distance is over 1 kilometer.



Is this something that is solely confined to Karez or is this a change that has been totally unmentioned in the .97 changelog as with so many other gameplay edits? I'd appreciate it if someone could find this out in-game.

I've heard it's 1,3k from multiple sources

[Bufl4x]

Last time i was using an Anti Air Vehicle on Kashan or Iron Eagle, the target box would appear at 1300 and i could lock on to targets at 1200.
I think it also happened on Burning Sands and Black Gold too.

It only applies to AA vehicles though, stationary AA emplacements and handheld AA has a shorter range.

[Psyrus]

I'm not sure if it's correct but it seems like the missile being fired determines the max lock range. The values can be found in the tweak files in
\EA GAMES\Battlefield 2\mods\pr_edit\objects\weapons\Armament\missiles\

For example

ObjectTemplate.seek.targetType TTHeat
ObjectTemplate.seek.trackingDelay 0.02
ObjectTemplate.seek.maxAngleLock 30
ObjectTemplate.seek.maxDistLock 700
ObjectTemplate.seek.directionBonus 0.2
ObjectTemplate.seek.reLockTime 30

ObjectTemplate.seek.targetType TTHeat
ObjectTemplate.seek.trackingDelay 0.02
ObjectTemplate.seek.maxAngleLock 30
ObjectTemplate.seek.maxDistLock 850
ObjectTemplate.seek.directionBonus 0.8
ObjectTemplate.seek.reLockTime 30

ObjectTemplate.seek.targetType TTHeat
ObjectTemplate.seek.trackingDelay 0.02
ObjectTemplate.seek.maxAngleLock 30
ObjectTemplate.seek.maxDistLock 1300
ObjectTemplate.seek.directionBonus 0.25
ObjectTemplate.seek.reLockTime 30

The above is *assuming* I'm correct that the values match what you're looking for

[MaSSive]

And Igla is used in opfor manpads. 1300 meters. Heh theres the answer.

[saXoni]

And Igla is used in opfor stationary AA. 1300 meters. Heh theres the answer.

Fixed it for you.

[MaSSive]

Sax those are all manpads. It can be dismounted and moved so its quite portable air defense system.

[saXoni]

In PR it's a stationary AA. The Opfor teams are using Strela as manpad.

[MaSSive]

Yes that is correct. Back to topic, did anyone knew this? I never thought of opening game files to look for these things, and Im going to be quite more careful when playing against opfor teams. IF I knew this earlier it would save my arse quite a lot times tbh.

[saXoni]

I knew it. However, I have always thought that every MANPADS' range was 700, which is apparently not true, as the Stinger's range is 850.

[Rhino]

with most weapons, the HUD locking distance is normally equal to the map's view distance, as the way BF2 works is that you can not see a heat sig (nor can a missile) that is beyond its view distance. In some cases its shorter than the view distance of a map, mainly if a map has a very, very large VD but sometimes the HUD has a longer locking distance than the missile itself, and the missile needs to fly closer to the target before it actually manages to lock onto it.

[xambone]

So if I can fire from 1500-1375m I am safe from Harm of All AA and Stationary AA ?
Does this mean Horizontal 1300 is the max also?

[jerkzilla]

with most weapons, the HUD locking distance is normally equal to the map's view distance, as the way BF2 works is that you can not see a heat sig (nor can a missile) that is beyond its view distance. In some cases its shorter than the view distance of a map, mainly if a map has a very, very large VD but sometimes the HUD has a longer locking distance than the missile itself, and the missile needs to fly closer to the target before it actually manages to lock onto it.

Well that seems pretty sensible, but what exactly do you mean by "sometimes"?

[Rhino]

Well that seems pretty sensible, but what exactly do you mean by "sometimes"?

Depending on the weapon.

Also I should mention if we could have AA locking distance not limited to the map's view distance, we would but we can't.

[saXoni]

as the way BF2 works is that you can not see a heat sig (nor can a missile) that is beyond its view distance.

On Kashan Desert I can lock on targets with the AAV, where the range is 1300, without seeing the target.

[Psyrus]

On Kashan Desert I can lock on targets with the AAV, where the range is 1300, without seeing the target.

That *might* be due to the following:

GameLogic.MaximumLevelViewDistance 1000

Renderer.fogStartEndAndBase 700.00/980.00/1.00/0.50

The fog renders before the VD cuts everything off (to save from very ugly dropoffs). So you'd be locking through the fog, not past the VD.

[saXoni]

It says that the VD is 1000. I can lock beyond the VD.

[Psyrus]

It says that the VD is 1000. I can lock beyond the VD.

Can you confirm that with proof? Or is it just anecdotal?

[saXoni]

Confirm that the VD is 1000, or that I can lock beyond the VD?

[Psyrus]

Confirm that the VD is 1000, or that I can lock beyond the VD?

Well I took those figures from an extracted Kashan 0.937 (pretty sure), so I *know* the VD figure.... I was just wondering if you had anything like Dtacs' first post picture to verify your claim.