near_blind

Its 1 and 2. If it's not working, you could try a repair.

are you sure you have the latest version of the open beta downloaded? did you remap those controls at some point?

PD-STT offers longer range, look down capability and can guide the AIM-54 (if you're into that sort of thing). The main consideration is that it is susceptible to the Zero Doppler Notch, so if a target has relatively little closure < +/- 100 knots, the radar will drop lock. P-STT is shorter range (somewhere around 50 miles), has no doppler notch so should more reliably hold lock, but can't guide the AIM-54 (it can provide pre-launch cueing for an active off the rail shot). P-STT isn't susceptible to ground clutter unless the target is very low, but the modes that transition Pulse Doppler to Pulse, or if you're using Pulse Search are. Generally you want to use pulse against a closer, less cooperative (I.e. maneuvering) target. I would also recommend turning off the automatic switching to pulse. Jester will make that decision based on range alone, however he doesn't take into account whether the target is above or below you, or if the target is far off to either side. The further below you, and the further from center a target is, the more likely the PD->Pulse transition will fail and the lock will be dropped. Jester had a habit of trying this when I was deep into a crank supporting a Sparrow, and now I don't let jester try any more.

https://tenor.com/w6bq.gif

I'm curious what specific attribute of the radar you're using and does it affect all modes? PLM is a boresight lock with a range of 5 miles, so it's interesting that it's locking things above and below you.

The pilot doesn't have a switch explicitly for that purpose. I use tend to use PLM for this purpose, as long as there isn't a target at your boresight within 5 miles it will break lock and or reset your TWS scan. Failing that, you can ask Jester to break lock for you.

I mean, if we're asking for modest features... Skates AI Lady RIO dub. All The Carriers. Yes. All of them. Full Fidelity F-111B and F6D.

Each hangar can hold an SH-60 ASW helicopter

Of those 30 seconds, it takes 20 to accelerate to its max speed of Mach 2, and will be subsonic within 10 seconds of motor burn out. Can it work? Absolutely. Is that how I want to be expending my 80 mile hate javelins? definitely not.

As kindly provided in the initial post: https://trello.com/b/HsMiJggJ/heatblur-public-roadmap

If we're still referring to the provided Tacview, only 1 out of 6 of your missiles "ran out of juice because the target was at 10,000 ft", and that was against a defending fighter at the tail end of a 50 mile shot. What other missile in the game could have done better? In a more general sense, if you find yourself in a situation where you *have to think* about whether or not a Sparrow is the right choice, the Sparrow is probably the right choice and you shouldn't have an AIM-54s left on the jet. The point is you don't get AMRAAMs, direct all hate mail to the address of one Richard Cheney. There are a number of reasons the AIM-120 persisted as a generalist missile, while the AIM-54 did not persist at all. One of them is that while it _can_ be a very effective weapon, it needs to be used within a certain context to excel whereas something like an AMRAAM is more generally capable. We lucky few get to actually work for our kills instead of the bug and lawn dart aficionados. You do not want to shoot the missile down low. Period. You do want the missile to loft. Always. There are acknowledged bugs with the current guidance schema: over lofting, the missile not turning correctly in the terminal phase of flight. These are frustrating, I get that, but they will eventually be fixed, such is the nature of DCS development.

First miss bled all it's speed trying to cut the corner on an F-4 going Mach 1.5. Second miss was either notched while looking down or ran into a potential guidance issue with the algorithm that forms the P/N curves. Third miss was dragged low and bled of speed. Fourth miss was probably affected by the same P/N nonsense that caused #2. In real life that missile was probably close enough to fuze. The guidance is still WIP and will be until the API can be leveraged.

@EnDSchultz, do you have a copy of that mission and or tracks handy?

You can always tell Jester to select stations 2 and 7 before take off or while transiting, and then jettison them yourself using the ACM jett button.

https://pilotclimb.com/flight-path-vector-fpv/

Can't really say much without seeing what the missiles are doing. Do you have a acmi file?

When it gets done. Probably not before, ideally not after

It looks like Mike was saying that he believes the shooter maneuvered in such a way that the missiles didn't receive the active command, which would be extra important because with TGT size small that will occur later than normal. It isn't an extreme loft. There are issues with the loft and guidance algorithm that are acknowledged and will be worked out going forward. For now, manual lofting is advised against because it exacerbates that particular issue.

The radar will indicate when the track has been extrapolated because it can't correlate any hits to that track with an x over that track. Maneuvering will increase the probability that the radar goofs and the tracks will enter extrapolation, but you you should be okay as long as you don't exceed 3Gs and stay upright. It most should, but ironing out the guidance algorithms has always been an iterative process in the DCS-Sphere. Both the AIM-120 and AIM-7 went through these quibbles when they were transitioned to the new APN math.

*was* 12 miles. Your first shot was from medium-lowish altitude against a cold target at low altitude, it simply ran out of smash once the motor burnt out. The AIM-54 is far less fond of low altitude these days. Your second shot looks like it was still guiding on fish rather than bluebird, who was still beaming, only you were both lower and he was now faster, so an even more difficult shot for the missile.

It's a shame the right missile model doesn't exist, but it's amazing the kind of fun you can have with a few afternoons digging through the lua.

When you go STT, a azimuth/dlz indicator will pop up on your VDI, and it moves left or right depending on your own offset from the target. My experience is the limits of the VDI screen roughly work out to the gimbal limits of the radar, I.E. You will lose lock about the time that line moves off either edge of the screen. I personally will try and keep that line somewhere in the area between the edge of the screen and the limit of the horizon indicator bar as my goal for a good crank. I dunno if this was how it was intended to be meched or not, but I find it a useful gouge.

Instructions unclear: Sent it off boresight from 500 feet at cold target 20 miles away. ¿Por qué no funciona?

It was either notched, or it turned hard enough to gimbal itself, which is one of those things that need to be improved with guidance updates.

Sure. You're shooting too late and too low. If you want to throw first shots out at 30 miles, I'd suggest switching to Sparrows or something that fires AMRAAMs.