Santi871

Indeed, it's one of those things that seem to be tucked away. I checked cause I had heard conflicting info. I assume markpoints used to be the old school way of doing it and have been replaced with more in depth functions.

If you look in the NATOPS description of the HSI, it says markpoints are created at the A/G designation position if one exists, or overfly point if it doesn't.

Reported, thanks. FLIR and HUD designations are showing a couple of missing features that do work with nav designations (WPDSG). That is, when a FLIR/HUD designation is performed, the designation diamond symbol does not show in the HSI/SA, and TGT steering is not selected in those either. It should work the same way as with a nav designation so I've reported that.

thanks, I'll look into this

Make sure that TDC priority is on the FLIR DDI.

You can't slew the FLIR in VVSLV, but you can depress TDC to create a designation where it's pointing, and then slew from there (VVSLV will be exited when you depress TDC).

thanks, reported

Did you cycle the filter to NONE after those trackfiles were formed? Or did those trackfiles form with the filter already in NONE?

I can see the aspect vector for the L&S but it does seem to go away in STT. Outside of STT it works though, are you certain you can't see it for the L&S outside of STT?

PRF shouldn't be able to be changed by operator action in STT, but seeing as the Sparrow still tracks, I'd say this is a relatively minor/visual bug

PDI means Pulse Doppler Illumination in the Hornet, interleaved is INTL. Harker is correct in that tracking in PDI PRF should need to be retained during the Sparrow's entire flight or else it will be trashed. So that is a bug.

Are you talking about the LOST cue in the HUD? or is the Sparrow actually losing track?

Thanks, I've reported this. Sorry that it got buried for quite a while.

It's reported, thanks

Could you attach a track?

I've reported this. The rest is correct I think.

RDY should flash at 1.5/10. Make sure you're not rearming, and that you wait a few seconds for the electrical system to stabilize after the engine turning on (should be visible as the MFDs running their BIT twice). PS: could you make a track that doesn't rely on extra content?

your guess is correct, it should be included in the next OB update

thanks, it's already reported internally

this is fixed internally

This is already reported, thanks though.

From the docs I have it appears to be correct: The Link 16 TIME label and entry field are blanked when GPS TIME ON is selected and GPS is operating. If I switch GPS TIME to OFF then the TIME appears. Are you positive it's certainly a bug?

You're misunderstanding my post, which wasn't very clear. Whatever electrical issue caused the MFDs to flash is causing the INS alignment to reset. I don't know what's causing it, or if it should be happening, but the fix is to start aligning after that happens.

You need to wait until the MFDs are past the bootup screens to start alignment. You switch the INS knob to stored heading before that happens and then it resets which ruins the stored heading align.

It's already reported. For now, you need to press uncage for aim9 to slave to the target.