near_blind

You're not missing anything, and it's not your fault. The LSO calls were built by ED with the hornet in mind. The turkey is on speed at a higher AoA than the bug, so the LSO constantly calls you slow. vJello needs to stop sipping torpedo juice and work on his visual identification

You said we should have zoom and slewing control. I posted where you can find them.

https://www.heatblur.se/F-14Manual/general.html#controls-and-displays

I'm not sure that it's the direction from the previous mission. You're sitting on an aircraft carrier which is a massive chunk of ferris metal, with it's own local magnetic field that effects the magnetic compass on your aircraft. As stated in the manual: nullYou'll probably be seeing a flashing "MV" somewhere on the HSD, either below the HSI compass wheel in NAV mode, or at the bottom right if you have the TID repeater up.

No one's seriously advocating yeeting skins, but It goes to the argument of what is "realism". We have a late 80s jet with upgrades from the early 2000s. Is it a 2000s jet? Is it an 80s jet? If the former, why do we have AIM-7Fs and AIM-54As? If the latter, where from comes the BOL, lantirn and ALR-67? In either case why can I dress it up in an officially distributed skin as a 70s CAG jet loaded to the hilt with MAK-79s? I imagine the answer is because it is at least theoretically possible, and it adds playability to the aircraft. As would rear aspect Navy heaters

AIM-9H on a Tomcat in the 1980s. We've hit our accuracy quota, let the lua editing commence.

An ICBM is going to be reentering the atmosphere at something like Mach 20. The AWG-9 doesn't have the doppler bins to see something going that fast. Assuming the missile was able to be guided, by the time it fuzed the warhead would be past the blast zone. _Even if the blast was in time_ the warhead is going to be made out of things tough enough that anything less than a direct hit isn't going to phase it.

That mission really shouldn't have you using -54As. That's a hold over from when the AMk60 was a wunderwaffe and considered "the best".

Sorry, I meant that the F-14 deck crew are extremely motivated, more so than their Hornet or Harrier compatriots, and rapidly accomplish the task before communicating. Realism Achieved

This is intentional. The idea is if you’re trying to prevent the aircraft from falling off a suddenly slanting carrier deck, you want the chocks now, not two seconds from now

I've got no idea when that changed, but... I guess it's not wrong?

How come?

That looks like a scripting error related to an event handler. Does this happen in every mission or just that one?

Per the Manual.

From even an unrepentant boat nerd: The E is a fine variant that has done good works. There is no shame in this.

This is one of those things that happen as minor changes happen to the code base over the span of a decade. When the F-15E was originally added for DCS A-10C, it had air to air weapons on the CFTs, and this is where those loadout presents come in. Some years later, it was decided (I imagine based of SME input) that in fact you can't load AIM-120s/AIM-7s onto those CFTs and they were removed from the list of options, but the preset loadouts remained. I would imagine that with the Razbam F-15E coming Soon , that will add them back. In the mean time what you can do as a work around is select a air to air load out, switch the group's task to your desired air to ground task, and then directly add air to ground weapons using the mission payload bar. You can then save your customized loadout using the Copy button. It's a kludge, but it works. null

Yes Also Yes. Consider that accurate for the AIM-54As.

I could get in trouble for even mentioning this exists, but here's Top Secret footage of an F-14A engaging and defeating three fighters with "OP AF plz Nerf" flight models. It might help developing counter plays against the Hornets.

Are you cranking?

From what I remember it wasn't done because of concern that power fluctuations when the generators kicked on after the engines started would cause issues.

Word of God is if the track isn't visible on the TID, it isn't weighted for scan zone slewing

The only behavior that seems like it might be repeating it on my end is if there are no healthy tracks that exist both within the scan volume and the TID display area. I.E. Turning such that a track centroid is dragged off either side of the TID will cause a TWSA scan volume to snap back to the center. I don't know if that's a bug or not.

It looked like the Dragons Tooth BVR instant action on the Marianas. I flew it and didn't see any issues with the radar snapping off or dropping tracks without reason. I dragged the contacts from one gimbal to the other

Other question would be are you running any mods that effect Jester? AIRIO, etc.

Are we talking about the behavior at 0:43? If so, what was the radar commanded to do there? It almost looks like PAL was briefly selected. If that's the case, entering any of the pulse modes or RWS will instantly clear any tracks you might have.