The_Tau

I use JSGME or OvGME to manage my mods

You can press stuff with human RIO too so don't press them

Thats why I use that mod to map RIO controls, like HCU, NEXT LAUNCH, MLC, CAP NUMPAD for target data, CAP TRG DATA page and that one CAP button for DO NOT ATTACK. So I have control over all of those from front seat. And its awesome. https://www.digitalcombatsimulator.com/en/files/3319633/

No, there is no Jester command, at best you can STT specific target. So either you have to jump to back seat, hook track you want and press "Next Launch button" Or you use mod like this one to get RIO controls in Pilot seat, and you just map it https://www.digitalcombatsimulator.com/en/files/3319633/ Also there is option "DO NOT ATTACK" on CAP under TARGET DATA category. It makes AWG9 ignore tracks, and its excellent to simplify AWG9 TWS scan to make it focus on one maybe tops 2 targets. "GND MAP" supposed to give track "Mandatory Attack", but I am not sure it gives track some priority over centroid of radar. So what I do when attacking multiple targets is to set do not attack on other targets with low pk (like they fly at low alt), so that awg9 focuses only on tracking 1 track with high pk (target flying high)

I use those tactics

Well actually i think it's other way around. Dispensers are not modeled yet so it's always LAU7 visually. So fix could also apply to fear the bones campaign

Yes? You just uncheck box "fill with chaff"

Hey, took a while but got 2 more playthroughs! I am pretty proud with Mission 3 it went pretty clean as I had good gameplan Also @Reflected I noticed that F14 have Lau-138 chaff dispenser, which I am sure only came post Desert Storm later in 90's.

First of all, once again. 54 is not 120. Do not use it like 120. Firing below 30k alt unless ACM, is firing outside 54 parameters. Ace AI is unrealistically too good, and that is ED problem. It always sees 54 incoming at 10nm, and can notch it perfectly no matter the quality of RWR 54A is a complete trash vs fighters, as it was designed purely vs bombers (and it was used as such by USN doctrine, AIM7s were for fighters). 54A not only require TWS go active signal (if track is lost then missile is trashed), but it also have much lower notch, chaff resistance than 54C. When notched, pull up maneuver by 54 I do consider as bug, require fixing. Unfortunately, there is nothing you can do about it right now Firing 54 parameters is at least 30k, but best 40-45k, higher -> better. 0.9 mach minimum, any extra speed is nice bonus but 45k is more important then 1.2 mach. AI is dumb, and if it is targeting you it will try to match your alt. So keep your alt after firing, it will make AI keep your alt at around 40k. 54 is absolutely deadly against targets over 40k. Therefore prioritize high flying targets. Say loadout is 4/2/2. If I see 3 targets in trail, first 2 below 20k and last one above 35k, I would target last bandit, set ignore the tracks of first 2, to make it easier for awg9 to have nice solid track, support until pitbull on 3rd bandit and then skate to build separation and reset. You could also fire on first 2 targets but PK would be much lower. You have to decide do you want 1 probable kill and 3 54s left or use 3 missiles to make them all go defensive but all of them survive and have 1 54 left. Use ECM. It will greatly decrease range of AI engaging you. Burn through range should be around 29nm so when you are closer then that DONT FORGET TO SWITCH ECM OFF. Otherwise you will turn enemy R27ERs into HOJ fire and forget stealth missiles. Per starting at mark 15 min Use TWS/STT range rule above 30nm to target use TWS, 30-20nm deadzone, do not fire, less then 20nm PDSTT. 15-10nm and less Pulse STT but PDSTT also good. Tacview-20230112-015824-DCS-F-14B BVR Su27.zip.acmi In short in BVR fly it more like interceptor MiG31 and not like F16/F18

In current HB manual I would like more info on what is actually simulated in DCS. Stuff like SP PD is nonfunctional, what PRGM RESTRT does or behavior of 54C in PD STT...

Amazing!

Yes, had 1 left. Just like you. I noticed 1 guy spawns right in side of mountain. Bad spawn placement...

+1 Please add this feature?

Tacview-20230223-233951-DCS.zip.acmi I admit this was my second take and I was very lucky that AI was in the end Rookie/trained (set as random in ME) This scenario is very tough for 54C as all drones are flying low (by 54 standards), but if they were simple CAP, and climb to 40k 54 could kill them quite easily

@bonesvf103 can you send that F4E mission you made? I find it interesting they started chaffing immediately when you fired. Also finding best tactic for doom scenarios is kinda my hobby

