DCS missiles

Since the inclusion of the AIM-54 it has become apparent that all missiles track targets without any source of guidance, be it aircraft radar or missile own seeker.

Once launched on a target if the shooting aircraft drops lock the missile continues to track as though it would HOJ. I think this is to do with some INS features ED added not so long ago.

This has become more apparent with the AIM54 because of its speed and range and this bug greatly exaggerates its capability.

This is a major bug and needs to be addressed.

I have attached 3 tracks

1. AIM-54 launched at approx. 50nmi, lock is immediately dropped but the missile continues to track targets lateral movements and then goes active at the appropriate range and splashes the target. (updated this track since update 2.5.4.29004)

As soon as the missile is launched the F-14s radar is switched off.

the missile flies out at 358 deg (353 tacview)

the target then cranks to the missiles left

the missile follows to 356 deg (351 tacview)

the target then starts cranking to the right

the missile follows and slowly turns to 002 deg (356 tacview)

just before the missile goes active the target starts cranking to the left

the missile starts following again just before going active.

If you watch the track with out changing views you will see this all happen.

2. AIM-120 does the same as above though launched at 35nmi (older DCS version 2.5.4.28840)

3. R27 is affected by the bug also but having no radar of its own never gets near the target. (older DCS version 2.5.4.28840)

AIM-120C tracking.rar

R27 tracking.rar

AIM-54 tracking 2.trk

I believe most modern missiles DO continue on an estimated course based on target's last heading and try to reacquire. Whether that's being modeled 100% accurately or not I can't say, but they don't just go dumb and fly in a straight line. The first two missiles you used would probably have this if available, the last one wouldn't but it also missed.

The missiles continuing to track inexplicably is a known bug, though, and the missile overhaul long talked about started with the F/A-18s Sparrow missiles which can read about in their dev updates. The tweaking of each missile will take time, though, it's not something they can just copy paste between them.

Does this only occur when a lock is dropped by the attacking plane? I have been doing some missile tests (in the stable release), but I haven't seen this behavior. Missiles will often just go dumb, or worse, perform a high g turn away from the target. Most of my cases were due to chaff I believe though.

If I have some time I'll try to replicate the issue.

I believe most modern missiles DO continue on an estimated course based on target's last heading and try to reacquire. Whether that's being modeled 100% accurately or not I can't say, but they don't just go dumb and fly in a straight line. The first two missiles you used would probably have this if available, the last one wouldn't but it also missed.

Yes an estimated course from last known is how an ins system would work but in DCS it doesn't stop there, it continues updating the targets aspect changes even though the host radar is switched off.

That is the point of this thread.

Does this only occur when a lock is dropped by the attacking plane? I have been doing some missile tests (in the stable release), but I haven't seen this behavior. Missiles will often just go dumb, or worse, perform a high g turn away from the target. Most of my cases were due to chaff I believe though.

 

 

If I have some time I'll try to replicate the issue.

Counter measures still apply and will stop the missile from trackng.

I looked at the AIM-54 and AIM-120 tracks. No missile was fired in the 54 track, so obviously it's bugged. There was a lunch in the 120 track, but it didn't look to be following the Su-27 until its own radar went active. It could also be bugged though.

I did my own testing and it looks like when lock is broken the missile follows a ghost target extrapolated from the last lock data. It doesn't go to the point where lock was lost, it follows the direction of the target as it was flying when lock was lost. It might look like it's still tracking because DCS missiles don't account for their own deceleration and need to constantly turn to adjust course as they slow down (which probably robs them of a good deal of energy).

I saw a video by Growling Sidewinder a while back where R-27s were still tracking him even after the death of the launching vehicle... However, they did not impact or detonate. It definitely has SOME bizarre behavior, but the missiles are being worked on as we speak, so we just have to wait until they work through them.

Does anybody know if the new AIM-7 Sparrow with the F-18 still does this? It's the 1st of the ''new'' missile format

I looked at the AIM-54 and AIM-120 tracks. No missile was fired in the 54 track, so obviously it's bugged. There was a lunch in the 120 track, but it didn't look to be following the Su-27 until its own radar went active. It could also be bugged though.

Playback of the F-14B/AIM-54 track was changed/broken by the 2.5.4.28840 ---> 2.5.4.29004 update i.e. I played all 3 tracks before and after.

Viewing Tacview, playback of the Hornet/AIM-120 and Flanker/R-27ER tracks looks the same in both versions.

Looking from the missiles perspective in tacview and using 'HUD' view the

• AIM-54 FPM tracked the last know position in 3D space until it's radar went active *

• AIM-120 FPM tracked about 6° right (i.e. away from the target), until it's radar went active.

• R-27ER FPM tracked about 4° left, then 7° right (i.e. away from the target) missing the target.

as this was played back in SP, it's possible the tracks don't match the original behaviour ?

*note: the track doesn't show a loft profile but the AIM-54 was launched from 45,000ft at a lower target at 20,000ft, so it's hard to say if it's a replay bug. The original play back showed the F-14B launching at 45,000ft and performing a split-S to level off at 28,000ft

I've updated the AIM54 track now on the original post since the update.

As soon as the missile is launched the F-14s radar is switched off.

the missile flies out at 358 deg (353 tacview)

the target then cranks to the missiles left

the missile follows to 356 deg (351 tacview)

the target then starts cranking to the right

the missile follows and slowly turns to 002 deg (356 tacview)

just before the missile goes active the target starts cranking to the left

the missile starts following again just before going active.

If you watch the track with out changing views you will see this all happen.

The track is on the opening post.

I've attached a tacview here

Tacview-20190328-113921-DCS.zip.rar

Indeed. It's not possible for the missile INS to anticipate that snaking maneuver back and forth.

Well, I don't mind this kind of bug with regards to the R-27ER...As long as I'm the one firing it!;):megalol: Does anyone know if the Super 530D is affected by this?