Jak525

On the SA format, when an AA WYPT is designated and the same waypoint is also selected, the circle/number indication draws twice, a bit to the side. AA WYPT.miz.trk

This is an old thread, but just thought of it while reading the Hornet manual. From the DCS F/A-18 early access manual -- "If in NAV mode, [sensor control switch aft] toggles the AMPCD between the HSI, SLEW, and SA pages in that order." Just to clarify, this is still accurate to our Hornet and will be implemented, right?

When you have the HMD on and in the HACQ/LHCQ ACM modes, you can't do sensor control down for VACQ. You have to access VACQ via WACQ (sensor control left) and then down. When the HMD is off, VACQ can be accessed directly from BST mode. Given sensor control switch down has no other function in HACQ/LHCQ, this seems a bit odd.

Oh haha. I'm not 100% sure about the dashed diamond but looking at some YouTube videos that's definitely been the case for the full diamond all this time. Only makes sense for the dashed diamond, IMO. Side note, I think there is something not completely right about the dashed vs. full diamond; for example if you designate in AUTO bombing via the HUD only, it's always dashed, but if you designate a waypoint as TGT then slew it around, you can still slew it and it remains full, unless you TDC depress with an AUTO bomb, in which case it becomes dashed. The waypoint itself is never undesignated either which is weird since the TGT changes but the waypoint obviously remains a constant. I'm sure this will be fleshed out when we get the targeting pod and stuff in though.

A note on #3, you usually calibrate your altimeter to the QNH, so it reads 0 when at 0ft sea level. QFE is the pressure at X altitude. QNH is the pressure at 0ft above mean sea level (MSL). At 0ft, QFE=QNH.

Yeah I'm assuming it is supposed to be there when TDC is on the HUD, just like it is in the velocity vector and the full diamond indication

Interesting. Would like to see a response from ED on this

With the segmented A/G target diamond, there is always a dot in the center. When the HUD is made TDC priority, the dot simply gets brighter. This is in contrast to the full diamond which does not have any circle except when the HUD is TDC priority. Track attached demonstrating both of these. AG diamond glitch.miz.trk

When you designate a waypoint (and I assume later, where a TGP is pointing, JHMCS, A/G radar, etc) as the A/G TGT, it appears as a diamond on the ground. If you designate the HUD as TDC priority, you can slew the full diamond around with the cursor, while the waypoint on the HSI remains designated and in the same place. If you TDC depress and have a bomb in AUTO mode, it becomes a segmented diamond instead. If you designate a target in AUTO via the HUD only, it's always a segmented diamond. Is this all intentional behavior? If so, what exactly does segmented vs. full diamond symbolize? It seems like it's for a HUD-designated AUTO bombing location, but you can slew around the A/G TGT designated by a waypoint on the HUD as well, and it will stay a full diamond, provided TDC depress isn't done, and the waypoint still remains designated as TGT and does not move despite slewing it on the HUD. It seems like when you slew a full diamond on the HUD, it should become segmented and then the waypoint become undesignated.

IFF on has to do with the IFF transponder in the plane. It turns that on. Yes, it means SCS depress over the target on the RDRA TTK / SA format.

It does indeed. You need a) Mode 4 + NCTR or b) Mode 4 + SURV or F/F donor. And yes, this is correct, the airplane stores trackfile information about the contact.

Yeah re-reading the bug report I linked it actually says more of the same things I have said than I thought lol -- and that bug was marked as reported. Although, it would still be nice to see a clarification as to whether or not LTWS L&S NCTR is intentional, and it's just not showing on SA, or it's completely unintentional. I'm definitely less concerned about my own post being recognized than the bug being sorted out though haha

Edit -- I've just done another test with NCTR off. After ensuring I was within range for NCTR (and aspect), the moment I turned NCTR on it ident'd hostile (again, no NCTR result on SA page and had LTWS L&S designation the entire time). Track attached LTWS NCTR off.miz.trk

