mattag08

It would be nice if we could get modern radar-aimed flak as well. For instance, the KS-19 and ZSU-57 with the SON-9 (Fire Can) fire control radar would be great choices since they served in Vietnam and Iraq as well as other countries with Soviet equipment. These were a weapon that aircrew have recalled being fired at them by the Iraqis with some significant concern and are quite dangerous in well trained hands. Imagine flak bursts targeting you at 40,000'+.

If someone fires 6 AIM-54s at you, just turn cold and run. Or just notch them all and drop chaff and you will defeat them all at once. Once the 54s are all out of energy, they are out of missiles and you can turn and kill them (or they run home and their sortie was pointless). Firing multiple missiles simultaneously is a very bad tactic. Now a Pk-enhancing missile or two is not the same thing and a very valid tactic. Exploit your enemy's ignorance, don't whine about it. Also as far as jamming, the Phoenix has track hold and burn through is a thing, so that's not going to 100% defeat a shot. I'm kinda thinking you don't actually fly the F-14 and just came here to complain. We all know about ED's half-baked attempts at EW and Radar modelling, but this is the F-14 forum not the DCS World problems forum...

The thrust to weight of a light tomcat is very near 1.0, so yeah...

Please mattag08 is what my parents call me. Matt is fine. :D

There's no superbug in DCS...

You need to learn how to defeat these missiles before whining. You're way off the mark here. This topic has been discussed to death. If anything the Phoenix is undermodeled compared to real life based on statements from actual 14 pilots/RIOs. You're going to have to learn to defeat it. It won't get worse, it'll get better with the missile API.

It was this way in real life. Even new tomcats quickly became worn. You need to memorize the switch positions as the real aircrew would've.

The nose yaws against the turn. I don't need to watch a video to confirm what I can easily observe.

In those situations use the emergency gear/hook release, so at least you can successfully land.

Hopefully the 22nd...

You don't though. You can see the nose track opposite of the turn. The net yaw is adverse.

The inclinometer (the "ball") is showing the opposite of correct indications. For instance, a right roll with no rudder will cause the ball to fly out to the left. The ball should be showing an indication into the turn if no rudder is applied due to adverse yaw. I will preempt attempts to explain this away by also noting that I am using landmarks to visibly verify the yaw. The adverse yaw is indeed present in the flight model and working as intended, the ball is simply moving in the wrong direction. This seems to differ based on speed. At slow speed the ball shows accurately sometimes. At higher speeds the ball shows a greatly accelerated and inverted position. I don't remember this being a thing in past builds so I feel like it was introduced recently, but maybe I wasn't paying much attention.

Mike, Can you tell us if this is actually functional in DCS? I've never seen a sparrow guide this way (heck I can't even get one to fire). Also, what is the practical game functionality of SP PD mode? Does PD have any benefits or detriments? Are these two things actually modeled and working in our current open beta build or are we still waiting on missile API for all these features?

This would also be very useful in multiplayer to sort contacts when one or more of the members of the flight doesn't have a human RIO.

I'm writing this post outside the normal keybinds post in hopes that it gets some visibility and attention from HB. I was hoping to get an update on when a particularly important keybind is planning to be added to the game. Specifically the keybinds/axis for the HSD course knob (and really all the HSD/VDI knobs). This knob is very commonly used in navigation (it is fundamental for TACAN use). The course knob is often used in a variety of situations where the pilot cannot be heads down or hands off the stick for a significant length of time such as Case I procedures, Case III procedures, TACAN rendezvous, TACAN navigation, TACAN approaches, etc. In some cases, this is due to the pilot needing to focus on flying the instruments very precisely (such as Case III) and any time spent away from the instrument scan can lead to deviations. In other cases, a wingman may be attempting to remain in formation while setting his radios for an upcoming approach or recovery procedure. This is made difficult to impossible for two reasons: 1) The pilot must remove his hand from the stick (if right-handed) to pick up the mouse and adjust the knob. The course can take multiple seconds to set, which can lead to falling out of formation position. This can cause problems that range from very inconvenient to downright dangerous. Imagine a formation approach in IMC where the pilot must maintain sight of his lead or he will have to execute lost sight procedures and separate from the flight for safety. Same for Case III procedures. 2) The pilot must look away from his lead and stare at the knob in order to manipulate it with the mouse. This leads to a similar issue as #1, but even more dangerous. By looking away from his lead for a protracted period in parade formation he is risking a mid-air collision. Due to the nature of how the knob is programmed and the time required to use the mouse, it isn't possible to complete this task quickly without looking away from the flight leader. In reality, this task is accomplished while flying formation or in IMC by using the left hand to turn the knob while the right hand continues to fly. Additionally, the pilot moves the knob by feel and only takes quick peeks to see how close he is to the correct radial he wishes to select. This way he can maintain sight of lead or continue his instrument scan and cross-checking his instruments. Currently this technique is not possible for pilots of the DCS: F-14B due to the lack of keybinds. Please add this keybind as soon as possible. I have been waiting since Day 1 for it and I'm sure there are other pilots who fly this aircraft at a similar level who have similar frustrations. As someone who was already very familiar with naval ops and procedures from flying the F/A-18C before the launch of the F-14, I was amazed to find some of these critical, obvious keybinds missing. These are not arbitrary, but very useful for many players who have a variety of home cockpit, HOTAS, and other peripherals that could utilize them if they existed.

