can not reproduce Maverick 65D second rack refuses to track since 2.7

[Gizmata]

I have been flying the A10 for 2 years and am well versed on using the 65D maverick.  Since 2.7, some seekers refuse to lock on anything, however after cycling the EO power, they return to function.  Typically the first missile will lock fine, but switching to the second rack (carrying 3 per side) will result in a non-locking missile.

 

Included test mission file which recreates what I saw one Syria map and a different Caucuses map

 

Test mission is on Caucuses using the A10CII with 3x 65D on each side.  Active pause (Left Windows + Left Shift + Pause) shortly after spawn with ground targets ~3 miles ahead.  Target and launch all on right wing, or fire one from right wing, then deactivate the right wing station in the DSMS, the Maverick camera will reset to the left wing missile and the new active missile won't lock unless you cycle EO power (3 minutes).

 

China Hat zoom level didn't make any difference.

Boat switch was forward.

 

I haven't seen anything like this in 2 years, so hopefully I am not the only one seeing this problem.

A10_Maverick_Test_04.miz

Edited April 30, 2021 by Gizmata
fixed wording left vs right for station to deactivate

[BIGNEWY]

Hi 

 

seems to be fine here 6 for 6 

 

can you make a track replay like mine so I can take a look at what you are doing closer.

 

thanks

 

 

6 for 6.trk

[Diesel_Thunder]

I ran a mission last night carrying 4 D model Mavs, and had no issues. All my shots tracked in and destroyed T-72’s. At least two were aimed with the TGP SPI (china hat fwd long), and one for sure aimed manually. No problems and all targets destroyed

[Gizmata]

I ran it again and created a track.  The first 65D (right rack) locked just fine, but the second (right rack) would not lock on anything.  I deselected the right rack and the left side rack locked fine, went back to the right rack and it still would not lock.  I then shut down the EO and started it again, and it locked fine.

 

65D fails to lock until reset.trk

[Gizmata]

I found a work around.  TMS forward short will make it try to lock when it doesn't even seem to be trying.  I hadn't needed to use TMS forward, to lock my targets before, so I didn't know that "feature" was added.  I always just used the slew to put the crosshair on a target and it would lock, but with 2.7 it seems to get into a mode where it doesn't try.

 

Also for anyone reading that missed it, TMS aft will break Maverick lock now, which should be helpful.  TGP targeting should be easier as well as once you slew the Maverick to the target point you don't need to bump the slew to get it to lock, just TMS forward short.

 

I still think something is off with the Maverick as it gets confused and won't target like it did prior to 2.7.

[Diesel_Thunder]

TMS forward short with Mavericks as SOI is the track command. If the crosshair gates aren't closed on the target, then you'll have to TMS forward short so the missile can attempt to establish a lock. At that point the crosshair should close (if it locks a target) and you can launch the missile.

 

If there is a high contrast target in view when the Mav stops slewing, then it generally will auto lock. If not you'll have to fly a bit closer and TMS forward short to command the Mav to initiate a lock.

 

That's the way it's worked for the past few years since I've been flying the DCS Hog (both the Warthog and Tank Killer). More info in the A-10 manual, page 588-589.

Edited May 1, 2021 by Diesel_Thunder

[Gizmata]

Looking at the A10C manual, quoted below, nothing says I must use the TMS to get the seeker to try to lock.  I haven't used TMS in launching over 1000 mavericks in the past 2 years, until 2.7 came out.

 

4. Slew the tracking gate over the target and release the slew control. When you release, the Maverick will attempt to lock onto the center of mass of a target it detects inside the tracking gate. If it cannot lock on to a target, after a few seconds, the seeker will go into Break Lock mode and the crosshairs will expand out to the edges of the display. To try to lock again, slew the tracking gate back on to the target and release the slew control. Depending on the range to target and the size of the target, this may take a few tries.

6. In addition to the slew and release method of locking a target, you may also keep the tracking gate in boresight and fly to place the tracking gate over the target and then press TMS Forward Short to initiate a lock. You can also do this when the tracking gate has been moved over a target while in a slave state (such as slaving your Maverick to the SPI).

 

Maybe they updated the A10 to work more realistic, it just seem wrong that the seekers won't even try to lock with me touching nothing besides the china hat and slew.

[Diesel_Thunder]

You don't have to use TMS forward short, but it is useful on distant low contrast targets. The seekers on the D and G model Mavs seem to have an easier time locking targets on their own if you are closer to the target and there is good thermal contrast between the target and its surroundings.

 

When I'm at max range, I have to use TMS forward short more often, usually also with china hat forward short to narrow the FOV.

 

I've worked with FLIR systems when I was in the military, and they have a much better time holding a lock when they are closer to the target object as there is a much better thermal contrast for the IR imager to work with. I operated gyro stabilized FLIR on ships, not IR seekers on missiles. The principles are the same between the two though.

Edited May 1, 2021 by Diesel_Thunder

[SliderCDN]

Flew the A10C v2 "in combat" first time last night and all 6 Ds went off just fine. Used TMS fwd short to lock moving tanks and BMPs just fine even under 1 mile.

[Frederf]

Releasing slew and TMS forward are the exact same commands to track. They have identical performance in acquiring track provided all other factors are equal.