Spiceman

Yes... in fact, in general, STT is arguably the better choice against a maneuvering target. Yes, the target will be alerted sooner, but if it's a fighter, they're already plotting and maneuvering against you most likely. There are different views on that out there, but I personally see no downside to launching in PDSTT. TWS is meant for radar SA and launching multiple missiles against multiple targets. It's benefits go away when you're prosecuting a single target.

Here's an example. I whipped up a quick mission with a section of MIG-29s. I didn't configure any options on them, just a CAP and letting them do what they want to do. The Wing went into a pretty good trail. I used the Jester menu to STT and then "Choose a Specific Target" (CTRL-4). I then chose the one with the farther range. A big reason to use STT is because these guys are going to start maneuvering. Your own section is also going to start maneuvering. There's a chance you're going to lose at least one of these targets in your TWS volume and hence lose your SA. The Lead, initially in TWS, will want to be locking his target at 20 NM as well.

Oh yeah, the entire avionics guts were ripped out and replaced for the D.

Right, the STT in combination with the TWS helps to ensure max Pk while also retaining good SA. There's a decent chance an aggressively maneuvering bandit will get himself out of the TWS volume. The Tomcat does not give you the HUD diamond with only a hooked target, only an STT. The HUD diamond is really tied directly to the antenna position as almost a hardware function.

They really weren’t prior to the 90s. The RIO almost always initiated VSL, so prior to the Tomcat entering the A/G arena in the early 90s, the target designator switch wasn’t used much at all.

Windy is spot on, I would just add a couple things... The two big came changers coming are a working TWS Auto and HB's access to the Phoenix Missile's API so that they can "talk" to the missile in flight. Once we get those two things, you can launch your Phoenix and crank to both slow your downrange travel and put yourself in a better defensive position. With access to the API, the radar will command the missile active and you'll be notified via the flashing TTI indicator on the TID. As far as launch range, it's really based on the target you're going against. I wouldn't hesitate to shoot at 50 NM for a bomber,. For a fighter-sized target, I usually shoot at 30 NM, which provides a decent Pk and gives you a good advantage over a bandit who might be going to shoot at you at 20 NM. In most section engagements, a good practice is for one of you to shoot in an STT and the other to shoot in TWS. We try to sort at 50 NM, with the Lead taking lead and the Wing taking the trail. The Wing will STT using Jester and both jets will shoot by 30 NM and crank (semi-crank with TWS the way it is). Assess the bandit situation by 10 NM and the jet with the best SA will call engaged and the other will support (assuming no one is defensive).

It may have been that the track file was lost and a new one initiated? No other reason the radar should be dropping your launch order designations.

Right! Good clarification.....

Right, no, it wouldn’t be aerodynamics on the control surface. It’s probably just the G on the control stick itself.

Edited.... the NATOPS states that the pilot should maintain a loose grip on the stick and allow it to naturally move aft during the cat stroke. This is probably what you see happening.

The nose gear strut is designed to provide a hands-off launch. The strut bottoms out during the cat stroke, storing 4 inches worth of instant energy when the launch bar leaves the shuttle. That instant energy release provides a sufficient nose up pitching moment that you shouldn’t need any stick deflection during launch. After that instant release, the nose strut then extends normally (by this time you’re off the deck).

Thank you! I think I’m all good now.....

I changed the mode to Realistic and it is now showing Friends and Enemies without me having to change them. However, it is still showing TNxxxx for Friends. Do I still have to update them manually in Realistic mode? In what mode will the unit names be pulled from the Multiplayer server? I've read the manual (I'm sure it seems like I haven't) but the manual seems to be telling me that I should be seeing the MP unit names now.

Oh, and one more.. I log on as Blue coalition and all the blue aircraft are displayed as Unknown with TNxxxx unit names. If I change an aircraft to Friendly, I would then expect it's tag to change to it's multiplayer name, but it doesn't. What do I have set wrong, or is this a bug?

New question, I don’t see that this has been asked... We have a server with two instances of DCS dedicated servers running on it. Since they’re on the same box, both dedicated servers have the same IP, they’re just using different port numbers. Lot ATC doesn’t seem to like this. We have a LotATC config lua in each DCS installation folder with different LotATC port numbers assigned (10310 for one server and 10311 for the other). Clients can connect to one server (10310) but not the other. Any suggestions related to this setup?

I cannot believe y’all fell for this....

Execute the pre-Combat checklist...

Give the Phoenix a try now that the update is out.

No it’s not. It simply flops around, no spring loading at all.

Yeah I have no doubt things changed when A/G became more prevalent, and especially when the need for coolanol went away. Maintaining that system out to the wing pylons was a nightmare.

I believe the D had liquid coolant for the radar, but not for Phoenix. So it would have been limited to the C.

Yeah, not sure. The NATOPS I referenced is from 2001. I agree, none of this is going to matter in the sim.

Well, no, I believe he is correct... I don’t have a direct memory of it, because we never carried Phoenix on the wings and I never came across it. But the NATOPS states “AIM 54C missiles do not need liquid cooling.”

If I remember correctly, one 18-gallon pump/reservoir (in the station 6 Phoenix fairing) supplies coolant to all Phoenix. There are no dependencies on which stations need to be loaded, I.e. you can have Phoenix on the wing pylons only, if you choose.

Those were our standard load outs. We had two standard load outs... two Sidewinder, two Sparrow, two Phoenix and then we had four Sidewinder, four Sparrow. This was before the Tomcat had a big A/G role (I got out of VF-41 right before they went on the cruise that wound up in Bosnia).