fmedges

A covey launch. Note 6 in the attachment. This is out of the speed and angels carrier operations guide.

Yep, something with the pod. Can someone recreate it and post a track here so that they’ll fix it?

We typically use MIDS A and B for interflight/squadron which frees aux up for monitoring other buttons.

Agreed

If it is working correctly then they should change the text to “Realistic maverick tdc slew” as it only covers that one specific thing. Pretty bad user experience if that’s the case in my opinion.

I really wish custom spawn spots would be a feature for this module.

Positive rate of climb and turn to BRC. Once at 600ft do a left 27 degree turn, similar to when you are behind the ship but maintain 600 ft. That should put you on the right abeam distance for your downwind. From there just fly the remaining case 1 pattern. If there are other planes (for instance coming in for the break) which ever gets to the bow first has priority and who doesn’t have that priority needs to slot in with appropriate spacing. For the CQ pattern once you leave the cat establish a climb to 600, lower hook and flaps and as above do a left hand 27 degree level turn at 600ft. Once established on the downwind fly the remaining case 1 pattern.

That’s really low

Radars are really sensitive to fragments. It doesn't take much to destroy them.

What aspect did you attack the convoy from? Keep in mind that when the laser goes on it has to be in the seeker heads field of view. I’ve found that attacking very fast moving vehicles from the front or sides can (depending on the drop altitude) cause the bomb to not see the laser and just go ballistic into the ground. Check your track file, you’ll be able to see if the bomb saw the laser or not.

For the lot number that we have that’s correct behavior

Appreciate you looking into it.

I've noticed a contact shows up on D/L, SA Page and on the attack radar when the radar is at 160NM, when decreased to 80NM it disappears from the attack radar display even though it's within 80NM. Track attached. Link_Not_Showing_Up.trk

Why does the F-16 not have the same bloom effect?

It should track as well?

How are you getting those ranges? The Second picture is at 30 miles with the missile at my 6 hence me using the aft antenna. The One with the pod is at 16.9 miles.

I've seen it as well, but when flying that far my track file is too large to attach here in the forums.

Was the seeker head via the datalink really that bad as it is in DCS? I say beyond 15 it's barely useable. I can't imagine (even though it was a quick process) that the test squadron sent a stand off weapon to the fleet with the seeker head un-useable beyond 15-20 miles.

Yeah, it’s quite frustrating from a user experience standpoint. There is both a beta build and stable build but both are a mess in terms of consistency with regards to the missile behavior.

No I don’t think that you are wrong, it does need some improvements.

I didn’t explain very well what I meant. The in game JTAC uses the 6 digit grid so there’s still a bit of searching involved and when I enter in waypoints I only use preside grid. The 6 digit is off by too much for my purposes.

In my experience non precise grid coords are still not even close.

As above thank you. This is awesome.

I think the issue turned out to be not updating the auto aim point via a tdc depress closer to release. Because of this the bomb fell, but the laser was outside of the seeker heads field of view. Why does the pod update it's coordinates when slewed, but this doesn't also update the aim point for auto releases? Is this how it is in the actual plane?

I was creating mark points last night using the pod and the when I weapon designated the created mark point it was not where the pod crosshairs were when creating said mark point.