Swift.

Rapidly moving 500NM sounds like its a TDC axis noise issue. Is it similar to this bug I reported a long time ago: If you are having noise issues, then you might be seeing the TGT jump to somewhere in the HUD (hundreds of miles in front), when you look forward.

A good that I found this, I was doing some research on this matter recently. In effect for the dispenser we have (ignoring the differences between Rockeye and CBU-99 for now), there should be two fusing options: Mk339 and FMU-140. Mk339 - Mechanical Time Fuze This fuse should have to pre-set timings set on the weapon itself, as mentioned above they can be between 1.2 and 50.0 second or 1.2 and 100.0 seconds depending on the version of the fuse we have (Factory pre-set to 1.2 and 4.0 seconds for PRI and OPT respectively). Either of these two timings can be selected in the jet by the use of the Primary or Option fusing setting, these refer to the Tail arming wire (Primary) or the Nose arming wire (Option). What this timing refers to is a time from release until weapon deployment. Meaning if you drop at 20,000 with a 1.2 second setting the bomb will pop 1.2 seconds after release and if you drop from 5000ft, it will pop 1.2 seconds from release. It is regardless of the height of the weapon. FMU-140 Dispenser Proximity Fuze This fuse should have a singular pre-set Height-of-Function that can be set on the weapon itself and a singular arming delay setting. The HOF setting will be in 100s of feet, (300,400,600...3000ft), and the arming delay in seconds (1.2, 4.0, 6.0, 8.0, 10.0). Again this fuse has two arming wires, Primary and Option as above. However with this fuse the Primary mode will make the weapon deploy at the pre-set HOF, except where this height is reached before the arming delay has expired, at which point it will deploy at 300ft HOF. The Option here refers to a hard set 1.2 arming delay followed by a 20ms delay until weapon deployment. So in effect, dispenser deployment will occur: Pri = HOF set in preflight Opt = 1.22 seconds from release What do we have in DCS? Well in DCS the external model for both bomb types indicates a Mk339 fuse, there is an argument to drive the FMU-140 model, but its not enabled by default. Contrary to this, the fusing settings we have (PRI, VT) appear to be attempting to replicate the FMU-140s settings, but don't match up with the actual functionality or description of the fusings. What should we have in DCS? What we should expect is that for the Mk339 fuse to give a Primary and Secondary MFUZ option which refer to those preflighted times, because we cant preflight in DCS I propose we leave them at the 1.2 and 4.0 second defaults as per the real weapon. And then we should expect the FMU-140 fuse to offer the same Primary and Secondary MFUZ option, this time referring to the time and HOF settings as above, in DCS I propose we use the same 1500ft as we have now for the PRI and the 1.22 for the OPT as in the real world (of course ideally, we'd be able to set the HOF in the kneeboard before engine startup) TLDR The CBU-99 and Mk20 fusing we have in DCS is wrong. We should either have 2 options for time of function, or an option for time and an option for height of function.

He did say "for recoveries", the video you linked wasn't a recovery

Apologies for Necroing this, but I have a question you might be able to answer. AA Tacan on tankers, is it just yardstick (range only), or do tankers have actual beacons onboard to give bearing too?

So a mate of mine has been having a similar issue, he found using PRI fusing to be the solution. As for setting HT to 1500, you've reminded me to make a bug report about the CBU fusing options, thanks

Where are you pulling that from? CV Natops makes no such limitations on the positioning other than between 1NM and 20NM(10NM at night) of the boat and not within 150-190 relative bearing closer than 3NM and not within 340-020 relative bearing closer than 5NM. Altitudes of no higher than 400ft unless within 5NM of the port side (300ft ceiling) or within 10NM of the bow (200 ft ceiling). The exception to this is when recovering aircraft with FFO, whereby the plane guard shall not be within 5NM of the carrier from 360-090.

That looks like a classic case of Game Flight mode, have a check in the options to see if you've got that enabled.

Pinned comment

Those little crosses you see are the Uplook reticules. What the HMD does in this mode is cues the 9X seeker to one of those cross positions depending on which side you are looking. Which is why as you said, the 9X seeker LOS appears to 'blank', its actually just being replaced by those little crosses. FWIW, The University of Tennesse have a published thesis about JHMCS that includes a description of these reticules. "Combat Effectiveness of Joint Helmet Mounted Cuing System"

And conversely, at night the HMD never really goes dim enough

Have you managed to save a track so we can see whats happening?

Or even a kneeboard page if thats whats needed!

There's an entire maintenance manual about it for one. And its a feature that's acknowledged as needing to be added, by Wags.

Haha the real reason afaik, is USAF have a requirement to fuel large bombers and stuff, so they need the higher flow of the boom and the ability for the receiver to be passive. Where the navy needed something that can be used on a smaller aircraft so that it can be flown organically from the boat.

It's against common sense because the correct logic is for the tracks to go into MEM based on frame time not a fixed seconds value. So the radar should automatically be given enough time to reacquire the target in the next sweep. Right now in DCS though, this is modelled wrong.

Cruise AOA performance too!

Needles refers to ACLS, which we don't have yet. So it might just be a placeholder voice line that doesnt have any controllers behind it.

Bit of a long shot wishlist item, but it would be nice if we could have some of those lovely MC OFP 23X upgrades. eg: - Dual Altitude HUD readouts, with HAT for the Radalt when above 5000agl - Trim AOA next to the ATC symbol when in landing config

There should be a small cross shown in the HUD along the reported LOS of the HMD. During nominal operation, this cross should appear collocated with the HMDs DAC, but can be used to detect JHMCS misalignment by seeing if this cue is not aligned with the DAC. Track not supplied, not needed.

With MC OFP 19C the Bingo Caution should appear when the fuel is below bingo level, and repeat the audible 'Bingo' every 30 seconds until the bingo level is reset to below the current fuel. In DCS, it only plays the audible once. BingoCautHornet.trk

Any chance for an update beyond 'Investigating' here?

Any chance for an update on this? I figured with hornet reaching its final dev stages this might be an item that would be ready for update by now. Attached screenshot taken in latest.

I assume you are checking that against the single GBU-38, not the BRU-55 ones?

The thing I posted is only part of the line. It's more like: { CLSID = "{GBU-31}", DrawArgs = {{56, 0.5}}, other stuff about DX I can't remember},

It does not unfortunately