Frederf

You gotta calibrate the LOSs between that launchers and TGP.
Point track an object with TGP and missile manually and press the "BSGT" button on the WPN format to save the calibration. Repeat for all stations with missiles.
Hot start airplanes simulate that the pilot has already done this for you before you took control.

None. With a two engine airplane the remaining engine has some utility. With one engine the crash takes care of the fire.

When closure positive switches to closure negative inside 2nm polar distance from steerpoint and master mode is not AG and automatic steerpoint sequencing is enabled then the steerpoint will automatically sequence. Inhibiting sequencing in AG master mode prevents undesired changing during air to ground attacks.
 
To enable sequencing use the DCS control right to SEQ when on the DED STPT page. The function works but what is missing is the capital "A" after the steerpoint number on the CNI DED page showing the feature is enabled.

The CZ function is present on AG TGP and AG FCR pages (even when off, but that's currently missing). If you can find the CZ button and click it I've never had it not do what it's supposed to.
The way you diagnose CZ is by doing small slews and pressing CZ. If it keeps putting the FCR cursors back in the same spot then there's nothing wrong with CZ. Either your spot's wrong or your INS is. If each CZ press acts like nothing happened and the slews pile on top of each other that's a problem with CZ.

With TWS cursor snap to system track antenna elevation is automatic. Without TWS cursor snap to system track antenna elevation is manual. I think if an AIM-120 is in flight that also counts as a "priority target" which will also do automatic elevation.
I thought it was bug as well for auto/man antenna control decision but if you cursor snap to a system track (no bug) it'll auto center elevation on that. However if a system track is present and the FCR cursors are not snapped then you have manual antenna elevation (unless an AIM-120 needs to include a particular target).

Direct Targeting Optical Sight. Dive toss. It's really, really, really similar to "EO VIS" mode of the Maverick. I would say that EO VIS is really "DTOS for Maverick" but same difference. If you've ever used the TDC in the A-10C and then attacked CCRP, similar to that too but more streamlined. There's a box that starts on the FPM, you can slew it first, designate it on the ground with TMS forward or weapon release, can slew it on the ground after if you want, and it's CCRP type aiming through the rest of the attack. In the visual/preplanned split it counts as visual (FCR will be AGR).
It can be handy to toss with, especially CBUs but it's just a sort of "visually-designated CCRP". CCIP can do that too with the delay cue stuff but you'd have to fly the pipper on where with DTOS you have a bit more flexibility putting the box places with the cursor switch.

"TMS up to create a SPI" This is wrong thinking. SPI was at radar cursors the same as before or after designation. Since there is no actual FTT implemented yet it's of no use to designate the GM/SEA radar modes. Just slew the cursors over the target and use that. Don't TMS forward in most cases. It's unnecessary in most situation and can only cause problems.

The maximum possible number of Maverick to launch with one WR press is two. They both must be tracking simultaneously from paired stations (e.g. 3/7) and "RP 2" must be selected. Due to an issue this currently isn't possible if LAU-88 or EO VIS or EO BORE is used.
AG master mode SMS OSB 2 (x2) "PRE" SMS OSB 8 then OSB 19 then OSB 2 "RP 2" DMS down WPN SOI Refine crosshairs on first target and TMS forward to track MSL STEP Refine crosshairs on second target and TMS forward to track MSL STEP to confirm both missiles are within firing parameters (optional) Weapons release button hold until both missiles fire (short delay) F16 EO RP2.trk
You could use two points to designate two targets. For example if STPT 1 has first target then simply TMS forward to track first missile and INC to STPT 2 and TMS forward to track second missile. You're allowed to change the target point in the middle of the process. Here's an example of two steerpoints which are near two targets with a steerpoint change in the middle.
F16 EO RP2 STPT.trk

TMS right (short) only steps between system tracks. By default all tracks are tank tracks (not system). To be steppable/snappable they have to be elevated. Elevation can happen by cursor and TMS up (no bug) or if there are zero system tracks by TMS right (elevates up to 10). Un-elevation is by TMS down (no bug).
It's really hard to tell what's going on with the Link 16 layer on top which is why it's a good idea to learn how it work with MIDS switched off. Here's a track showing manipulations of the TWS radar and elevating/un-elevating/stepping tracks by TMS up/right/down.
F16 TWS step.trk

In general AG missiles have two methods of jettison:
Unguided launch of the missile from the rail Jettison of rack which holds launcher rail On SJ SMS page often you can cycle through multiple modes of jettison for a station. Just keep pressing the OSB and different things will highlight. For example Mk82 on TER you can jettison a bomb from TER or you can jettison TER from airplane. Here is a track showing jettison ofHARM by unguided launch, then LAU-118+HARM, then LAU-118 alone. The choice is up to the pilot.
It's not possible to drop a missile off a rail. They can only slide off the rail in a forward direction. When loading the prongs on top of the missile are loaded by sliding it backward on a rail and then a pin locks it in place so it doesn't fall off. During launch the rocket motor breaks the pin and the missile slides forward again.
Master arm switch is for a weapon to be armed with its targeting electronics operating and fuze ready. Stuff can still come off the airplane with master arm in safe position: chaff, flares, jettisoned fuel tanks, jettisoned stores, etc. A missile is relatively safe when fired unarmed. Obviously if it hits you it would hurt but the warhead doesn't do the same thing hitting the ground unarmed compared with armed.
F-16 HARM jett options.trk

There are two course settings for ILS, the HSI one and the DED one, and they're fully independent. For some reason in DCS they are acting semi-connected. Anyway, you've set course 091°. It's more like 079°. You can't trust the ruler or the ME label as those are in true/ruler direction and not magnetic.

Automatic control of radar power for LPI purposes

ILS command steering cue, the mode when the airplane hasn't captured the glideslope from below and is getting lateral guidance.

Double undesignate enters both VVSL and then again to enter a mode that doesn't have an explicit name. It's "OPR" but a stabilized vector at infinite distance. I'm going to call the FLIR states: slaved, INR/direction, INR/point, SCENE, and AUTO. What you're calling "snowplow" I'm referring to as INR/direction. I'm going to use sensor control switch (SCS) to mean castle.
 
From slaved (WPDSG) state you have three options to have a slewable FLIR picture
With FLIR selected, TDC depress to command a new FLIR target designation. It will be essentially at the previous slaved waypoint since FLIR LOS was already pointed at it. Mode will switch from slaved to INR/point. With or without FLIR selected, undesignate x2 to enter INR/direction. FLIR will drift off waypoint since FLIR is fixed in direction. Slewing (with FLIR diamond'd) is then possible in this INR/direction state. With FLIR selected, SCS right for SCENE. The reason that the FLIR LOS returns to the waypoint when you use option #3 and cycle through the modes is because the target designation has not been changed and FLIR is still slaved to the waypoint-target in the blank-labeled slaved-to-target mode. As long as you TDC depress while in SCENE or AUTO (or INR) before you SCS right rotary back to the slaved-to-waypoint mode then FLIR will remain as you rotary through the INR/SCENE/AUTO modes.
 
So try the following:
WPDSG SCS right once (or twice) to scene (or auto) slew TDC depress slew SCS right twice (or once) to return to blank/INR Omitting the step "TDC depress" has behavior that advancing past AUTO in the rotary selection will cause the FLIR to resume the slaved-to-target-waypoint behavior.

TGP for AA missile employment is the sort of thing that gets updated frequently over the lifespan of F-16. A 1985, 1995, 2005, 2015 airplane are going to have significant differences in capability.
 
Let's look at what are the theoretical sources for missile cueing for the AIM-9 and AIM-120 respectively. Those options are:
Nothing (boresight) Radar TGP Helmet cue Datalink As of M2 tape it's been possible to slave AIM-9 to TGP LOS. The TGP may track an AA target independent of the FCR. A dotted TLL is shown on the HUD. Laser rangefinding to AA target is possible. AIM-9 will be slaved to TGP LOS automatically if TGP is tracking and SOI (thus priority over FCR) and AIM-9 is set to SLAVE (not BORE) on SMS. While TGP is not tracking the missile is slaved to boresight. With FCR ACM and TGP AA tracking TMS right commands FCR to track along TGP LOS (instead of normal 30x20 pattern) provided SOI is either FCR or TGP. Correlation of missile and aiming sensor (radar, optical) and caged status is indicated by TLL display on the HUD. This allows prosecuting TGP tracked AA targets with AIM-9 which are off HUD. Since there's no range when using TGP cueing the HUD DLZ and flashing "shoot" diamond are not shown. I don't think they come back if laser rangefinding is provided (since only range, no closure info?).
 
TGP-cued AIM-9 attack is absolutely a thing either without or in concert with FCR. I don't know about AIM-120. In general AIM-120 won't let you initiate a launch without good data (no coast/notch) although it will let you continue a launch which has lost those requirements. Maddog I don't believe if every cued in any direction except BORE straight ahead. Maybe helmet can cue the boresight direction similar to AIM-9. I don't know. TGP AIM-120 engagement I don't believe is a thing except by cueing ACM FCR with TGP LOS and then attacking as normal, same HMCS.

Here's a less than 10 minute track of a ramp start, boresight, and attack with two Maverick against two targets.
F16 Maverick Boresight and RP2 Attack.trk

Scorpion is a Thales (acquired from Gentex,  Visionix division; also Raytheon was join with Gentex) product which fulfilled the HMIT military program requirement. It is a HGU-55 (in A-10) helmet fitted color monocular device. The Thales change of owner changed the magnetic to an optical-inertial tracking system.
 
JHMCS is an Elbit Systems/Rockwell Collins (collaboration division Rockwell Collins ESA Vision Systems LLC) product. It is derivative of DASH III and Kaiser Agile Eye by VSI. Unlike Scorpion it's not monocular and requires modification to the HGU-55 helmet. Instead of being merely compatible with also wearing NVDs the JHMCS replaces NVD function as an internal capability.
 
Scorpion is better than JHMCS especially for AG. JHMCS's big deal was AIM-9X integration. It's older.

"Lock" is a funny word when it comes to radar. I don't know if there is an agreed upon definition of what is and is not a lock in the F-16. I would recommend using the more common terms like "track "bug" "STT" and similar. Unless there is functionality I'm unaware of, it's not possible to bug any contacts which are known exclusively to the datalink. To bug any contact (i.e. make it target of interest) the radar must have contact with the target.
 
Due to the display of the FCR it can be confusing or even impossible to know what state the contact object is in and how to proceed. Here is what a single IL-76 looks like with MIDS on and TWS but the radar is aimed (or too far) so that it does not see the contact.
L16 contact without radar detection is hollow.
Radar aimed down to see target and at first a contact is displayed near L16 object because not enough information is available to make a track file.
After a few scans the target becomes a track file. At the same time it is correlated with the L16 track becoming a filled triangle.
Turning MIDS off to see radar without L16. It's a non-steppable/non-snappable tank track*. Normally L16 remains on but this shows what's happening better.
With cursors over track TMS forward the first time. Azimuth narrows to "A2" and cursors snap to object. Track is "system type"*.
TMS forward a second time. Now you can see the track is bugged by the circle around it.
TMS forward a third time. This commands STT which is signaled by the cursors and all other tracks disappearing.
 
Now I will do the exact same process again but leaving L16 on.
 
Radar can't see L16 track
Radar contact next to L16 track
Radar makes track, correlates with L16 track
MIDS remains on.
TMS forward once, cursor snaps to target, azimuth narrows "A2"
TMS forward second time. Target is bugged.
TMS forward third time. Target is STT.
 
*Since the last time I looked tracks were shown (with MIDS off) as solid for tank-type and hollow for system-type. That is no longer the case. Currently tank-type and system-type look identical. The difference is that tank-type cannot have cursors snapped to them nor will they appear in the TMS right short rotary stepping through tracks.
 
The radar should be understood fully without L16 first. The addition of L16 information is very confusing because sometimes it correlates with radar data and sometimes not.