Maverick hitting the wrong target

[apolloace]

Hi,

 

I have had this problem quite a few times.

 

I am engaging a column of vehicles on road. The Strela unit protecting the group is at the end of the column.

 

As I am locking up the Strela & firing a AGM-65D, to take out the Air Defence unit first, the Maverick is hitting the vehicle next to the Strela.

The next missile then takes out the next alive unit, though I have the Strela firmly locked in the TGP.

I have no option but to hit the Strela unit with a GBU/JDAM from high altitude.

 

Any suggestions why this might happen? :helpsmilie:

 

[MacTheGoon]

Are you setting the strela in your TGP as SPI and slaving the mav to it afterwards?

[apolloace]

Are you setting the strela in your TGP as SPI and slaving the mav to it afterwards?

 

Yes!

 

Even if, the SPI is not set properly & the Mav not slaved to it, the missile will hit somewhere else.

 

Why is it always hitting the next alive unit?

[kerlix]

My only guess is that with moving vehicles at a (slightly) longer range, the SPI is losing track of your intended target and locking on to the next moving vehicle before you can slave the MAV to it.

 

When the MAV is slaved, try zooming in (is the china hat forward-short? I forget) to make sure you're on the right vehicle. If not, maintain stable flight and manually slew it over to the target of choice, lock it up and fire.

 

That's really all I can think of. Unless some unknown, unreported new bug has reared it's head. But I haven't seen similar complaints so I'm thinking it's something along the lines of what I described. It's happened to me before, so I know how it looks and the disappointment that follows when the wrong bad guys die first.

[DoctorStrop]

This has happened to me twice. Once I had the HUD as SPI, and the second time I has knocked the steer-point button on my HOTAS by mistake. I always make sure I can see the MAV crosshair cycling with the steer-points before I start my run in.

 

Not saying this is what happened to you, just saying how I cocked up.

[KLR Rico]

My only guess is that with moving vehicles at a (slightly) longer range, the SPI is losing track of your intended target and locking on to the next moving vehicle before you can slave the MAV to it.

 

I think it's something along those lines. In a convoy with closely spaced vehicles, you have to get pretty close before the mav's sensor can resolve individual targets. I'd guess it usually needs to be within 4-5 miles to do that. Otherwise, the sensor attempts to lock onto the whole convoy and eventually settles on one target, just not the one you wanted.

[Xavven]

I don't mind that this happens even if it's considered a bug by computer simulation standards. I think I remember reading in A10's Over Kosovo that the AGM-65D sometimes gets confused and locks on to hot spots on the ground other than the intended target, just like any other missile can get trashed with flares or chaff.

 

Actually, sometimes I wonder if the AGM-65D in DCS is too good since it doesn't seem to lose tracking when the target vehicle passes behind foliage, like trees for example.

[Aginor]

Yeah, our Maverick has a much better, almost magical quality compared to real life. So I don't really mind when it happens to me sometimes.

[stefaanadriansens]

it will go to the target with the most heat . dont fire it near a destroyed vehicle or glowing buildings

[WildBillKelsoe]

slave to tgp then set mav as soi and tms down short while slewing, when the crosshairs start to tickle, rail off

 

 

Sent from my iPhone using Tapatalk