AvroLanc

My understanding is that F-pole is simply the distance between you and target aircraft at time of missile impact. For a SARH missile. Likewise A-Pole is for a ARH missile, the distance between you and target at missile pitbull. The idea of cranking is to increase the range between shooter and target at missile impact. A crank is a maneuver designed to increase your F-pole. I was a little confused when sk000tch says they're unrelated?

Agreed, the HSD is much more an SA page than HSI.

An IFF interrogation is initiated with TMS Left. You can interrogate in SCAN or LOS (Line of sight). SCAN does whole radar volume scan, LOS does a +-15 degree scan about the TDC cursor or bugged contact. The DED is similar to the UFC display boxes in the Hornet. It does many more things though and is the main data entry method in the Viper. There's Verical Scan, 20 Degree Scan, Boresight, and Slewable close combat modes. As well as a JHMCS mode. All similar to Hornet. I don't believe the HUD shows Hostile/Friendly/Unknown status - at least it never does in the 'others sim' or in any manual I've read. You find yourself constantly referencing the FCR page for IFF.

It's complicated but very very simply..... The Viper can interrogate Mode 1,2,3,C,4 and S codes. Selection of which codes to interrogate is done through a combination of a DED page options and an FCR page selection. Colour coded symbols are displayed for matching (or not) IFF responses on both the FCR page and the HSD. Generally these are green or yellow squares overlayed on the radar brick with the mode number in them. Green for matching response, yellow for a non-matching response. Of course a hostile will have no response. No HUD symbology, at least for a Block 50 AFAIK. There's no SA page on the Block 50 Viper. All IFF and Datalink info is shown on the HSD (and FCR) page.

Yep, looking forward to those additions. It's been a while since Feb. You still won't be able to pre-set MFD page setup though (unlike the Viper...one day).

But to be fair, there are HOTAS functions that can call up/swap DDI pages that are, as yet, unimplemented. This would go some way to speed up and ease page changes.

There’s been gaps of more than 2 weeks between mini updates before. As others have said, the Hornet is only 50% complete systems wise. Long way to go yet. Hopefully mini update soon. .

I'd like to choose between M56 or PGU28 rounds. Some training ball round would be good too. Similar to the F-14. Wags did say way back when that difference ammo types would be coming. Proper red tracer colour too.

Mainly to keep the pitch ladder centred in the HUD. With a strong crosswind the pitch ladder and VV will drift off to the side when HUD uncaged.

Well, I’d argue that sensible detailed wishlisting on a occasional basis serves a purpose. It serves to highlight the relative complete/incomplete status of the Hornet to those players who may have limited knowledge of Hornet systems beyond generic TGP/TWS/Radar requests.

There’s no harm in thinking out loud. Nowhere in this thread have people been impatient or demanding. It’s just enthusiasm.

+1 A mini update would be nice. I’m hoping the relative quiet is due August holidays and we’ll see progress in next few weeks. I’m optimistic that we might see a surge in Hornet items in the run up to Viper release but I may be too hopeful. Items for me: Long mentioned full INS and GPS enhancements. Full alignment, HSI options etc JDAM improvements. In Zone stuff, LP, AUTO LFT, FLT time , TOT etc TWS and finish RWS....complete RWS long overdue MIDS page, MIDS voice channels TGP symbology, slaving functions Simple missing HOTAS functions

The JHMCS options page has blanking options for closest members and TUC. I believe it shows at least wingmen positions and a datalink track of interest?

I believe, from memory, for SW the Boresight option is there only to force the seeker back to boresight once uncaged and tracking a target. So try with an uncaged SW. Opening the ACM cover will override and force to boresight in any case.

Pre Hornet it worked like a standard Paveway II. (I think). Eventually it will get a proper treatment so that it models more realistic Paveway III guidance at some point. Basically it's just a placeholder for now.

Interestingly I’m having exact same issue with rockets in the FC3 SU-27. Maybe not Viggen specific.

I appreciate Harpoon is WIP, but I think there's conflict in the current implementation between FLT altitude and the possible 'Search' Altitude. Currently the missile will fly out at HIGH, MED or LOW. It will then enable it's radar and search according to the 'SRCH distance. The radar seeker seems to have a range of 10nm from my observations. Upon target detection, the missile will attempt to descend down to a sea skimming approach.... and if FLT is set to MED or HIGH, will miss due to being far too high at the 10nm seeker activation point. A 30000ft (or even 15000ft) FLT alt is far too high if the seeker range is 10nm. Common sense would suggest Harpoon should decend to a lower altitude upon reaching the SEARCH range setting. If a 10nm seeker is used, a radar horizon of 10nm could be achieved with a height of just over 66ft...... This would generate a much more sensible (realistic?) 3 phase profile. FLT alt, Seach alt, and Terminal alt.

Only partially wish list... I was actually being complementary, most of the above seems to be in.

While clearly WIP, I've been having fun with the Harpoon. I've been surprised to discover that the 9 or so Out of Zone Conditions have been modeled pretty well already. These are the cues you get in the HUD and Stores DDI to advise of problems with launch parameters / geometry. They are not detailed at all in the early access guide. Nor did Wags mention them. Some might find this useful: ALT - Aircraft altitude is less than the recommended absolute minimum launch altitude. This is 2500 ft AGL. OFF AXIS - The bearing to the target, search area, or Harpoon turnpoint is greater than 90°. HPTP ANG - The total turn angle at the Harpoon turnpoint is too large. A/C HPTP - The aircraft is too close to the Harpoon turnpoint. TGT/HPTP - The Harpoon turnpoint is too close to the search area/target. SCH/DSTR - The distance between the entered search and destruct range is too small (BOL mode only). DSTR RNG - The destruct range is greater than Rmax (BOL mode only). INV TGT - The total distance to the target is greater than 172 nm, which is invalid (R/BL Mode only). INV SRCH - The total search range is greater than 105 nm which is invalid (BOL Mode only). They seem to indicate as intended. However I've not been able to generate a INV SRCH caution yet. Seems to be not working. What is the max range of the AGM-84D as modeled in DCS? Also, I'm pretty sure a pickle hold of a few seconds in needed, rather than the instant release we have at the moment. (The same applies to JDAMs, but again not correct yet).

Yeah I suspect this is correct behaviour. You could hardly expect the missile to climb to 30000ft from, in theory 2500ft min launch altitude, and still have fuel / energy remaining.

Come on, seriously? The command heading bug should be wind corrected. Period. Any ounce of aviation common sense / aircraft familiarity makes this obvious. The current implementation flies you on a track downwind of the intended path, clearly illustrated by the OP. Not sure why this is in Wishlist and not BUGs.

Haha, just when I’d got over this issue! Microprose probably we’re using similar reference material? This argument did occur to me months ago. I think we just have to go with HB now on this.

Never installed/cleared/used in service.

Reported. Not fixed yet. https://forums.eagle.ru/showthread.php?t=244803

First digit always 1 Second digit 5,6, or 7 Third and forth anything between 1 and 8