Jump to content

AMRAAMs consistently miss non-maneuvering targets at long range


Recommended Posts

Posted (edited)

Since 2.9, and the enhancements to the FA-18C and F-16C radar, both aircraft are now able to engage well past 50-60 miles. However, when the Aim-120B and Aim-120C are shot at non-maneuvering targets past 50 miles, they will consistently undershoot the target during the loft, as if they are no longer able to correct their course. I have mostly tested this in the FA-18C using TWS, but I have noticed it in RWS. I have also tested this with the F-15E and F-16C and the missile behavior remains the same. 

Attached is a track replay of this issue, as well as the tacview. 

image.png

Blind Amraam.trk

Tacview-20231114-223326-DCS.zip.acmi

Blind Amraam SE.trk

Edited by bennyboy9800
  • Like 1

Intel i7 9700k CPU

Nvidia GTX 1080Ti

16GB RAM

Samsung 256GB SSD

Thrustmaster T16000m HOTAS

Posted

AIM-120 has a battery life of 100 seconds and in your tacview that battery goes out when the AIM-120s are roughly 12nm to target. (Not even went active, that happens around 9nm)

Rough estimate your amraams still needed 15s or so of battery to hit their target. You need to keep this in mind when launching long range shots because battery life is the limiting factor more than kinetic performance. 
You can hit shots from that range but you need to be higher so missile would have a faster average velocity

  • Like 1
Posted (edited)

Aim120C battery lifetime is 100 seconds.

I have only looked at the Tacview here and there it is over 100 seconds
12nm before the impact, the Aim120 runs out of power

 

EDIT: too slow 😔

Edited by Hobel
Posted
12 hours ago, Hobel said:

Aim120C battery lifetime is 100 seconds.

I have only looked at the Tacview here and there it is over 100 seconds
12nm before the impact, the Aim120 runs out of power

 

EDIT: too slow 😔

 

So this 100 second battery life is a fixed value that won't be changed?  In other words, it is a feature not a bug? 

Intel i7 9700k CPU

Nvidia GTX 1080Ti

16GB RAM

Samsung 256GB SSD

Thrustmaster T16000m HOTAS

Posted (edited)
vor 16 Minuten schrieb bennyboy9800:

So this 100 second battery life is a fixed value that won't be changed?  In other words, it is a feature not a bug? 

It used to be 80 seconds and was then adjusted to 100. maybe the Aim120C 5 has even more but who knows
Now all Missles have a life limit.

Perhaps irl other factors also play a role so that it is not always fixed at 100 seconds so that it fluctuates between ~-+10 seconds.

Edited by Hobel
Posted
22 minutes ago, Hobel said:

It used to be 80 seconds and was then adjusted to 100. maybe the Aim120C 5 has even more but who knows
Now all Missles have a life limit.

Perhaps irl other factors also play a role so that it is not always fixed at 100 seconds so that it fluctuates between ~-+10 seconds.

 

When I adjust the op_time and life values in aim120family.lua it still fails to track past 60 miles. 

Intel i7 9700k CPU

Nvidia GTX 1080Ti

16GB RAM

Samsung 256GB SSD

Thrustmaster T16000m HOTAS

Posted (edited)
vor 5 Minuten schrieb bennyboy9800:

When I adjust the op_time and life values in aim120family.lua it still fails to track past 60 miles. 

It is possible that this is hardcoded, many things are not visible, so it is not possible to customize it.
but I'm not that familiar with it.


and btw 70-75nm are possible only you have to fly fast and high

 

Tacview-20231030-223148-DCS.zip(1).acmi

Edited by Hobel
Posted (edited)
1 hour ago, Hobel said:

It is possible that this is hardcoded, many things are not visible, so it is not possible to customize it.
but I'm not that familiar with it.


and btw 70-75nm are possible only you have to fly fast and high

 

Tacview-20231030-223148-DCS.zip(1).acmi 99.09 kB · 1 download

 

Trust me, I am fully aware of missile kinematics. The issue is not whether or not the missile can reach that far, it is that it is not tracking when it is launched from that far. If this feature is hard coded it would be quite a shame. This would be another example of ED permanently handicapping the modding community. 

We are routinely handicapped by arbitrary code-locks, meanwhile base-game systems such as cruise missiles are completely useless as a result of major game-breaking bugs that continue to be unresolved. I assume the phrase 'if it ain't broke don't try to fix it" has never once been spoken within ED.  

 

Here is another example: op_time value set at 200, the missile has more than enough energy to make course corrections and hit its target, but yet it remains completely blind, and misses by a mile. 

Tacview-20231115-124130-DCS.zip.acmi

Edited by bennyboy9800
  • Like 1

Intel i7 9700k CPU

Nvidia GTX 1080Ti

16GB RAM

Samsung 256GB SSD

Thrustmaster T16000m HOTAS

Posted (edited)

If 100 seconds is the realistic value, then unfortunately this is the case until new evidence is found. 

For example, the Russian 27ER has only 60 seconds, although it could theoretically fly much further, but 60 seconds is correct

 

Zitat

and misses by a mile. There is no reasonable explanation for this behavior other than that of bugged


When the battery is empty, the rocket logically no longer sees the target.

Edited by Hobel
  • Like 1
  • 2 weeks later...
Posted
On 11/15/2023 at 9:05 PM, Hobel said:

When the battery is empty, the rocket logically no longer sees the target.

It also can't steer either, since its actuators are electrically driven.

i5-4690K CPU 3.50Ghz @ 4.10GHz; 32GB DDR3 1600MHz; GeForce GTX 1660 Super; LG IPS225@1920x1080; Samsung SSD 860 EVO 1TB; Windows 10 Pro

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...