[NEED TRACK REPLAY]AGM65F not hitting assigned target

[Biga42]

Although the target was assigned via TGP the AGM 65F is hitting other nearby target, any one experienced this?

[arturojgt]

Yes, I think that we see the target trough TGP but is too far away and close together at the maximum range that maybe the IR head is picking the wrong but it seems ok to us because we are seeing the correct one in the TGP.

 

 

Dream Commodore 64C, 1530 datasette, 1541 floppy disk drive, DCS cartridge, competition pro joystick, 14” Tv with VCR.

[Harker]

Depressing the TDC with the TGP simply designates a point and the Maverick seeker is slaved to that point. That is all. After that, the missile seeker is free to lock whatever it sees. It's your job to verify the target via the IMAV page and make manual adjustments if needed.

[Biga42]

See the picture, although the TGP is locking the target, the AGM seeker head is point to the point were the the TGP's TDC depress was push, the seeker head does not slaved to TGP track target...what am I doing wrong?

Edited November 20, 2019 by Biga42

[NineLine]

DO you have a track you can share of the issue?

[Biga42]

Same with A100

 

the same with A10C

[Zarma]

See the picture, although the TGP is locking the target, the AGM seeker head is point to the point were the the TGP's TDC depress was push, the seeker head does not slaved to TGP track target...what am I doing wrong?

 

Because in the Hornet the "weapon designate point" isnt moving like the SPI in the A10C. If the target of the point mode is moving you have to re-designate from time to time.

[Biga42]

Zarma, please explain...

[Ramsay]

Zarma, please explain...

 

In the A-10C when the TGP is set as the SPI generator, the TGP constantly updates the SPI (sensor point of interest) and any sensors slaved to the SPI i.e. the maverick, also track the updated SPI.

 

That doesn't happen in the Hornet.

 

TDC designate creates a Target Point (you can think of it as special kind of mark point that has fields for weapon data).

 

So using the TGP, to lock a moving vehicle, TDC creates a 'fixed' Target Point that isn't updated automatically.

 

Hence the need to slew the Maverick's IR seeker onto the target.

 

When the TGP is point tracking a moving vehicle, it won't update/create the target point until TDC depress is used.

[Biga42]

ok, I got it and worked!! thanks! But..is this a bug or it's the way hornet does it?

[Harker]

ok, I got it and worked!! thanks! But..is this a bug or it's the way hornet does it?

AFAIK, the Hornet doesn't use SPI logic, like the A-10C does, so you can't create "movable" target points slaved to the TGP. Might be different with the AG radar, I don't know.

[Hamilton]

See the picture, although the TGP is locking the target, the AGM seeker head is point to the point were the the TGP's TDC depress was push, the seeker head does not slaved to TGP track target...what am I doing wrong?

 

 

the same with A10C

 

 

I´m also having exactly the same problem described with both F-18C and A-10C.

 

Thanks.

[Harker]

I just tested the A-10C and it works fine. I set up a moving vehicle, used the TGP in point track, TMS Up Long and now the TGP is generating the SPI. I then slaved the Maverick seeker to the SPI with China Hat Fwd Long and the seeker followed the SPI along its path. Maybe you missed a step in the procedure.

 

The reason the Hornet cannot do that is that, as mentioned above, it can't use the TGP to continuously update the target point.

I see no bug here, at least according to the capabilities of the DCS Hornet. And the A-10C is fine too.

[Biga42]

Yes...in A10 it works perfectly!!

[discwalker]

In Hornet not perfect

 

Lock can permamently jump after 1 sec from the tank to the nearby lightpole for example. (I can only extlemely close range point the seeker to the tank if 5 meters nearby a lightpole exists. EDIT:

)

In the attached degraded mission first play time I cannot hit the BUK launcher (Near Kobuleti, in the X airport) because mavF seeker cannot decide the lock between a tiny nothing and the big vehicle.

Two actual flights in the track. The second with a launch and an accidental hit from CLOSE.

2,5,5,39384_MAVF_cant_make_decision_when_tiny_object_is_close-2flight.trk

Edited November 26, 2019 by discwalker
youtube example of trouble locking up a terget

[NineLine]

Lock can permamently jump after 1 sec from the tank to the nearby lightpole for example. (I can only extlemely close range point the seeker to the tank if 5 meters nearby a lightpole exists.)

In the attached degraded mission first play time I cannot hit the BUK launcher (Near Kobuleti, in the X airport) because mavF seeker cannot decide the lock between a tiny nothing and the big vehicle.

Two actual flights in the track. The second with a launch and an accidental hit from CLOSE.

 

The maverick doesn't know the difference between a tank and a light pole and only likes what it likes, it can't make decisions, that is your job as a pilot. I have even seen a video of a pilot swearing at his Mavericks as he has trouble locking up a target. These weapons are not magic superweapons, they are faillable.