Jak525

I think he's talking about the fact the STT target trackfile is dropped upon exiting STT. Is that what you mean or are you talking about something else? Cause I figure the method by which STT is entered doesn't impact whether the track is dropped on return to search.. one niche case I'd think of being with the Gun selected you'd go to Gun Acquisition mode so the track would have to drop. Watch the video closely, it's confusing cause it's looped, but after exiting STT, the trackfile reverts to a SURV-only trackfile immediately. Thus the radar contribution is immediately dropped by the return to search command, which shouldn't happen under any case, right?

The radar is super difficult to use due to a lack of proper trackfile memory logic. Assuming there is no other MSI sensors involved, your trackfiles are going to delete quicker with a smaller scan volume and always as a function of frames, not purely time. So you won't have a trackfile delete when the radar hasn't even had the OPPORTUNITY to scan over it again. This missing logic is why it feels like the radar is "struggling" to maintain targets. As it's been explained before, the age out time should apply strictly to the display of the raw hit brick symbols, with zero effect on the trackfiles themselves.

As Harker said this is related to MSI as a whole. A total rework of trackfile memory is required so this report can really fall under the gigantic umbrella of "totally rework the A/A system/MSI". But the reported issue is a bug.

(Removed, I said something incorrect)

The X has to do with not meeting A/G RDY (ready) criteria. Different weapons have different requirements, can't remember if fuzing is required in DCS for the dumb bombs, but at the very least you need A/G master mode and master arm. Sadly this X-out cue only works correctly for some weapons, luckily the Mk-80 series being one of them. It's really actually a great thing that makes the Hornet very intuitive because you can clearly tell when your weapon is ready to go by the universal "X'd out" cue and the opposite "RDY" cue. I'd also note that if you are getting a store X'd out, it is definitely identified in the SMS. If it wasn't inventoried, it would not be showing up at all for selection.

