Northstar98

Not sure what's going on here, as I'm unable to reproduce in my own missions
However, there are a couple of things I'll mention:
I ran into issues using attack unit/group with ARMs a few updates back, it seems that if the radar is not able to be engaged immediately upon activation of the task (for instance, if it isn't illuminating you) the AI will drop it. It's better then to use the SEAD task or the search then engage tasks, as the AI will constantly evaluate these and won't drop the task unless it reaches a stop condition (which you have to define yourself) or until it runs out of waypoints. This can be somewhat inconsistent though - I've seen identical missions sometimes work and sometimes not when testing this today. The EWRs you're trying to engage are 55G6s, these radars cannot be engaged by the HARM, as the HARM's minimum frequency is greater than the frequency they operate at (or put another way, their wavelength is above the maximum that can be received by the HARM). The limitation comes from the fact that, because the HARM's diameter is fairly small, the conical spiral antenna the HARM has isn't large enough to receive such long wavelengths. I've attached some tracks below showing AI SEAD/DEAD aircraft launching ARMs (to get the mission file, simply make a copy and change the extension to .miz instead of .trk).
AGM-45A_S-125M_AttackGroup.trk AGM-45A_S-125M_SearchThenEngage.trk AGM-88_S-125M_AttackGroup.trk AGM-88_S-125M_SearchThenEngage.trk ALARM_S-125M_AttackGroup.trk ALARM_S-125M_SearchThenEngage.trk

To me this looks like a minimum range problem - it's being employed outside of its envelope for the profile it has.
The missile first performs a lofted trajectory, then assumes level cruise flight and then descends for the terminal phase upon acquiring the target. Because the target is close you're not allowing the missile to transition between the phases - it's being forced to perform an aggressive dive before it can even finish the initial lofted trajectory.
Simply increasing the target distance to 5 nmi has the missile hitting the target 4/4 times, though ideally, it should be even further away to allow the missile to assume its level cruise flight and terminal phase (and the HY-2 has a maximum range on the order of 50 nautical miles).
Now, it might be that the Seersucker (which, FWIW, is what the HY-2 missile's NATO reporting name actually is) has a mode that results in a shallow trajectory, meaning it doesn't have to perform such an aggressive dive to hit a close target, but right now only one profile is available.
There doesn't seem to be much in the way of real launch footage, but so far, the initial loft seems correct as-is (though obviously I can't determine altitude accurately from just video).
HY-2_10nmi.trk HY-2_5nmi.trk

To get a submarine to engage a surface ship, you might need to use attack unit/group - I've attached a track below and the Santa Fe does indeed engage with torpedoes (though why they are Yu-6 torpedoes I don't know - the Santa Fe would've had Mk 14 and Mk 37 Mod 3 torpedoes) - see Santa_Fe_attackgroup.trk.
I've only ever seen submarines engage targets of opportunity when at periscope depth. Unfortunately, the Santa Fe isn't configured for this, but the other submarines are (see the Type_93_opportunity.trk below).
As for ships not engaging submerged submarines, there are no ASW sensors and there are no ASW weapons in DCS so that explains that. I've only seen ships only fire anti-surface weaponry against submarines that are either on the surface or have deployed their periscope (see TypeVIIC_attack.trk for an example of the latter). If the latter, the AI appears to be reliant on visual detection.
Santa_Fe_attackgroup.trk TypeVIIC_attack.trk Type_93_opportunity.trk

The problem there might be that it impose ground clearance problems if placed on an adapter. Again, it's not a configuration listed in either of the -1s I have (unlike the AN/ALQ-71/72/87/101, which is explicitly mentioned as being able to be mixed, the 119, 131 and 184 are only listed by themselves). That doesn't necessarily mean it's not a possible configuration, it just means that it's a configuration that isn't explicitly mentioned.

Yep, absolutely agreed, they would go a very long way to fleshing out scenarios.
For carrier aviation, the A-6E and KA-6D Intruder is supposed to be coming by HB. That largely just leaves a more appropriate E-2C (Group 0 for Forrestal, a 2000 for the Supercarrier) and the EA-6B Prowler (there is a mod, but ideally we'd get one as a core unit of similar quality to other AI units).
There's definitely quite a bit missing for the Kola Peninsula map - Tu-16 is a prominent one (K-10/K-10-26/K-26P/RM-1/P) as is the Il-38. I definitely wouldn't say no to a Su-15TM.
I'd definitely go for more variants of the MiG-23 - the M, MF and MS would probably be my top picks and are probably the most relevant versions for DCS. Same for the MiG-21 - the F-13 and PFM would be my picks.
For the F-111, I'd rather go with F-111Es and Fs (if not both, preferably the latter) circa Operation El Dorado Canyon (which would also fit well for ODS and late Cold War gone hot).
I would also mention the B-52G and/or a pre-1991 B-52H (i.e. with the tail gun).
We have the SA-3, we don't have an SA-4 however (and that, alongside the SA-7 are really the only relevant single-digit systems entirely missing from DCS).
I think something that would be worth mentioning are EWRs and completing battery components for current SAMs. For the former, I'm mostly talking about things like the P-37 (for which a model already exists in the game files and has done for over a decade now), the P-80 and the 5N84A. The SA-2 is missing the P-12M/P-18, the SA-5 is missing the 5N84A.
For Cold War tanks (centering on the late Cold War, as this is where most of our Cold War assets are centered around, and my particular favourite 😛) :
Challenger Mk. 2/3 Chieftain Mk. 10 Leopard 1A1Ax M1/M1IP Abrams T-62 T-64B/BV T-72M/M1 T-80B/BV Would be my picks.
For Cold War ships... Dear me, there's so many, where to start?
DD 963 (Spruance) - any configuration as long as it has Mk 15 Phalanx Block 0 and RGM-84 Harpoon (be it Mk 112, Mk 112 + ABL or Mk 41 VLS - the latter is probably more applicable to DCS, considering we don't have ASW) DDG 2 (Charles F. Adams) or DDG 40 (Coontz) CGN-38 (Virginia) or GC 47 Baseline 0/1 (Ticonderoga) Oslo FFG BPK Pr. 1143A Berkut [Kresta II CG] EM Pr. 956 Sarych [Sovremenny DDG] Would probably be my top picks, though far from an exhaustive list.

You can edit the programs on the CMDS page on the DED; accessed by hitting LIST on the ICP and then 7 (I think).
 
Alternatively, you can go into your DCS main installation folder go to Mods -> aircraft -> F-16C -> Cockpit -> Scripts -> EWS -> CMDS -> device and then editing the CMDS_ALE47.lua file (which you can then save onto your user area, as everytime DCS updates or repairs, this file will be overwritten with the default).
 
From there you can edit all default programs, including the automatic ones (Semiautomatic and Automatic countermeasure dispense isn't implemented for the F-16C (yet)).

Interesting - I'm not seeing the same:

The missiles in your screenshot also appears to be of the older 5V55R model, I've got the newer one on my end.

The altitude setting determines the altitude of the fire-at-point aiming point. If you're trying to engage a target on the ground, you should leave the altitude at 0. If you add altitude, you'll find that whatever unit is doing the firing will be aiming high to hit the aim point, which will be up in the air.
This altitude setting is more intended for setting up AAA barrage fire. Of course if you have it set to MSL and then have the altitude equal to that of your target you'll get the same result as having the setting off (i.e AGL altitude of 0).
It might be useful for attacking structures that are significantly tall enough though. For instance, when attacking bridges, I've found that I sometimes end up hitting the ground directly below the bridge and not the deck of the bridge itself - adding some altitude can be used to raise the aimpoint up to the height of the deck resulting in much more hits onto it. Similar things for buildings - if you wanted to hit a building high-up for whatever reason (perhaps to hit a certain floor as opposed to ground level) it can be used to do that.
Last I checked it was the total number of rounds to be fired by a group as set in a mission editor. It doesn't matter how large the group is, they will (or rather should) stop firing once the total number of rounds reaches what's set in the settings. If you want to have a certain number of rounds fired per gun, your best option is to take the number you want and multiply it by the number of guns you have in your group.

Only thing I'll say is not all Ropucha Is have the MS-73 Grad-M system fitted, out of 25 Ropucha Is, only 6 have the MLRS system (and all are the Pr. 775/II subvariant), at least according to this.

What I would do is make a trigger that turns a flag on once you're airborne or are on approach (personally I would choose the latter). Then for your welcome trigger zone I would add the condition "flag is true" set to the flag you set to come on once you were airborne/on approach.
The easier way (though perhaps a less desireable way) is to add a "time more" condition to the trigger that activates your welcome transmission. Set it to a time between after you expect to have taken off and before you land (note that the time more condition uses seconds for the time, so you'll need to enter 60 for a minute and 3600 for an hour). This way the "time more" condition should only be true after you've taken off but before you've landed. This one doesn't offer much in the way of flexibility however (if you arrive before the set time, the trigger won't activate and if you depart later than the set time the trigger will activate before you've landed).

It's part of the Halloween Easter Eggs (it also adds a green tint to any bloom) it should be back to normal by tomorrow.

There is a no-clouds option in the mission editor.

Not exactly.
The Sparrow is a semi-active homing missile - what happens is that your radar illuminates the target and the Sparrow tracks the reflection. Think of it kinda like a cat chasing a laser spot - the laser (radar) emits radiation (which will be visible light for the laser and microwaves for our radars) which reflects off of the target and into the cat's eyes.
As Dragon1-1 said, countermeasures are just probability. Each missile has a coefficient that determines how likely it is be decoyed or not.
I believe the coefficients can be found under ccm_k0 = x in the respective .luas of the missiles (can be found here).
Here are the ccm_k0 values for all Sparrows in DCS:
AIM-7E: 2 AIM-7F: 1 AIM-7M: 0.5 AIM-7M(H): 0.5 AIM-7P Block I (II, as per hoggit?): 0.5

There are keybinds to translate your head.
EDIT: To be more useful, you're looking for:
Cockpit Camera Move Back: RCtrl + RShift + Num/ /Num- Cockpit Camera Move Center: RCtrl + RShift + Num5 Cockpit Camera Move Down: RCtrl + RShift + Num2 Cockpit Camera Move Forward: RCtrl + RShift + Num* Cockpit Camera Move Left: RCtrl + RShift + Num4 Cockpit Camera Move Right: RCtrl + RShift + Num6 Cockpit Camera Move Up: RCtrl + RShift + Num8 All found within the "View Cockpit" category.
Or alternatively, when in mouse look you can use the "Camera transpose mode (press and hold)" keybind (usually set to your middle mouse button) which allows you to do it with the mouse.

You need to make sure that the SEC caution light extinguishes before advancing to idle. In your start 2 track, you advanced to idle before the SEC caution light extinguished.
What I do is instead of advancing to idle at 20%, I wait until the SEC caution light extinguishes and only once RPM has stabilised (at about 25%) advance to idle, it takes a little bit longer (maybe 15 seconds, if that), but you shouldn't run into any issues with hung starts.
F-16CM_START_2.trk

The last 'major' change (EDIT: it was at least more substantial than other changelogs for the Supercarrier) to the Supercarrier was in the June 16th 2021 update (2.7.2.7910.1):
The last time the Supercarrier was even mentioned in the changelog was the August 11th 2021 update (2.7.5.10869), which included a few fixes:

Glad it went okay.
But if this crops up again, if you look down at the bottom of the mission editor, you'll see a small icon that looks like a stopwatch, what it does is it turns on/off historical mode (if you see a date in the top-right of the screen, in the unit selection window, it's on).
What it does is it filters units and weapons to only include those that were in service for the date of your mission.
I'm unsure if it differentiates between different operators, but I do know that some stuff isn't included, and it isn't always precise for whatever variant.

It was supposed to be 2002 IIRC. It might have some other stuff that is later, but even accounting for that, it still predates APKWS by a significant amount of time.
 
 
AFAIK, the new A-10C is ~2017, so Scorpion HMCS, APKWS and GBU-54 are all perfectly accurate. The older A-10C probably best fits circa 2005 AFAIK, which is why it doesn't have those systems.
 
 
Yeah, 2007/2008.

I might be wrong, but I think the new security system is tied to your account, so as long as you're signed into a machine with your account, you should be able to install the modules, no problem.
They might have a check to make sure that 2 machines aren't running your account at the same time, but you should be able to install on both, you just have to make sure you're only signed in on one at a time - at least that's how I think it works.