Spiceman

Hopefully OBC. IRL you can’t launch without it.

Lord, there are three sources of AOA info with 1 degree FOV from each other. Pick one.

Hard no. And moot.... Heatblur is laser focused on realism, it’s practically a religion to them, as it should be.

The only difference I see between the video and DCS, and I am admittedly not a videophile/photophile, is that the painted numbers on the VDI screen (the VDI had “fixed” images and “painted” images like the pitch ladder) are a bit large. Other than that, they look the same to me. The other thing that would really be cool if HB could pull it off is the sloppiness of the painted images, like the little droops and smears and globs, where the electron gun didn’t stop shooting perfectly timed with moving to the next line. Like the pitch ladder numbers in the video. Looks sort of like an old typewriter with dirty hammers (or whatever those things were called). It would get worse under G as well.

For what it’s worth, they look exactly as I remember them.

They have the missile hard-coded to go active at 16 TTI as a workaround for the moment, I believe.

I use the JTAC/Designation functions a lot. I also use the Zone Polygon to have polygon zones as DCS, unbelievably, doesn’t support something so obviously basic. I also use the menu functions to have nested menus. I can’t imagine building quality mission with just the native DCS ME functions. The script makers are quite literally saving the game.

The Phoenix and the AWG-9 have done their jobs there as well, right?

It’s not lost, and it will continue to fly to the last known target location and unless the target did some pretty drastic maneuvering the Phoenix will very likely find it. The target will not have any warning until it’s most likely too late.

The missile in flight will not change what it’s doing. Any future launch will be SARH against your STT’ed target. You could turn away, get shot down, turn the radar off, what have you and the missile in flight will continue to fly to the last known target location and go active at 16 TTI and chase whatever it sees.

The answer is no to all of those. The guidance mode of the missile is set during the LTE cycle and it doesn’t change once in the air. That, and the AWG-9 makes no correlation between an STT’ed target and a TWS track.

When a Phoenix is in the air, Track Hold is enabled and the AWG-9 will put the track in coast mode until a new track file can be created. If the track is re-acquired, the AWG-9 may or (more likely) may not be able correlate the new track with the old track and most likely the Phoenix will continue to be guided to the held track file. That’s my understanding, but the devs can correct me if I’m wrong.

It’s modeled. You can test it by taking a shot at a bandit and immediately turning the AWG-9 off or to Stby. The Phoenix will stop lofting and fly in a straight line to the last known location of the bandit. It will go active and when it’s close enough, if the bandit is in the Phoenix radar cone, it will start guiding. There is some weird bug in DCS whereby if you take shot in TWS, the bandit doesn’t react/maneuver against it, but it does start popping chaff. Not sure what’s going on there. The bandit starts maneuvering when the Phoenix goes active at about 16 TTI.

If I disable Object Export on a server because I don't want clients to have a Tacview, it also renders TACAN inoperative. I don't remember it always being this way, is it a bug?

There was actually a plastic filter stored in the map box that snapped onto the front of the VDI. The little rod along the bottom of the VDI is what it snapped onto.

I don’t believe the carrier supports suspending a launch, so it’s more a question for ED. I also don’t believe it’s on ED’s list of intended features for the carrier, so I wouldn’t hold out much hope.

TTG on the TID is the only tool. By the time the F-14 was doing any serious A/G , handheld GPS was a thing and the crews would carry store-bought handheld GPS. The first one I remember seeing was the GPS III Pilot.

Yeah that’s why they talk about how much skill it took. Once you raise that handle, you are solely responsible for the wing position and there’s no failsafe. Drive them too far forward and go too fast and you could break all kinds of stuff.

I think what some guys used to do is override the CADC by using the emergency wingsweep handle and driving the wings full forward so that they could drop full flaps or drive them forward of 50 degrees to get main flaps.

He may very well be saying that he dropped the flap handle, which would indeed drop the main flaps. That does not contradict anything said here.

Those interlocks exist because the flap handle can be lowered as long as the wings are greater than 50 degrees. The flaps, however, will not completely deploy until the wings come all the way forward. So while the pilot can only select flaps up or flaps down, the flaps have various stages of deployment. Our SME crew consists of avionics techs and electricians who maintained the system, rigged the flaps, adjusted the micro switches I mentioned, and were turn-qual’ed on the Tomcat and operated the flaps literally hundreds of times.

Yes, we’ve been having that discussion. There’s just no application for a flap axis mapping for the Tomcat.

That's the whole thing... the F-14's flaps don't have an intermediate position. As soon as you come off the micro switch by moving the flap handle a couple degrees, the flaps move from full up to full down. There is no intermediate position for the flaps. The flap *handle* can be left in any position between up and down, but the flaps will always either be fully up or fully down. The flap handle could very well have just been a two-position toggle switch in real life. It's not because the F-14 is a very mechanical system and there was a physical interlock between the wing sweep and the flap handle which prevented the flap handle from physically being moved if the wings were aft of 50 degrees.

What would the three positions be, given that the F-14 only has two flap positions?

It’s a bug right now.