AvroLanc

Yes, but how does the Maverick know where to look exactly at that nav location? The seeker would still be off by an alignment error. Every seeker slightly different, rail + pylon installation error etc etc. There might not be an alignment/boresighting procedure in the Hornet IRL, but if so, it shouldn't be possible to get a perfect 'handoff' everytime. If there really isn't a boresigting mechanic in the Hornet, then IRL a separate MAV slew was needed every time. Which sounds semi-plausible.

IN LAR shows shows instead of SHOOT, when locked on a friendly. It’s bad form for the avionics to tell you to shoot a friendly.

Ahh OK, if the AI only transmit when in STT, then that explains it. It used to work in plain search though. Frustrating. Yep, PM me at some point, time's a bit tight later unfortunately.

Ok I agree, but I think that highlights another Bug lol.... If you deselect SURV or have no AWACS why aren't we getting the F/F (members) link information? I've made a track/report about this a few weeks ago. I don't think it's fixed. Can you see what I mean? edit: original bug report https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-f-a-18c-hornet/bugs-aa/291070-investigating-f-f-datalink-contracts-not-showing

Yeah, I'm not saying the HMD is MIDS exclusive, just that it needs a contact to have a MIDS contribution to display something (unless obviously it's your own L&S). The Top HAFU represents a MIDS contact that your OWN radar can also see. Again, I'm guessing to a certain amount since there's no documentation yet. It's logical (I think) to me.

Sorry, I'm not sure if we're understanding each other. What do you mean by 'you get stuck with your own HAFU status which is bugged'? I've taken control of your track and it behaves logically: Start using SIL to silence the radar. I notice that the bottom half HAFU's are displayed with the correct shape for the contact. Now, activate the radar and I see that the bottom shape is replaced by a top shape, except the top shape is now an unknown staple. Because the HMD only displays MIDS, the disappearance of the bottom isn't a major problem. I know it's a datalink link contact that I need to IFF. Is your issue the unknown status? Are you expecting a top and bottom togther? If you SIL again, the contacts revert to a pure DL with correct HAFU status. Maybe this is intended and represents the need to IFF an unknown contact, just like the radar. I don't know, it seems logical to me atm.

Yep, watched the track. It's the same behavior as I was describing. My opinion is that you should LOSE the bottom HAFU when your radar paints the target (in the JHMCS display). The HAFUs on the HMD are MIDS INFORMATION. They can't be directly compared with the radar HAFU's, since the HMD doesn't display raw radar hits. As such, they always represent datalink contacts. A top and bottom half together are superfluous. There's no need to show a diamond like shape. Bottom Half - MIDs contact not detected by own radar. Top Half - MIDs contact also detected by own radar. Again, there's a bug with Donor only (non-AWACS) HAFU's not displaying bottom half on RDR page but that's a related but separate bug.

I'm not actually sure this is a bug as far as the JHMCS is concerned. Remember, the symbols we're are seeing in the HMD are MIDS Contacts by definition. Not radar contacts. Since all the HAFU's shown in the HMD are datalink contacts you only need either a top half or a bottom half. Bottom Half - MIDs contact not detected by own radar. Top Half - MIDs contact also detected by own radar. I would agree that a potential bug is on the radar page. When an AWACS is not available, or SURV deselected, the bottom half of a datalink contact is never shown on the RDR page. Even with SIL selected.

There's an additional page within the HMD control page. It's called 'MIDS Info'. Within that page you can set the priority of the 5 different MIDs symbols to show. You can also set the max display range of the contacts. I've not tested extensively, but seems to work, especially the display range.

So.....I'm thinking maybe the fix is delayed due to the addition of some of the later suite voice warnings? Maybe 'chaff/flare', 'missile missile' etc Would be nice.

Ahh OK, I’ll take a second look. Cheers.

With the new changes, how do you tell whether you’re in TDC or HTS mode for the pod now? There appears to be no indication on the pod mfd.

Yeah this is correct behavior I believe. At least it's how it's worked for the last 10 years.

