Default774

In game perspectives of all tracks NEZ https://streamable.com/yf3mrd Half range https://streamable.com/7rwaw3 BVR https://streamable.com/tg5awm

The AIM-120 is still very vulnerable to barrel roll manoeuvres at higher altitudes. A well timed barrel roll defeats the missile every single time. 120_barrelroll_BVR.trk 120_barrelroll_HALFRANGE.trk 120_barrelroll_NEZ.trk 120_barrelroll_BVR.acmi 120_barrelroll_HALFRANGE.acmi 120_barrelroll_NEZ.acmi

The AIM-120 sometimes fails to acquire targets that are in a constant speed/altitude turn. In both of the test runs, I am performing a mach 1.07 430kts CAS and mach 1.03 410kts CAS constant turns at 30000ft of altitude. The AI is set to launch at Half NEZ-Max range, however, this shouldn't matter here, as the missile has plenty of energy to reach the target still. This issue seems to be related to the missile going active when the target is going roughly cold. 120_circle1.acmi 120_circle1.trk 120_circle2.acmi 120_circle2.trk

The closest distance tacview indicates is 46ft(take with a grain of salt, tacview polling rate is slow). Whether this is distance to the center of the plane, the pilots head, whatever, it seems too far for the missile to proximity fuse here. I don't see the issue here

I don't think this is an entirely unreasonable miss. Your missile is at around mach 0.7 at the terminal stage which is very slow. Adding to that the AI was defending quite erratically. Your missile is very slow, so it has to make harsh manoeuvres to keep on target. Your missile is having to pull over 25deg of AOA to keep on target at this speed. As for the proximity fuse, you only have a tacview which is notoriously inaccurate due to the slow polling rate.

Additional track to look at with other angle and background, might matter . In this track the notch was especially poor (~100deg relative angle) and the missile still seemed to get decoyed by chaff. 120_postchaff3.acmi 120_postchaff3.trk

If you're referring to my earlier comment of the missile losing track 1:40 into the mission, the missile battery doesn't apply here at all. The AI fires about 20-30 seconds after mission start because my test mission has an unnecessarily large distance between the aircraft at spawn. The missile is nowhere close to 100 seconds of flight when it loses track and keeps emitting after it loses track

Same behaviour occurs in lookup as well. hm1&3 show the missile losing track in the defending turn which doesn't make a lot of sense to me (Separate issue?). 120_hm1.trk 120_hm2.trk 120_hm3.trk 120_hm1.acmi 120_hm2.acmi 120_hm3.acmi