When the Gun is selected there is no way out of ACM. Castle right however does not exit ACM. Use the Undesignate button on the stick (when the Gun isn't selected).

FYI, AOA button is not yet implemented in DCS (iirc) but it controls AOA data source. If I recall you can choose between air data computer, left probe, or right probe. FCS format shows all 3 read outs.

Yeah you should make a bug report. Per real pilot, it sweeps on the ground but doesn't transmit (hence Maltese cross is displayed, as Tholozor notes). Silent is different and should stop like it does in DCS, with the ability to hit ACTIVE and do a frame. But the behavior on the ground is wrong in DCS, it should keep sweeping.

Yeah, there's a missing ability to hit Undesignate to leave AACQ. Only really need it in this scenario where you have zero trackfiles, but still would be nice.

Correct, that's another issue; the actual performance assumptions are from before the AMRAAM was reworked, I don't think they've been updated. Regardless they don't work as they should even with the out of date assumptions.

Pretty sure RECCE should work for JHMCS blanking with TDC to az/el. You can hotas the Az/El EXPand via the cursor.

Bias is a sub function of Auto. Both are heavily simplified, but no. You should be able to go from Bias to Auto by hitting RSET though.

The Lost cue is bugged and totally useless. I explain the issue here. Really it should only flash for a few seconds, and then you'd be stuck with the Straight Line (SL) countdown, which is not resettable, but it'd obviously go away when the countdown is complete, or when a new missile is fired.

The very wrong mechanization of the jammer aside (which has been pointed out by a real pilot to me; you know it's reallyyy wrong when a pilot is able to say that one of the most sensitive systems is wrong), even with the radar off there is no reason you cannot designate or change the L&S. L&S is an MSI trackfile function not a radar function, but even pre-MSI don't know why you couldn't since it's not changing the radar, it's just a software designation. (Of course, locking them into STT is a different story which is impossible with the radar off.)

Please listen to Harker, everything he is saying is entirely correct and important. In other words: regardless of any debate over whether the radar can see missiles or dust particles or raining cats, it is not going to accidentally acquire ANYTHING that is not similar or identical to the commanded target of acquisition, with respect to range, bearing, direction, and closure rate.

@BIGNEWY refer to above post by Mo, real Hornet pilot. While this is being worked on it'd also be nice to fix the incorrect cage/Uncage behavior and L&S slave logic which I've reported before but I'll avoid going off on a tangent there (tl;dr the seeker/LnS angles are not being constantly checked), which is mostly also summed up by Mo there. I've reported this issue before and to keep it short and sweet, as Mo mentioned, it's always slaved to the L&S unless you hit cage/uncage, doesn't matter where the head is at all.

Undesignate actually designating is pretty funny but it is correct. You can call it the NWS or pinky button for less confusion. As Harker mentioned though, leaving STT should not kill your trackfile, it should be a smooth uninterrupted transition. Quite annoying. A relatively sweeping overhaul of the MSI trackfile system I think is required to fix this type of thing and others. As for undesignating the L&S via HOTAS, as Harker said you have RSET. Really there is not a big need to do this. Having an L&S is not a "soft lock", there is really no such thing. It will prioritize that trackfile for AUTO centering in TWS, but otherwise, the radar is not shooting any special beams at jt or changing its operation or whatever. STT is a different story which lights the RWR up - and you have the ability to leave that by hitting the Undesignate button.

LOST wouldn't even tell you if the datalink to the AMRAAM isn't getting there, because it's one way. However, yes there is a gigantic problem with the LOST cue. Basically it is representative of live parameters between the aircraft and the target, whereas it needs to be a simulation of how the missile is predicted to perform based on the instant it was launched. Basically after launching an AMRAAM, if you turn sharply, it will say LOST. But the AMRAAM was already fired so ownship maneuvers are totally irrelevant. For example, if I shoot a gun and then point the gun toward the floor, the bullet is still flying straight, cause I've already fired it. The LOST cueing however is not properly accounting for this. As for the LOST immediately at launch there may be an additional issue in multiplayer, I'm not sure though.

Yes, there is missing A/G Radar scan centering functionality. You cursor over the azimuth select option, hover over the azimuth you want, depress and hold the TDC which teleports the cursor to the center of the display. Then slew left/right and release to set the center. You can't just TDC depress around the display like in A/A since that makes a designation under the cursor.

RWR is not correlated with MSI trackfiles, you get the nails at the top of the ATTK/AZEL and around the SA. IFF transponder is though. But the RWR is separate.

You should not be able to be in CCIP with a target designated. The only bug here is that you can re-select CCIP to display the CCIP symbology again. What should happen is even re-selecting CCIP does nothing here, and it remains in AUTO. The only way to go back is to undesignate the target.

Yeah you should be able to center in RWS via the Attack format. Real annoying that's missing but oh well.

EXP SHOULD work in STT too, and it seems they put the pushbutton there despite being nonfunctional. The reason EXP is in STT is because of what I described above. The newer (newer as in newer, still quite old overall) STT RAID should not zoom in the display. So you have EXP there if you want to zoom in. Note TWS SCAN RAID is supposed to zoom in, and it does in DCS and works more or less right. EXP is inapplicable in SCAN RAID since jt does the same thing.

STT RAID is actually modeled wrongly in DCS. It's an older version. The version concurrent with MSI should not actually zoom in at all. SCAN RAID does, but RAID does not. You'd have to use EXPand for that as mentioned. You should be able to change the L&S in STT RAID, but actually the STT target would stay the same. This is not really modeled right, but will hopefully be fixed when MSI is. Basically the L&S can be different from the STT target. But yes, you would need to use the cursor to do all this since Undesignate will exit STT RAID/STT/SCAN RAID instead of stepping the L&S.

DCS doesn't actually simulate tracking i don't think so this'd be a fake thing. But I wouldn't oppose it still. It's possible I assume since they do change the tracking bars based on the size of the object.