Ironhand

Your assumption is correct. There is only a single dial in the cockpit controlling radar elevation. IIRC, it is discrete (like the keyboard control) rather than continuous. EDIT: (from the real world manual):

That’s weird. Works every time for me without any issues. What happens if you place a static object and use F12?

Probably the easiest way is to use F7 to bring us one of the ground units. The LCtrl+F11 to set the free moving camera and position it where you want.

Why don’t you post the mission so that we can take a look at it? Otherwise it’s a guessing game.

It’s on your C drive (regardless of where DCS is installed) under your user name. In saved games you’ll see a DCS folder. In there will be a bunch of folders one of which will be “Missions”. EDIT: If memory serves, in Windows File Explorer, go to: C:\users\(your user name)\AppData\Local\Saved Games

Open the mission in the Mission Editor and check the season. If it’s a winter month, then all is well. If a summer month, there’s an issue.

Revised your mission to a two-ship and made a larger single group (rather than two smaller groups) for them to attack. Then added that they attack as a group, and it worked like a charm. Revised mission attached. B-52H_attack group-Revised.miz

Obviously not a tutorial but here's a working sample. Depending on the area you're trying to cover, though, it might be best to use single aircraft rather than a group, if you need tight coverage. B-52 Bombing.miz

I believe the “carpet bombing” WP was too close to the target. I’ve forgotten the exact distances involved but that’s often the sort of behavior you see with that issue.

Just curious. Where are you getting the Mach number from? Neither the Su-25 nor the Su-25T has a Mach meter. If I start at 20,000 ft in either the Su-25T or the Su-27 with the Mach set to 0.8 in the ME, I get identical TAS numbers. Mach Test.miz

Excellent! On all counts.

Obviously, that “required module” statement doesn’t belong in the mission file. You can remove the requirement yourself, if you’d like: 1) Navigate to the folder containing that mission and make a just-in-case-I-screw-this-up backup of the mission. 2) MIZ files are ZIP files. Unzip it. Open the “mission” file contained inside with NotePad++. 3) One of the first sections you’ll see is the “required files” section. Delete what’s inside that section and save. 4) Reassemble the ZIP file, changing the suffix to MIZ if necessary. 5) Fly.

Resets the elapsed time clock?

Later.

Scan Zone Up/Scan Zone Down

So you edited one of the current presets and got the issue? Which preset?

Ahhh. That would be the difference. Thanks.

Ok. I’ll bite. How do you launch two instances of DCS on the same computer at the same time? The times I’ve launched a second instance by accident, I’ve gotten an error message.

Ummm…the MiG-29C is the MiG-29S. “C” is the Cyrillic “S”.

Always a possibility, I guess. Didn’t realize those key commands existed for the F-15C. Same key command but different results requiring two different descriptors. EDIT: So...I just checked the F-15C key commands and, for the F-15C, RCtrl + - and RCtrl + = are described as "Predicted Target Range Decrease" and "Predicted Target Range Increase" respectively. So, if it was result of something you said/did, they got it backwards as well. Not a confidence booster.

The A2A birds (F-15C, Su-27, Su-33, and Mig-29A/C/G) all have dedicated commands to enable/disable NWS. The A2G birds (Su-25, Su-25T, A-10A) do not and it would be helpful, if they did. The A-10C and A-10CII do have the capability but they, of course, are FF modules.

These mods use, as far as I know, use FC3 aircraft as their base. So the F-22 would use the F-15 controls, the Su-57 the Su-27. Any specialized commands are usually included in a text file or something similar. Just download the FC3 manuals you need.

Is the problem that, even when you set it in the UI Layer it doesn’t work? Also, have you tried to run Repair to see if that fixes the issue? I’m away from my PC for a few weeks, so I can’t check to see what mine looks like, unfortunately.

The key binds are still there. Just called something different now, for some reason. You might want to make it a bug report because of the mis-naming.