Possibly related to the radar not being properly horizon stabilized?

It is possible IRL. Not yet implemented.

There are more formations than what are listed in the F-14 NATOPS. Tac wing (USAF = Fighting Wing) is pretty standard when just killing time.

Considering it's an Environmental Control System item, probably not much in the sim. If modeled properly, the ECS controls: 1. External drop tank pressurization 2. Cockpit pressurization 3. Canopy seals 4. Windshield and canopy defogging 5. Windshield anti-ice 6. Windshield air 7. Anti-g suit inflation 8. Pressure and exposure suit vent air 9. Wing airbag seals 10. Ammunition purging (aircraft prior to block 150) 11. Electronic equipment cooling and pressurization 12. Temperature control of liquid coolant supplied to AN/AWG-9 control system and AIM-54A Phoenix missile. In theory turning it to the wrong setting could result in ECS overheating and other issues. I thought they mentioned this being modeled, but I've never seen it myself. RAM AIR was used to circulate fresh air through the cabin (such as when there is smoke in the cabin due to electrical failure or some such). These sorts of environmental cockpit effects aren't modeled. If the ECS is in the RAM AIR or OFF position you can't fire the gun.

Is this in MP? If so, it's a known netcode (ED) issue.

If you have GUN selected you will not see the ACM mode symbology, but it is still working in the background. Switch to SW or SP/PH to see the diamond on the HUD. VSL Hi will not show because it is scanning above the HUD.

Every time the contact goes to the notch when defending against a missile I get this behavior, FWIW. It's more pronounced now that TWS Auto has the automatic track hold for AIM-54 launches.

While this probably should be fixed, I'll give you a better alternative from someone who's been at this for 25 years (with some real world flying experience): You should avoid using the mouse as much as possible. All of these controls you're mentioning should be bound to keyboard keys at worst and your HOTAS somewhere (usually my throttle base) if possible. This way you can't accidentally click the wrong thing. Generally, you should be able to actuate the commonly used items by feel and not have to look down so you can continue to fly the airplane while you manipulate the controls.

Has anyone been noticing oddities in AIM-54 and AIM-7 behavior since the TWS Auto patch (particularly in MP)? As a client and as the host in a MP session AIM-54s and AIM-7s have been failing to guide approximately 50-75% of the time. This occurs in both TWS and STT modes for the AIM-54 and obviously STT for AIM-7s. AIM-54 shots were made at ranges from 5 NM to 50 NM at 20,000' altitude, hot aspect, maneuvering and non-maneuvering targets. AIM-7 shots made at ranges of 2 NM to 15 NM. Often the missile will do very strange behaviors such as: 1. Coming straight off the rails and never guiding. 2. Coming off the rail and immediately tracking the location of the enemy when the missile was launched (chaff possibly?). 3. Tracking, then failing to track, then guiding again, then failing to guide, then guiding again and repeating this behavior over and over until it hits or passes the target. 4. Flying the loft profile then ceasing to fly the loft profile and going straight at the target even though the target remains STT'd or the TWS track is stable (at ranges of 30-50 NM). 5. Both missiles (in all variants) seem to have near zero resistance to chaff and will almost always guide to the first or second chaff bundle regardless of a good track in TWS or STT. This may be occurring for AIM-120s as well, but I've only played the 14 since the patch, so unknown if this is a ED missile issue or HB radar issue. Related: I don't know the exact seeker algorithms or sensor operation of SARH missiles, but is it possible for to fire a SARH missile with a good STT lock on an aircraft and the missile seeker to track chaff? Even if the launch platform has retained a good lock on the aircraft throughout the missiles entire flight? Also unrelated: In the manual the AIM-7 is supposed to continue to guide based on FLOOD mode after a loss of STT. Is this behavior modeled? I've never see it work in over a year of flying the F-14 now.

Yes this is an issue with Fox-1s in general. Been a bug for two patches now.