As it was noted before AIM-54 Phoenix is NOT AIM-120 AMRAAM - its much older (concept from 1950s, design/electronics from 1960s or best case 1986 for 54C - 14 YEARS before 120C-5) - DIFFERENT PURPOSE! from different era! - Different shape/weight class (needless to say there are no more short, fat missiles, but rather long and thin - there is good reason for it) You have the biggest radar ever fitted to fighter, best detection and possible engagement range at least until Eurofighter arrives. From those facts IMO limiting yourself to 30-35nm shots (like you would employ with 120) is a great handicap and limitation placed on F14. AIM54 is fast in comparison to other weapons which were in service at the time of its introduction in 1974, mainly AIM-7 sparrow. Comparing it to 2000s AIM120C-5 is pointless However it got poor acceleration and ridicules' drag, employing it like 120 will put you in great disadvantage. Needless to say that AIM54 mk47 will have great difficulty to break mach 2 when fired from below 10k, mach 0.9 Firing at 30nm will allow bandit (except one armed with IR missiles or like MiG21) to potentially /spot you/lock you/fire at you/go defensive even before your 54 goes active. All he really needs to do is to go into notch for few seconds and your TWS track is gone. On top of that 54 will not have really energy to do anything to really threaten him. If your goal is to force him to go defensive, you might as well fire AIM7 preserving 54s for closer ranges for Fire and Forget capability AIM54 when employed correctly is amazingly good at keeping same amount of energy over distance. Missile energy wise for TWS shots, there is not much difference between 35nm shot or 60-70nm shot. MIssile will arrive at pitbull point with very similar energy. So why not use that to your advantage and fire from longer range, and stay outside enemy engagement range? If bandit is at above 40k when missile which still have at least 2.5 mach of energy goes active, PK of 54 is very high even against ACE AI or humans. Here is an interview with former F14 crew member that said that they doctrine of using 54s was to fire at 40nm ranges up to 30nm for TWS shots. then 30nm-20nm was missile "deadzone" as bandit will be much more aware of danger from you due to your proximity to him, and more likely to start defensive maneuvers. And then they would use STT at ranges 20nm and less. In my experience in DCS these ranges are very much true or even you could use mentioned older distances of firing at 60nm. In PvP especially, if bandit is high above 30k-35k at 60nm he still is ingresing towards target area, thinking he is completely safe. He might arm bombs, check phone whatever, and suddenly got RWR warning. He might even ignore it thinking its for someone else. You add to that at least 1.2 mach, 30k-40k ft alt you would be cruising, following Missile Abort Ranges (for 120 especially), and then you are extremely hard to kill to any SPAMRAM throwers (F-15 included).

@TOMCATZYeah aim 54 is not amraam. Do not treat like one. Its got its own stats. Look at my tacview and yours. You fired at 35nm I fired at 60nm and yet 54 arrived at 10nm from bandit (distance AI detects missile and starts defending) with around same speed of 2.7 mach. With 54 is not really distance which affects missile pk but altitude. Altitude of you and the bandit

You see, you did something I suggested not to do - you dived after fire. Try again but fire from longer range say 45-50nm, turn jammer on (turn it off when range is less then 29nm), and KEEP alt until pitbull, Then you can skate if fired upon or push him. Keep alt at least above 20k but best 30k unless fired upon from less then 10nm Your second 54, you fired from alt 3k feet, and 54 couldn't even break mach 2. Fire it from 30k, mach 1.2 and missile will dive down speeding up even to mach 3. Thats aim 120 speeds. Much bigger difference. I recreated your scenario. If you gave bandit any special actions or attributes feel free to share your mission I will try to find best tactic BTW AI was set to ace Tacview-20230222-002159-DCS.zip.acmiTacview-20230222-002844-DCS.zip.acmi

Tacview-20230112-024101-DCS-F-14B BVR F-16C.zip.acmiTacview-20230112-023433-DCS-F-14B BVR F-16C.zip.acmi Tacview-20230112-030006-DCS-F-14B BVR F-16C.zip.acmiTacview-20221218-210516-DCS.zip.acmi My take into this Currently AI in DCS is amazingly (unrealistically?) good in notching ( talking ACE level here), and it will always see missile at 10 nm. Please don't tell me you use AIM54A (too bad vs fighters + it is per USN doctrine prior 1986), use 54C If you can see your lost track diverging from real track, cut missile support, fire another one. Lost 54C might find bandit on its own Fly high, fly fast. Keep those speeds and angels, dive ONLY in emergencies Due to this fact, you are limited in defensive maneuvers to basically horizontal plane, therefore know your MAR ranges, stick to them Fire from long range 60nm, PRIORITIZE high flying bandits. Higher they go (35k+, 40k+ very juicy kill for 54). AI on CAP mission will try to match your angels, use that and bait them high 40k+. After fire DONT dive, if you do, AI will follow matching your angels making life of your 54 much harder. Use ECM, especially vs FC3 Flankers, they will not fire until range is <29nm. REMEMBER TO SWITCH ECM OFF WHEN RANGE IS BELOW 29nm. Otherwise you turn their R27ERs into stealth Fire and Forget missiles After pitbull banzai, keep the pressure, you kill them with long range great, mission accomplished. Otherwise they are low and slow, you are high and fast. Scan low, STT, fire 54 20nm and less, Keep speed and angels! Keep the MAR (remember they fly from thick air!)! Abort if they are too close Tacview-20230112-015824-DCS-F-14B BVR Su27.zip.acmi Tacview-20221218-205259-DCS-F-14B BVR Su27.zip.acmi Tacview-20221218-205259-DCS-F-14B BVR Su27.zip.acmi Tacview-20221218-210516-DCS.zip.acmi Tacview-20221218-211218-DCS.zip.acmi

Focusing on Hydraulic System

Worth watching. There is whole take off procedure from CV for F14 to realign AHRS system

I always use one throttle button as modifier which essentially doubles all my throttle and stick buttons. And if necessary adding 2nd modifier tripples buttons Of course learning it can be a bit of pain but with enough practice its all worth it

well there is ur problem. T1 TV is on separate stick for reason. Look closely at exact moment u drop BK90s, you are 5km to target in front of you but then marker moves behind you and distance is 0. BK90 try to bomb new designation you overflew it forcing them to turn around

Hmm I watched ur track and I must say I find it weird your placement of M1 moves immediately after you drop your weapons. You are not pressing T1-TV when launching BK90 arent you? That would update M1 position and as you are not moving it, it will update it to ur current plane location

What are exactly the steps you do? Weapons to Attack, Mode to ANF, M waypoint selected, QFE entered, dive to 500 - 50m alt range, unsafe, when in range fire. Whats ur version of game? Maybe u need update?