Mavericks are not hitting the target

did a mission and also the Maverick training mission. It is not hitting the target locked, it´s buged!

Please post a track

I have just tried the training mission and first Maverick hit the target I had locked

Please post a track

Here is the tacview

Missing for me routinely. Also JDAM bug appears to be back.... Sigh. Both JDAM and Maverick routinely missing for me now.

Have you got the DCS track to look at?

Here is the tacview

Are you aware of the keyhole limitation for Mavericks?

According to the Tacview, your nose was pointing fairly far away from the target both laterally and horizontally - well, at least that's my guess, because Tacview doesn't tell us what you targeted.

But something have changed, because I've already finish this campaign and worked fine.

Post a track to eliminate all human factors, the tacview doesn't tell the entire story.

Well in the real world Mavericks aren’t 100% effective so “maybe” ED is simulating that (although i doubt it).

I have flown lots of times with them today in various missions in the A-10c - hitting fairly well but now have the white smoke shader issue and cannot shake it

Just flew a mission...9 of 9 mavericks (3 x D, 3 x G and 3 x H) hit their designated targets dead center.

here is the trk file

https://drive.google.com/file/d/1loOOoEmcLXP0HPEceetgEB9prqz0sIQ0/view?usp=sharing

here is the trk file

Nothing wrong there, your second shots are made when the seeker pointing cross is outside of the keyhole limits, so the missile looses track.

Images from your track

here is the trk file

In the replay, I saw the first AGM-65H score a direct hit.

The second was clearly outside of the keyhole limits and missed the target completely.

Moments before 2nd AGM-65H rifle:

With the AGM-65D, I observed the exact same thing: the first shot was well within keyhole limits and the missile scored a direct hit, the second missile was clearly beyond keyhole and missed.

Moments before 2nd AGM-65D rifle:

The keyhole limitation has been implemented for years now. If your missiles hit two weeks ago and miss now, I don't think the DCS version has anything to do with it.

There was a problem with Mavs a while ago where missiles from the side-rails of the LAU-88 always missed, while the missile from the lower rail would not suffer from that problem. However, in your track, the outer-rail-missiles hit, and the lower-rail-missiles missed, so it seems unlikely that this particular bug has resurfaced. Plus, once again, both hits were within keyhole, both misses were outside of it.

On a side note, you never retracted the flaps; during the run-in with 65D's, that resulted in a FLAPS indication on the MFCD and meant that you would not have been able to shoot the Maverick. Above 200 KIAS, the flaps retract automatically, so it was "by accident" that you were able to shoot at all.

All things considered, I'm certain your technique is bad, and that is the reason your results are hit and miss (pun intended, to be honest :D).

Edit: And sniped ;)

Thank you all you guys for take your time to show me what I was doing wrong. It was quite a while I was not flying the A-10C and have forgotten the basics. You're amazing!

I can confirm also since this update jdam falling short of target. Never happened to me before.

I can confirm also since this update jdam falling short of target. Never happened to me before.

Please find a suitable thread to report that.

When you do, it would help if you could include a version number.

At the very least, there's Stable and OpenBeta, so "this update" is ambiguous.

Same problem here, with the latest release version

2.5.5.32533 Maverick AGM 65D perfectly locked on target

(T-90) but not hitting it.

Same problem here, with the latest release version

2.5.5.32533 Maverick AGM 65D perfectly locked on target

(T-90) but not hitting it.

Same problem? The problem in this thread turned out to be user error, so are you saying that you too are using the Maverick incorrectly? /s

I think you might need to open another thread if you found a problem with the AGM-65D's tracking.

Same problem? The problem in this thread turned out to be user error, so are you saying that you too are using the Maverick incorrectly? /s

 

 

 

I think you might need to open another thread if you found a problem with the AGM-65D's tracking.

I am using the Mavericks correctly, as I have done for years now. With the latest release version

2.5.5.32533 Maverick AGM 65D perfectly locked on target

(T-90) but not hitting it, random, about half of the time.

I am using the Mavericks correctly, as I have done for years now. With the latest release version

2.5.5.32533 Maverick AGM 65D perfectly locked on target

(T-90) but not hitting it, random, about half of the time.

As I just said, this thread is not about a bug, it is about user error. If you found a bug, you might need to open a new thread.

Same problem here, with the latest release version 2.5.5.32533 Maverick AGM 65D perfectly locked on target (T-90) but not hitting it.

Please post a track.

Definitely need to see a track - I have just flown a test mission I have for the A-10c and from 6000 feet hit 4 out of 4 targets (3*BMP, 1*MBT)

I am flying latest OB (2.5.5.33057)