After doing some more testing. Attached is a new track where I don't break off after the missile loses track. The missile loses track at around 1:40 into the track. You know the missile loses track because the missile launch tone stops playing on the RWR (Side note, why does this happen?). As soon as the missile loses track, there is about a 50-60kt TAS difference between the missile and the target (Tacview numbers, not very accurate). Of course I don't have access to debug tools that would show when the missile precisely loses track and why, so this is my best guess. In this track, I keep accelerating after the missile loses track on the same trajectory. Despite the relative speed between the missile and target increasing, the missile never regains track. If the missile lost track due to near equal speed, why does it not reacquire when this is no longer the case? Does the missile have a mechanism that prevents it from reacquiring here? Another side note, I know that notching behaviour is affected by whether or not the missile is looking down into the ground or the water. Notching a missile above water is (as far as I've experienced) much much more difficult than notching over land. Does the same effect not apply here? 120_spd1.acmi 120_spd1.trk

The tacview is inaccurate in this case, missile was fired while rolling. https://streamable.com/5ipq6c

Player POV tracks here. No snapping observed as missile does not reacquire at all. 120_pc3.trk 120_pc1.acmi 120_pc1.trk 120_pc2.trk 120_pc2.acmi 120_pc3.acmi

The AIM-120 is prone to losing track on cold targets, even when there is sufficient doppler shift present from relative velocity. Additionally, the missile exhibits the often observed snapping after losing and regaining track on its target. The cld3 track shows the issue most clearly, even with 200knots of relative velocity, the missile still loses track on the target. After the AI makes a slight turn while defending, the missile regains track on the target and proceeds to snap wildly losing its speed. Disregard the missile losing track of the target completely at the end of cld1&2, this is the missiles battery running out. All midcourse support is broken upon pitbull so the missile is completely on its own. 120_cld1.acmi 120_cld2.acmi 120_cld3.acmi 120_cld1.trk 120_cld2.trk 120_cld3.trk

Look up notch is performed in the tracks to make the missile go for chaff. After the missile gets chaffed, the guidance becomes abnormal, repeatedly snapping between the targeted aircraft and the chaff which decoyed the missile. This doesn't seem intentional. 120_postchaff1.trk 120_postchaff2.trk 120_postchaff1.acmi 120_postchaff2.acmi

Additional edge case track for the initial oscillations mentioned. Test was performed over land so the missile can lose track as notching is virtually impossible over water now. Missile acquires very late in flight, probably too late to respond properly and still hit. Nonetheless, the oscillations/snapping are present. 120_a1.trk 120_a1.acmi

I know what notching is. A quick look at the tacview shows that the relative angle is around 50 degrees; nowhere near enough to notch the missile. Not to mention this test was performed over water, which effectively prevents notching as of 2.8.

The AIM-120 does not consistently acquire a flanking target on active, even when the missile is fully supported through the entire midcourse stage. The missile never acquires the target even though it is being provided datalink updates from the parent aircraft. 120_naq.trk 120_naq2.trk 120_naq.acmi 120_naq2.acmi

The JSOW-A is unable to hit targets on certain very high mountains. The submunitions never get released and the JSOWs eventually hit the ground after attempting to circle around. jsow_a_1.trk jsow_a_1.acmi

Additional tracks, over the top and bottom shots seem to have changed aswell. 120_h3.acmi 120_h4.acmi 120_h5.acmi 120_h6.acmi 120_h3.trk 120_h4.trk 120_h5.trk 120_h6.trk

The PATRIOT is extremely unreliable for shooting incoming munitions such as PGMs(JSOWs) and ARMs(HARMs). The missiles often self detonate before reaching the target, or miss the target by a small margin. At closer ranges the missiles dont seem to guide at all and just go straight, obviously missing the target. First track shows a lone patriot site attempting to intercept one(1) incoming AGM-88. The site fires a total of 9 missiles at the target, all of which miss. The second track shows the same patriot site attempting to intercept two incoming AGM-154s. It takes the patriot site a whopping 25 missiles to intercept these two slow moving targets going perfectly straight. Last track shows the patriot attempt to intercept two incoming mavericks. This shows the missiles self detonating inexplicably before reaching the target very well. patrior_jsw.acmi patriot.acmi patriot_mav.acmi patriot.trk patriot_jsw.trk patriot_mav.trk

F-16 HMCS logic changed so some old tracks no longer work, remade side on shots which now show different behaviour. 120_h2.trk 120_h1.trk 120_h1.acmi 120_h2.acmi

The Tunguska is currently unable to hit targets that are not flying directly towards or away from it. The missiles exhibit left-right twitching, jittery guidance and do not hit their target(See track, tacview polling rate is too low to show this). AI set to maximum skill. tgs.acmi tgs2.acmi tgs.trk tgs2.trk

Addendum to this, original tracks no longer work in the newest OB version as the 120 seeker behaviour seems to have changed. The missile no longer loses track initially in the above tracks so there is obviously no reaqcuisition to snap off of. Thankfully, I've managed to reproduce the snapping off of INS in the newest OB version. 120_t2.trk 120_t3.acmi 120_t1.acmi 120_t2.acmi 120_t1.trk 120_t3.trk

this is fixed yes

Last thread was locked with a notice to wait for a future patch, after retesting this in the latest patch the issue was not fixed. Same track as last report can be used, as it still works. MC_GM_SIL.trk

The AIM-120 exhibits snapping behaviour when acquiring targets when either extrapolating/on INS. The missile will aggressively snap to the target as soon as the seeker (re)aqcuires the target. In high altitude situations the missile snaps to target and doesnt oscillate. At lower altitudes the missile snaps to target, and also starts oscillating as it tries to guide onto the target, sometimes missing due to this. This behaviour occurs most often when either reacquiring a target when it leaves the notch or more commonly when the missile acquires a target off of INS. If the target deviates from the predicted path of the target and the seeker still acquires it, the missile will snap to the target aggressively. 120_y2.acmi 120_y1.acmi 120_y2.trk 120_y1.trk