near_blind

without a tacview or a video, or a track where the jester menu isn't used, this is fairly hard to diagnose. With missiles in the air, elevation/azimuth steering is automatically controlled by the computer to try and maintain coverage over the greatest number of highest priority contacts. Off the top of my head, all I can think of is that one or more of the targets went into track extrapolation while descending, and the radar wasn't able to correlate those tracks into a new hit, causing the zone to get dragged down. That or the radar somehow getting into TWS-M with a look down azimuth set, but that shouldn't be possible with missiles in the air.

bare in mind that lua is completely missing the configuration for the player F-14A. F-14A is unit name for old AI unit. F-14A-135-GR is the HB unit. A bit of a lingering whoopsie on ED's part.

I'd imagine the aircraft is getting SINS data through the cable.

The Sparrows stole it

It's now been reported to ED.

(Even in STT, CW isn't a thing with AIM-54s, but that's a separate topic)

How does the signal change for an AIM-54 launch? CW in the Tomcat is specifically an AIM-7 thing, the AIM-54 is looking for the PD wave form. There's no switch to HRPF because all AWG-9 PD modes (TWS, RWS, PD-STT, PD Search) are HPRF: the radar doesn't use MPRF and LPRF is pulse only, which the AIM-54 cannot guide on. The only emission that would explicitly tip off a launch would be post launch cueing signals from the AWG-9 to the missile, but if we're going down that route, I'm not sure any TWS launch would be considered quiet.

That's a bug. I'll have to see if it also includes player aircraft. As for the user "explanation" CW isn't used for guiding Phoenixes, and the Tomcat is _always_ using HRPF PD because the AWG-9 doesn't use MRPF and only uses LPRF for pulse, which can't communicate with the AIM-54. You could argue that an RWR could theoretically pick up on seeker steering commands passed to the AIM-54 by the AWG-9, but if that were the case, AIM-120s and SD-10s should also trigger a launch indication in TWS.

aighaightaightaight, but what about Agile? * ducks *

Yeah, that's my bad. Sentiment remains though.

Having talked to two different people who were lit up by barlocks in two different types of aircraft during a recent geo-political imbroglio, it's my impression that at least the United States has settled on barlock = all launch warning, all the time

Apocryphally, if that facet of the Barlock were simulated accurately in DCS, it would go straight to a launch indication when detected by the RWR.

Unless something has drastically changed, DCS only allows four aircraft per flight in any situation.

Check what the Viggen is doing. Last time I tried to dogfight an AI one it was doing something like an infinite sustained 8G turn. The deflection was such that the lead required to hit it had pulled the gunsight out of the area of the HUD.

null The wording isn't exactly clear for what is displayed when the auto schedule sweeps past 55 degrees, but it should definitely show MAN before that.

It also effects Paveway IIs. It's been reported.

Showing AUTO instead of MAN is a bug and has been reported.

It doesn't. Link 4A data only goes one way. You aren't always guaranteed to have an E-2 around, or be in range of an E-2 or a boat. It exists, and you can use it. That's what's good about it. Comparing Link-4 with Link-16 is always going to come up short because Link-16 is the better system, it's also 20 years newer and has the benefit of building off of the lessons learned from Link-4. Link-4's advantage is that it exists in 1974, and that you can use it while half the jets you would conceivably facing barely have a useful radar, much less any sort of datalink beyond "fly this heading and altitude".

I was able to confirm from your tracks and have made a report with Heatblur.

It happens whenever you load anything that requires the pallets after removing the pallets.

Works on my end. did you put the wings into auto after doing the CADC reset before trying to use the control hat?

yes

There's quite a lot funky with how DCS handles radars, missiles, and countermeasures. Unfortunately those values are not entirely up to HB to decide

How fast are you going? Above 225 knots the landing flaps will jam If not retracted. If you’re taking off in the B with burner, that’s not a hard number to pass

any weapons mods installed? are you moving the aircraft before the ground crew says "rearming complete"? You're selecting Phoenixes and not Sparrows?