So after the Nov 4th patch, still no Betty / Altitude warnings / AP disconnect etc I was under the impression this was reported and fixed internally?

It’s probably THE most important and useful element of the AZ/EL page. Certainly the best SA improvement of a C-Scope over the standard radar page. And we have to wait, lol. Hurry up and wait. At least we’re used to it. Looking forward to it anyway.

Yes, more BARs, less AZI available.

1) You can't undesignate a target in TWS. There's always a L&S contact bugged. In RWS however you can press RSET on OSB 19 to clear the L&S. No need to SIL on/off..... 3) The BRA indications are relative to the BULLSEYE point you set, in your case WP 0. Top left is TDC relative to bullseye, bottom centre in your aircraft pos relative to BULLS.

Very much enjoyed the latest mini-video from Wags, but there's a question regarding MSI functionality on the AZ/EL page... Should/will the AZ/EL show datalink only (Surv or pure F/F) symbols for those contacts outside the radar field of view. Obviously the normal ATTK RDR display does show MSI symbols in this condition and I would assume an important feature of the AZ/EL page is showing the relative elevation/height of a DL contact, without having to refer to the SA page. It would be a major SA boost to be able to see this. My concern is that it didn't show this behavior in Wag's video. The DL contacts disappeared when slewing RDR elevation away from the raw hits. Just curious.

The minimum release altitude for the Harpoon should be 2500ft. You get a 'ALT' inhibit warning on the HUD and Stores page if below. DCS might allow drop below this, haven't tried, but it's a cheaty and unauthentic workaround.

Yeah there's something weird going on. I've tried all combinations of PP/TOO/EFUZ ON/OFF. I've had PP working one drop, and not working next. Same for TOO, there seems to be no consistency with the EFUZ setting either. The issue appears to be related to the weapon flying too high above it's intended profile. At some point it recognizes this, and rolls over to a 60-80 degree bank in order to lose height. However, it's too late and overshoots massively and duds. I've tried different drop ranges, max and approaching min but this has little effect. This problem could alternatively be related to the final terminal maneuver they always do. The JSOW always performs a roll/jink at some point close to the target. I believe this represents the transition from INS to GPS final guidance and the roll is maybe to acquire/align with the GPS signal. Maybe somethings going wrong here, randomly, with the guidance stuck in some kind of loop. I'm still trying to capture a consistent track, but real life happens.

Exactly. This is almost certainly how it's supposed to work. The cruising portion of the flight should end at (the absolute latest) when the search distance is reached, at which point the missile should be at a much lower 'search' altitude. This would only need to be 100-200 feet to give an adequate radar horizon for it's limited seeker. When a target is found the missile should then descend to the sea skimming portion, to end in the TERM profile (remain skimming or pop). It seems that the 'search altitude' is completely ignored by ED's implementation. But common sense implies it's there or a similar mechanism to get the missile lower much further out from the target than it presently does.

Can confirm this behaviour. Sorry, I'll get a track later, but it seems that either PP mode or the EFUZ on setting will cause the JSOW to overfly/miss and dud. AGM-154A variant tested. Maybe for those experimenting try: PP/EFUZ INST PP/EFUZ/OFF TOO/EFUZ INST TOO/EFUZ OFF I've tried a few PP and EFUZ INST, they all showed odd flightplaths /dudded. However, TOO and EFUZ OFF worked correctly. Pretty sure EFUZ OFF should cause a dud. Not sure why this has gone unnoticed for 3 weeks, but there you go.

It can't be slaved to a PP. But, it can be slaved to a normal TGT point. So create a WP in the location of your targets and press WPDSG on the HSI and the TGP will slave there. No need for TOO mode.

It still works. Tried it loads. It might actually be a feature. It’s an 80’s tech weapon with a hodgepodge of components. I wouldn’t be surprised if the real weapon doesn’t use elevation, remember it needs man in the loop anyway - all the time. The cruise alt/flight profile means that a precise elevation isn’t needed. ED may be in the process of readjustment in light of the SLAM-ER coming soon.

Nobody else having problems with Link-16 with no AWACS present?