_SteelFalcon_

WP 0 is sadly not a thing, so you'll have to manually plug it in on the DED if the mission maker hasn't put down a waypoint at your starting position/airfield

there used to be a bug report linked in here: 
but that has apparently been removed or relocated. it's weird how currently you lose all Link info when your radar picks up a contact that was previously already marked as friend or foe.

This sounds like you have an axis bound to that HUD Brightness knob that automatically resets the brightness if you let go of the mouse button.
check the axis binds and unbind whatever is set to the ICP

aaaah it's been a while 😉 see here:
the tag is sadly misleading, since it wasnt fixed in oct 2022

same as here 
 

remember for full alignments you must confirm LAT/LONG on the INS page within the first 2 min of starting the alignment, else it wont align properly

I think that‘s the low alt warning height. Press 2 on the icp and change the ALOW value

check your slew deadzone on the RDR cursor axis, maybe it doesnt properly center and thus instantly engages ACM Slew mode.

Remember on longitude, you must add a leading 0 (e.g. E012 34 567)

Wild guess: your INS alignment is faulty.

Currently you dont need to re-boresight after rearming. Although i‘m not sure if that‘s correct.

pretty sure it's labeled as "MAN RNG Knob" in the Axis bindings.

Someone in an f-16shared a SPI over link-16. Comm switch IFF in long press

Yeah. Prebriefed threats should be some type of steerpoints. There was a post about that on the forums some time ago.
 

Sounds like it‘s an issue if local and zulu are on different dates then?

You can find the CMDS Programs in the CMDS_ALE47.lua and you tecnically could change it. but it will break IC on servers that require pure scripts
Semi and Auto cannot be changed in the cockpit on the CMDS DED page
Also: none of the SEMI/AUTO programs have Flares in them. 
The Programs for Semi and Auto are the following:
-- Auto presets
-- Threat type 1
programs[ProgramNames.AUTO_1] = {
    chaff = {
        burstQty     = 1,
        burstIntv    = 0.02,
        salvoQty    = 4,
        salvoIntv    = 1.5,
    },
    flare = {
        burstQty    = 0,
        burstIntv    = 0,
        salvoQty    = 0,
        salvoIntv    = 0,
    },
}
-- Threat type 2
programs[ProgramNames.AUTO_2] = {
    chaff = {
        burstQty     = 1,
        burstIntv    = 0.02,
        salvoQty    = 6,
        salvoIntv    = 1,
    },
    flare = {
        burstQty    = 0,
        burstIntv    = 0,
        salvoQty    = 0,
        salvoIntv    = 0,
    },
}
-- Threat type 3
programs[ProgramNames.AUTO_3] = {
    chaff = {
        burstQty     = 1,
        burstIntv    = 0.02,
        salvoQty    = 8,
        salvoIntv    = 0.5,
    },
    flare = {
        burstQty    = 0,
        burstIntv    = 0,
        salvoQty    = 0,
        salvoIntv    = 0,
    },
}

Manually enter local time using either the hack line on the time ded or you overwrite the zulu time with local time on the time ded
 
or some quick maths in your head

I tried to replicate, but it seems to work fine. hint: if targets are too close together, the missiles shot very short after eachother will blow eachother up. looks fine to me tho
AGM65D.trk AGM65H.trk

That‘s done on the SMS page, not the WPN page. Make sure you have the correct weapon selected (sms page right row of OSB buttons, 2nd from the top button i believe)

Instead of module-bound it is now in the UI Layer section and universally useable so you dont have to bind it for every plane separately

Do you even have coordinates for the selected steerpoint? does the HSI show a red flag top left?
even if you have aligned correctly (in NORM, dont forget to confirm the LAT / LONG / ELEV within the first 2 min by pressing ENT on each line in the INS page) if you dont have coords for the selected STPT, it'll show a red flag on the HSI

Rws -> bug guy 1, move cursor to guy 2, tms up on him too. Now swap primary target back and forth with tms right.
if target gets within 5 nm, guy 2 is dropped and guy 1 will be STT‘d automatically

Are your flight members within 5nm? If so, a SAM contact closer than 5nm automatically becomes an STT track

0 ft could be below ground, make sure to use the correct elevation for your steerpoint. 0ft doesnt mean AGL / „on the ground“ but 0ft MSL and thus your tgp might be looking „below the ground“ and as result it seems that the pod is off

Yeah, set RP to 6 if you drop singles, or set it to 3 if you drop pairs. Just like you would for a stick of Mk82SE
it‘s advisable to also change the impact spacing to more than the default 10 ft. But that depends on your desired effect on target