Hey could this get a tag/response? There's definitely an issue here I think

He means if you trim out an asymmetric load, and then when you release all your bombs, presumably then being symmetrical again, you'll need to trim back.

I saw Wags saying in a YouTube comment they don't have any info on it, so I don't believe so.

Use AACQ. It will lock the closest target automatically, any range within the radar's current settings. Although there's currently a bug where it doesn't always get the closest one. Reported though, I think Wags mentioned it recently.

Go to your keybindings menu. Press whatever button you have bound to the FLIR FOV/RAID/HARM sequencer button. Make sure it jumps to said binding and highlights it. If it doesn't, the button isn't being registered. If it does highlight, you have some other problem. Also, in the track you posted, you did not assign TDC priority to the left DDI

MODE > MAP. It's able to be toggled.

Done

NCTR via LTWS? [TRACK ATTACHED] So a bug was reported a bit ago about being able to identify something as hostile with only an LTWS L&S designation. However, I just noticed in Wags' datalink video when it initially came out, he said in the description NCTR requires an "L&S or STT" (also states in the manual). If you just L&S a target, it will not show an NCTR result on the SA format. So my question is, is LTWS L&S supposed to be able to get an NCTR print, and thus there is a bug where it doesn't show up on SA, or is it not supposed to be able to get an NCTR print, and thus there is a bug where planes are being designated hostile when they shouldn't (as reported in the linked bug post)? I did a bit of investigating -- track attached. I believe the plane is indeed NCTR printing the target via LTWS, it's just not showing up on SA (again, let us know if this is correct behavior or not). I started the mission against another plane and at a high angle, so an NCTR couldn't be made. I had an L&S LTWS designation the entire time. Upon getting in range and within about 30 degrees of his tail, it became a hostile. SA page never displayed an NCTR ID so this is a bug even if LTWS is supposed to be able to do an NCTR. I did another quick test and it does not seem to be the same case for the DT2. LTWS NCTR test.miz.trk

You're pretty much right here. However, the barometric pressure you set is the pressure at 0ft ASL. You're essentially telling the altimeter "when your pressure is the same as the pressure I dial in, the altitude is 0ft." From that it will know the altitude above sea level (or technically below; there are some places a few hundred feet in negative altitude). The reason they set standard pressure (29.92) above the transition altitude (in the USA it's 18,000ft, in Europe it's more variable) is not because of there not being weather readings at that altitude. All you need to know is the pressure at sea level. Pressure decreases at a fixed pattern as altitude increases. The reason they do this is simply so the altimeter doesn't have to be continuously updated during cruise. You could continue updating the altimeter if you wanted (technically speaking that is; setting standard pressure is a requirement).

A bug was reported a bit ago about being able to identify something as hostile with only an LTWS L&S designation. However, I just noticed in Wags' datalink video when it initially came out, he said in the description NCTR requires an "L&S or STT" (also states in the manual). If you just L&S a target, it will not show an NCTR result on the SA format. So my question is, is LTWS L&S supposed to be able to get an NCTR print, and thus there is a bug where it doesn't show up on SA, or is it not supposed to be able to get an NCTR print, and thus there is a bug where planes are being designated hostile when they shouldn't (as reported in the linked bug post)? EDIT: Track attached. I believe the plane is indeed NCTR printing the target via LTWS, it's just not showing up on SA (again, let us know if this is correct behavior or not). I started the mission against another plane and at a high angle, so an NCTR couldn't be made. I had an L&S LTWS designation the entire time. Upon getting in range and within about 30 degrees of his tail, it became a hostile. SA page never displayed an NCTR ID so this is a bug even if LTWS is supposed to be able to do an NCTR.. EDIT 2: Did a quick test and it does not seem to be the same case for the DT2.

Try deflecting the stick in the direction of the crosswind

Yes, like every other feature the Lot 20 F/A-18 has xD When it will be implemented, don't know. It's not in the short term goals