Muchocracker

Directly from the manual bro. The fuses not being armed at all combined with you flying at 400 feet it's triggering the DUD cue and the breakaway cross.

In fact you don't even have a designation created in the system at all at any point in this track.

the large cross on the HUD is bomb dud cues, appears when the bomb is computed to impact the ground before the fuse is armed. It has nothing to do with creating or deleting a waypoint designation.

Can't play the track because whatever map it is i don't have it currently installed. But it sounds like you're hitting the CAGE/UNCAGE and setting the amraam to VISUAL mode.

segmented ring does not appear at all when i watch the track. It only shows the cross.

you need to have the DL-13 datalink pod loaded on a station.

Idk what kind of "half" state you've got the jet in but it shouldn't even be allowing a designation to happen from the helmet if there is no sugmented ring in the HMD (which denotes that the system is in A2G master mode and that the helmet is selected as SOI). There is something else going on here that i'm not able to re-produce on my own, but in your track all it takes is recycling the master mode or recycling your SOI out and back to the helmet to get it working properly again.

It needs to be a short track please, not a full mission.

Disable that DDI mod, it broke with the latest patch

Not really. In reality they're both handled independently by 2 different systems. The radar does its own trackfile processing(contributing to MSI) as well as the 120 d/l functions. The mission computer handles the MSI and all the other avionics related systems. The whole thing's architecture would need to suppport this kind of cross "commanding" of actions for lack of better term.

Not relevant. The current state of both the weapon and the f-18 module in DCS is as i've described above. and FYI, you are violating forum rules for posting documents. That one especially is marked secret (literally in bold letters on the top of the page). Delete it

the F-16's INS overhaul hasnt been moved over, so the relative vs absolute targetting modelling isn't relevant to the hornet yet. The JDAM should always be hitting to the spec'd 5 meter CEP. If There is excessive missing it's either caused by aircraft INS error (from not having GPS or not turning on IFA) or error in the coordinates being handed off to it. To diagnose why there is a disparity in these images you'll need to post the trackfile.

DLY2 has no function, it's not suppose to be there. Just ignore it.

The pitch bobble that happens on deploying and retracting is proper and intended. It's a noted behavior in the NATOPS

Just like any other inertial aided munition

It does not program the bombs, it programs the station. You have to swap between the PP#/TOO# for every weapon dropped. I highly encourge pulling up the hornet chucks guide on google. It gives you step by steps for a lot of systems.

Gonna have to be more descriptive than that. JPF page works with the FMU-152 and JDAM's.

You're in pre-planned mode buddy. The bomb has to be manually programmed with lat-long information. The weapon will be on standby otherwise.

It's not about any of that. It's just whether they programmed the MC and radar data processor to be able to transmit uplinks independently of the trackfiles created by the radar or when there are none at all.

100%. Pre-L&Sing targets out of the radar FoV during out's and recommits would be very helpful

There's plenty of literature out there in radar and Electronic Warfare theory textbooks to do "first principle" approaches for many of the EA and EP techniques, they're not hard to find. You can do many of the deception jamming modes like Barrage, Spot, Cover Pulse, RG/VGPO, Range and Range/Doppler MFT, Inverse Gain, and AGC Capture without getting too close to the sun on classified material. The challenge is you need to completely overhaul the radar modelling to truly simulate most of these. ED is on the way there, but it's still a long way to go.

It could work in theory but i don't think this has ever been proven. It would be dependent on whether the mission computer is sophisticated enough to command the radar to send uplink transmissions independent of the radar trackfiles.

You have to install the FMU-140 fuse to get the RadAlt height of burst function. This is not a bug

As i already explained before. It's terrain/object avoidance. To make sure it has a clear flight path to the intended target and not hit something on the way down.

If you dont post tracks nobody can diagonose