Looks like JP found the bug and squashed it.
Have done 10 successive tests without incident.
Found another bug related to CFT F-16s and working on it.

Things to consider with the AG FCR
The AG FCR scans in one BAR only in comparison to the AA FCR which can scan 4 BAR.
The AA FCR at 20nm and 1 BAR will scan a volume of airspace of 60 deg in azimuth and 10000ft in elevation. Its clear that the radar beam is quite small in elevation.
The AG FCR footprint will increase or decrease depending on the tilt angle of the antenna the altitude and the height above ground
Antenna tilt (elevation) and aircraft altitude determine the patch of ground illuminated by the beam.
The antenna tilt thumbwheel has a detent or center position that allows antenna tilt to be automatically centered at the A-G cursor position (equal to AUTO TILT) . With auto tilt, the antenna will ALWAYS tilt to bracket the cursor position.
Antenna tilt will be relative to the cursors range, and the aircrafts altitude.
The steeper the antenna tilt , the smaller the radar beam footprint .

Thanks Mav-JP.
All normal, just like JP said
The master caution illuminates because the ANTI SKID caution light was illuminated. The ANTI SKID caution light illuminates when power is applied to the brake control/antiskid assembly and goes off when power-up BIT has been successfully completed. This brief illumination of the ANTI SKID caution light may be observed when power is first applied or after the LG handle is placed down with the BRAKES channel switch in CHAN 1.

And CFT issue fixed

Ok, I’m going to make one thing clear. The following posted pictures with the fancy arrows, are not an attempt from my behalf to question your intellect. I just think that newcomers stumbling upon this thread, may benefit from the explanation, and If I come out as a smart-arse, trust me, I’m a dumb f***k, bu tat least, I’m not dumber than flat earthers.
Ok… lets begin.
The AA FCR doesn’t either display the entire picture on the MFD. Aircraft that are flying above or below you lower and upper scan limits, are not displayed.
To make things even worse, if you are flying at extremely high altitudes and are trying to detect very low flying aircraft, you radar footprint decreases dramatically when the antenna tilt angle is increased.
Looking at the YT video, the FCR is in 10 nm SP and cursors at 5nm.This means that the elevation T elevation symbol will not drift, unless the pilot pitches up or down .(assuming he has auto tilt).
I can also see l that the F-16 is flying fairly level ,and the antenna elevation is at a constant angle and slightly below 0 deg, so we don’t need to know the aircrafts altitude.
There seems to be a dark arched patch at the bottom of the FCR, but from 10nm and above, and I see clear ground mapping

I replicated it in BMS, put both screen shots together for easier comparison, and this is the result.

@Jetsun TMS AFT to remove the HANDOFF. Then you will be able to change the POS STP via the ICP.
This was added so you have the ability to pre-programm a dedicated STP for each HARM station in addition to mode,table,etc…

@gabrielwong1991 Don’t know much about the AGM-65L and why its HUD symbology differs from the D/G, but I will do my best to describe what you are seeing.
On the HUD, 235057 is your ETA (23:50:57)
Below that is you bearing (00) and range (0002).
On the TGP, the first 4 digits are you laser code (1688). The following digits are your time to go (000:24). Of course, there should be a space between them, and the laser code font size should be smaller.

@Mav-jp I bet most have noticed it,but either knew what was happening, or just ignored it.
For cockpit builders, its pure joy… They just love those lights popping on and off.

It’s a bug.
The heading tape should not change position when the DEPR switch is placed in PRI.
Two other things that come to mind.

1. The amount of depression is displayed in milliradians is a 3 digit number ( above ARM status)
   In this picture we see that the depression is zero. It should display 000 and not 0.

2. When the DEPR switch is placed in PRI, the roll indicator / DED should be blanked out.

EDIT
Disregard #2 It dose not happen

There is nothing wrong with the TGP. It is pointing to the “active” VIP sighting.(OSB 10)
Them problem is with the VIP reset initialization, and I will explain.
When the VIP sighting option is mode selected and the IP steerpoint is selected, the SOI initializes to the HUD, and the delivery mode displays VIPCRP. The FCR sighting point initializes to IP, which is added to the sighting point rotary (IP/TGT/OA1/OA2).

When the VRP sighting option is mode selected and the target steerpoint is selected, the SOI initializes to the HUD, and the delivery mode displays VRPCRP. The FCR sighting point initializes to TGT, and reference point (RP) is added at the end of the rotary.

A complete reset occurs with any change on the VIP / VRP DED page, including
data changes or mode selected status. The SOI and sighting point reinitialize, previous slews or updates are zeroed, and new slewing or updating is available.

As showcased in the following video, a reset occurs ( HUD SOI/ IP sighing selected) when VIP is not mode selected.

The reset goes haywire when VIP is mode selected, or when data changes are made while VIP is mode selected. Instead of initializing to IP, the sighting initializes to TGT.

@MaxWaldorf Check DEV B.T

@depapier Found whats happening. MSL is lower that STP elevation
Good catch.
Will investigate

@depapier You are defiantly using high drag weapons.
Could you tell me which type ?

And CFT issue fixed

Looks like JP found the bug and squashed it.
Have done 10 successive tests without incident.
Found another bug related to CFT F-16s and working on it.

Help us out a bit.
In which F-16 variant do you see this problem.
Could you guys provide a TE ?

There is nothing wrong with the TGP. It is pointing to the “active” VIP sighting.(OSB 10)
Them problem is with the VIP reset initialization, and I will explain.
When the VIP sighting option is mode selected and the IP steerpoint is selected, the SOI initializes to the HUD, and the delivery mode displays VIPCRP. The FCR sighting point initializes to IP, which is added to the sighting point rotary (IP/TGT/OA1/OA2).

When the VRP sighting option is mode selected and the target steerpoint is selected, the SOI initializes to the HUD, and the delivery mode displays VRPCRP. The FCR sighting point initializes to TGT, and reference point (RP) is added at the end of the rotary.

A complete reset occurs with any change on the VIP / VRP DED page, including
data changes or mode selected status. The SOI and sighting point reinitialize, previous slews or updates are zeroed, and new slewing or updating is available.

As showcased in the following video, a reset occurs ( HUD SOI/ IP sighing selected) when VIP is not mode selected.

The reset goes haywire when VIP is mode selected, or when data changes are made while VIP is mode selected. Instead of initializing to IP, the sighting initializes to TGT.

@javelin10 Yes. S-J Master Mode - S-J is selected/deselected using OSB 11 on any SMS MFDS page. If S-J is selected while in an override mode (DGFT/MSL OVRD), S-J will be entered
upon leaving the override mode.

S-J while WOW has been fix in U2. S-J can be accessed while WOW or LG is down, and stores can be selected. GND JETT has no influence in regards to accessing S-J or selecting stores. If GND JETT is set to enable, the HOT mnemonic will be displayed on the MFD, and stores may be jettisoned.

@jc1 It has been reported.

@jc1 Ok, you found a bug.
Auto steerpoint selection is inhibited while in AG mode ( CCRP delivery mode) as shown in my video.
In your video, you are in preplanned weapon delivery mode. Nevertheless The STP should have not incremented.