Swift.

As I recall the uplook reticules are a different projector. Which is why they never change shape or size. Only turn on or off.

There are different effects at play here. What ED have done is a CFAR. What everyone else seems to be talking about is sidelobe ground returns.
The former is why you see false alarms whilst 'high'. And the latter is what you see in that video and what is obvious in razbams modelling.
 
What ED have done is 'accurate', but just incomplete. Once we get sidelobes modelled, we should start to see more like what you all seem to be expecting.

With JDAM, you have to remember that Absolute targeting and Relative targeting are a thing.
Absolute being what you describe where you program known coordinates into the bomb and it will fly to those exact coordinates as best it can (ie using the alignment transfer from the jet until it can get its own GPS fix, where it will correct any offset).
Relative is what we have in DCS, where you use an aircraft sensor to generate coordinates to feed the bomb. The bomb will then in effect fly to that location (relative to the aircraft, hence the name). And wont correct any offset at GPS, but will maintain it (ie not allowing any more drift).
 
They are both 'correct' and both have their uses. We are just missing the Absolute mode from DCS currently, so we experience the pain of having the INS errors carrying over the alignment transfer and causing issues on preplanned coordinates.
 
In viper the mechanization should be Relative when CZ is shown (ie cursor slew has been applied), and Absolute when CZ is removed (ie no cursor slew).

That seems quite low for this type of munition. Have you tried pushing it to the upper extreme just ot check function? ie does 3000ft burst height work?
It's possible the weapon is functioning too low for the vertical velocity it has, and the skeets are hitting the ground before they can deploy.

I don't have access to a PC to check the track currently, but are you selecting STO before the radar is taken to AA mode?

Its not new, but it will be how you set up the HMD. Have a fiddle around, some of the functions are already working.

It looks like the default TEDAC viewport is now called 'TEDAC'. So we don't need to mod one in anymore. You will however notice the same issue with this export as with all exports: it's hopelessly dim.

Would you be able to check you don't have force feedback enabled. It's under misc or general settings iirc.

Correct, it can't do VHF or UHF homing.

They come under
Symbology Select Switch 
both forward aft and depress.

Just double checking, you are putting the master switch forwards right? I can imagine DCS might default it to rear for night time and forward for day time.

Because you landed. 

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 wasnt a yes no question, it was an either or.
I can see that the fuel bit has been initiated by the Boxed FLBIT on the fuel DDI page. 
Activation of this BIT will cause a master caution and FUEL LO warning to appear on the Left DDI within 13 seconds, these cautions will remain for at least 1 minute and will be removed as the BIT concludes with the FLBIT automatically being unboxed.
If you are certain that you aren't activating the FLBIT manually, then it might be a double click issue as the FLBIT pushbutton is the same as the pushbutton to enter the FUEL page

The real hornet cant mount single LAU-127s directly to the pylon. The way it is now, where the LAU-127 mounts onto a LAU-115 and then onto the pylon, is correct.

I see that Game Avionics mode is still selected. Try deselecting that

Thats the whole MSI thing that hornet has, its there for general SA.