Ironhand

Unfortunately I won’t have access to my computer for another week or so. I’d love to take a closer look at some of the assumptions that we’re making. OTOH, it certainly seems that the missile interacts differently with the two platforms.

That’s interesting. I was only going by the data you presented and hadn’t watched the videos. You used active pause. So there’s a variable not account for. Either the target aircraft were flying at different speeds within the first two test groups or the “own” aircraft speeds are not identical as assumed. I suppose both could be true, though. The 11,800 m test is the one where they were identical. EDIT: Maybe I’m making a mountain out of a mole hill. And this isn’t a criticism of your test procedure. It just seems that something is amiss and it might not be the missile.

What I find interesting is how, at 12000 m altitude, the distance travelled between launch authorization and the actual launch is nearly identical (0.01 km difference). OTHOH, the difference at 1100 m is 0.1 km and 0.2 km at 8000 m. Why is that? Differences in closure rate?

If the R-27 R/ER was the Cookie Monster, most of the cookies would be eaten. Anytime I test without chaff available, the hit rate goes way up. That even applies to long-range shots toward the outer limits. Using Dipirona4100’s R-27 track, I went from something like 12 out of 20 hits with the first missile to 19 out of 20 after removing the target’s chaff in the ME. Admittedly, that’s not a lot of trials but…

I see your point. I must be doing something wrong, then. I’ll try to figure it out, when I get back.

What were the conditions that have you convinced that it absolutely should have hit the target?

Ummm...they're not random. The stars are the Spring star field. Unfortunately, they don't follow the seasons. It's always the same star field visible. So Orion and the adjacent constellations are always setting in the west (you need to set the date/time to late December just after sunset, for example, on the Caucasus map). Set the time to just before dawn and you'll have Pegasus, Pisces, Perseus, etc rising in the east. And the various constellations as they would be in the Spring traveling through the night sky. The planets are there, too, though too far off the ecliptic and not showing as they would at the ME set date/time. EDIT: Something that I started working on but never finished, using Arttu’s Night Sky mod:

@Dipirona4100,FWIW, taking control of your TRK, I get first missile hit roughly 50-60% of the time. Take chaff out of the equation and it jumps to roughly 90% for the first missile. Admittedly I run the attack differently than you do (lower airspeed, stay below him, and, given the short range, use Med or ILV). I've attached a representative TRK file. At lower altitudes, especially, I find it best to stay below your target. At high altitude (10km or higher), you can get away with letting him get a few hundred meters below you. But don't do that at the altitude you're flying in your TRK. Dipirona4100_R27-Ironhand.trk

Is this, perhaps, a Mig21-bis issue? They work fine with the FF MiG-29 and FC3 aircraft that can carry them?

Excellent idea.

Or, simpler, just make the default setting in 2D be “Off”. It’s off by default in the cockpit. Do the same for 2D external.

Not impossible but there’s far more terrain as well as map objects, etc on the Caucasus map than the WWII Marianas map to deal with. AND…I’d love to have a map like the OP suggests. Won’t live long enough to see it, though.

After the latest update, my HSI reads “KM” and “ЗПУ” as it should with the cockpit set to default. Perhaps a mod of some sort interfering or a slow repair needed on your end? EDIT: I don’t know if the flag you fly under makes a difference, though. I checked as Russian and Ukrainian.

FWIW, the Su-27 manual mentions, when doing circuits, turning them on as you cross the outer marker.

Yes, I knew that. It was faulty thinking on my part. Sweet senility is slowly settling in.

Do you have the switch set to “Boresight”? Outside the canopy bow you need to aim the missile’s seeker directly, not through the IRST.

Ahhh… “Бирюза” Turquoise in English… but why “T” in Cyrillic? Confusing.

One that jumped out at me was on the image for the HUD that starts with acronyms “П, Г, and K”. “T” does not stand for “Привод”. First of all, there’s no “T” in the Russian word. I think it stands for “Топливо” (Fuel) meaning RTB due to low fuel.

It matters whether the target is approaching, crossing, or receding when talking about a SAM's engagement zone. Most of the time, the target aircraft were crossing at the outside edge of the zone. So, although it prepared to launch, it didn't because they remained just outside the missile's max range for their altitude and aspect. Changing the aircraft's approach a bit, yielded a launch when the ranged closed to approximately 38 km. Mission attached. I had altered the SAM unit placements but that really made no difference. All that needed to change was to reroute the target aircraft a bit. EDIT: Just added TRK file (BUK-Test-Mach) showing how much sooner the BUK launches, if the target is traveling faster--M1.3 rather than .5 or .6. Supernove-III_Buk test-Ironhamd.mizBUK-Test-Mach.trk

Good. Glad you got it sorted out. And thanks for letting us know.

The issue is with one/some of the units in the mission--either static or active. I deleted all units except for the 4 clients (Su-25Ts). Once I did, the tower started responding to the start up request. If there is a unit mod of some sort in the mission, you might try deleting that one first. I left all triggers intact. So it's definitely a unit that's corrupting the mission.

In my experience with the ME, there are times when something weird will happen. Often the best approach is to start over and you’ll find that the problem won’t be there anymore. If I get a chance a bit later (when I’m at my computer, I’ll check your mission and see if I have the same issue with it.

Thank you for checking.

Well, I was nowhere near Dmin and we were approaching head on, when it started. It had disappeared before the target started aggressive maneuvering. It is the KMOD cue, though, I think. The range kept shifting somewhat erratically by a little bit until after the missile was launched and the cue disappeared. Maybe so but I had done none of that. It seemed to happen automagically.

In my case, before, during, and a bit after. I was wondering if it stood for KMOD. KD in Cyrillic but the English KR doesn’t make sense, if that’s the case.