AGM-45 Shrike Quick Guide by Klarsnow - updated June 5th 2024

[MysteriousHonza]

On 8/29/2024 at 10:47 PM, =475FG= Dawger said:

I don't think so. Not much of a warhead. Not meant to penetrate. Hitting the transmitter. Probably not going to kill the vehicle.

This is dcs. No ground unit has good enough DM... One bomblet from heat cluster should be enough to mission kill almost any vehicle it hits center mass. In DCS, it does %dmg. Shrike in dcs upon direct hit should destroy any radar unit as we cant really disable radar antennas on them 

[Oscar1984]

В 29.08.2024 в 22:44, CaptPickguard сказал:

WRCS seems to work decently in some conditions. Still need to test more. The small warhead really highlights the inadequacy of the current vehicle damage models though...

I recall a change to ships that disabled their radars when hit with a HARM. Maybe ground vehicles can get this change too, permenantly disabling their radar when hit with an ARM.

If you're looking to sharpen your strategy in such games, it's all about adapting to the dynamics. One key is knowing when to play tight versus capitalizing on the mistakes of loose players. Tools like hand charts and online resources can help you refine your approach, but don’t overlook broader learning platforms. For example, sites like GradesFixer https://gradesfixer.com/ can provide interesting insights on analytical thinking that could indirectly benefit your decision-making at the tables. 

Cool video.

[thodre]

On 10/17/2024 at 5:37 PM, Sunnny said:

Hi guys,
I'm trying to understand Loft deliveries with the Shrike in the F4.

[...]

So does the Shrike activate its seeker above or below 18,000 feet ?

I don't know about the seeker, but it starts correcting it's course below 18000. It's clearly visible on the missile-cam.

On 10/17/2024 at 5:37 PM, Sunnny said:

So I'm wondering: 
Are there some more reliable data available ?
Has someone already undertaken this labourious task of figuring out these parameters for different altitudes and speeds ?

I haven't. I usually use wrcs which works pretty well for everything up to a range of about 20nm.

[lee1hy]

SA-15, SA-19 MK50 DIRECT
SA-8 MK37 BAND C  DIRECT (no sound)
SA-11  MK49 LOFT  (no sound,no RWR Alert)
SA-3 P15 SNR125 MK36 MK37 LOFT
SA-6 MK49 LOFT 

AGM-45 (MODE)
ARM 

20000ft
450knots
Singleplayer (Doesn't work in multiplayer)
spwan with weapons

Aiming at a SAM location with a gun sight then you will see the ^ caret,  pitch up and fire automatically when it is O
 

Edited January 12 by lee1hy

[Lostaviator]

The Shrike seems like it will track a Mig 21 instead of sam radar when Migs are in the area.  Regardless of settings.  Single player and Multi  Anyone else experience this?

[tekrc]

I am also struggling with shrike LOFT deliveries (LABS not WRCS). if I set everything up (telling jester to set the calculations up. but theres no shrike option so substitute mk 82 just to try), and fly to the IP with the mode selector in loft (cockpit settings attached), the missiles launch immediately after holding pickle and does not start the LBAS timer.

In addition there is no option for the shrike in the bombing calculator within LOFT so I'm not sure what Im supposed to pick here that is actually close in drag coefficient.

Edited January 29 by tekrc

[Fliegerkalle]

Does anyone tried to attack a OSA Sa8 ? The mk49  which is defined in manual seems not to work. ? 

[Northstar98]

1 hour ago, Fliegerkalle said:

Does anyone tried to attack a OSA Sa8 ? The mk49  which is defined in manual seems not to work. ? 

The manual is out of date (but I've got an updated table for player and AI aircraft which I will post shortly).

Only the Mk 37 works against the SA-8 (targeting the C-band acquisition radar).

The fire-control radar operates in the J band, above what any Shrike guidance section can target.

[felixx75]

I found that picture:

(this may be correct)

[Northstar98]

As ED have changed some of the radar definitions in subsequent updates and the forum seemingly doesn't let you alter the configurations of tables after the fact (only their contents), here's a new set of tests for the AGM-45 Shrike, testing every applicable ground-based radar in-game.

For these, I've gone through the various .lua definitions of each unit to see what frequency ranges they're actually defined with. These are available here. For units that contain both an acquisition and a fire-control radar, fire-control radars are typically listed as "FrequencyRange" under "LN =", whereas acquisition radars are typically listed under "searchRadarFrequencies".

I've noticed that other guidance sections not in the frequency range track the radar, this is almost certainly a bug. A couple of radars are also undefined (9S86 and RD-75 being the 2 pominent examples).

EDIT: Note that this is accurate for DCS 2.9.12.5336.1, the results as shown below may change in subsequent updates. I'll try and keep this post updated as changes occur.

I've colour coded the guidance sections based on their in-game behaviour, though I may change this to accomodate those with reduced colour perception.

 

For players:

• Guidance sections marked in green provide a tone and ADI steering and track the radar.
• Guidance sections marked in orange don't provide a tone or ADI steering (requiring you to have foreknowledge of the radar's location, as some of these also don't show up on the RWR) but do still track the radar. This is probably a bug.
• Guidance sections marked in magenta provide a tone and ADI steering, but don't actually track the radar. This is probably a bug one way or the other (either they shouldn't provide a tone or ADI steering, or they should track the radar - the latter especially in cases where it applies to intended threat radars for certain guidance sections, such as the Straight Flush with the Mk 49 Mod 0/1).
• Guidance section marked in red don't provide a tone or ADI steering and don't track the radar. This may or may not be a bug (IRL there's more to it than just operating frequencies match = compatible)
• Uncoloured guidance sections are unable to be determined (only applies to the Mk 50 against the SA-15, which cannot be made to track the fire-control radar).

I should also mention that this was tested in single player. Multiplayer may yield different results looking at some reports.

Spoiler

Radar:	System(s) Associated (in DCS):	Frequency Range /GHz:	Radar Band(s) (NATO):	Guidance Sections Corresponding to Frequency Range:	Notes:
USSR/Russia
1L13 Nebo-SV [Box Spring]		0.18 – 0.22	A	None
1RL144 [Hot Shot] (acquisition)	2K22M (2S6M) Tunguska-M [SA-19 Grison]	2 – 3	E	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
1RL144 [Hot Shot] (fire-control)	2K22M (2S6M) Tunguska-M [SA-19 Grison]	10 – 20	J	None
1S11 – 1S91M3 [Straight Flush] (acquisition)	2K12M3 Kub-M3 [SA-6B Gainful]	0.5 – 1	C	Mk 37	Sources contradict (C band or G band), exact version DCS is trying to recreate unknown.
1S31 – 1S91M3 [Straight Flush] (track/illumination)	2K12M3 Kub-M3 [SA-6B Gainful]	8 – 10	I	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1	Sources contradict (H band or I band), exact version DCS is trying to recreate unknown.
1S51M3 SOC/SOTs [Land Roll] (acquisition)	9K33M3 Osa-AKM [SA-8B Gecko Mod 1]	0.5 – 1	C	Mk 37
1S51M3 SSC/SSTs [Land Roll] (track/fire-control)	9K33M3 Osa-AKM [SA-8B Gecko Mod 1]	14.2 – 14.8	J	None	Exact version DCS is trying to recreate unknown
55G6 Nebo [Tall Rack]		0.03 – 0.3	A – B	None
5N59S [Tin Shield-B]	*S-200M Vega-M [SA-5B Gammon], S-300PS [SA-10B Grumble]	2.85 – 3.82	E – F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50	*IRL isn't associated with any version of the SA-5 (EWR or S-300PMU acquisition radar (also seen in use as an acquisition radar for other S-300 variants)).
5N62V RPC [Square Pair]	S-200M Vega-M [SA-5B Gammon]	1.55 – 3.9	D – F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50	Possibly incorrect - most sources state this operates in the H band, centred around 6.66 GHz.
5N63S RPN [Flap Lid-B]	S-300PS [SA-10B Grumble]	8 – 20	I – J	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1
5N64S RLO [Big Bird-B]	S-300PS [SA-10B Grumble]	2.9 – 3.3	E – F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
5N66M NVO [Clam Shell]	S-300PS [SA-10B Grumble]	2.9 – 3.3	E – F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50	Sources contradict each other (either E/F band or I band)
9S18M1 [Snow Drift]	9K37M1 Buk-M1 [SA-11 Gadfly]	3 – 4	F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
9S35M1 [Fire Dome]	9K37M1 Buk-M1 [SA-11 Gadfly]	6 – 10	I	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1
9S80M1 (PPRU-M1) Sborka-M1 [Dog Ear]	Various short-range PVO-SV systems (SA-8, -9, -13, 2S6/SA-19, ZSU-23-4)	3 – 6	F – G	Mk 22, Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 25, Mk 50
9S86 [Snap Shot]	9K35M3 Strela-10M3 [SA-13 Gopher]	Undefined	Undefined	None	Supposedly millimetric band (K band/30 GHz or above)
P-19 Dunay [Flat Face-B]	*S-75V Volhov [SA-2E Guideline Mod 3], S-125M Neva-M [SA-3B Goa], *S-200M Vega-M [SA-5B Gammon]	0.83 – 0.875	C	Mk 37	Unsure why upper end was reduced from 0.882 to 0.875 GHz. *IRL S-75V uses P-12M/P-18, S-200M uses 5N84A/P-14F – P-19 is S-125M acquisition radar or general purpose EWR
RD-75 Amazonka	S-75V Volhov [SA-2E Guideline Mod 3]	Undefined	Undefined
RPK-2 Tobol (1RL33) [Gun Dish]	ZSU-23-4 Shilka	14.6 – 15.6	J	None
[Scrum Half] (Acquisition)	9K330 Tor [SA-15A Gauntlet]	3 – 4	F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
[Scrum Half] (Fire-Control)	9K330 Tor [SA-15A Gauntlet]	4 – 8	G – H	Mk 22, Mk 25, Mk 49 Mod 0, Mk 49 Mod 1, Mk 50	Mk 50 only receives acquisition radar
SNR-75V (PV) [Fan Song-E]	S-75V Volhov [SA-2E Guideline Mod 3]	4.91 - 5.09	G	Mk 22, Mk 25, Mk 50
SNR-125M (UNV) [Low Blow]	S-125M Neva-M [SA-3B Goa]	9 - 9.4	I	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1
SON-9 Grom-2 [Fire Can]	AZP S-60, KS-19	2.7 - 2.9	E	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
PRC:
Type 345	HQ-7B (FM-90) [CSA-7 Sino-Crotale]	10 – 20	J	None
HQ-7B ACU	HQ-7B (FM-90) [CSA-7 Sino-Crotale]	6 – 10	H – I	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1	Known as HQ-7 Self-Propelled STR in DCS. Mk 23 provides tone & steering when it shouldn’t.
US:
AN/FPS-117		1.215 – 1.4	D	None
AN/MPQ-46 IHIPIR	I-HAWK PIP Phase 1	8 – 12	I – J	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1
AN/MPQ-50 IPAR	Patriot PAC-2	0.5 – 1	C	Mk 37
AN/MPQ-53 RS	I-HAWK PIP Phase 1	4.48 – 5.45	G	Mk 22, Mk 25, Mk 50
AN/MPQ-55 ICWAR	I-HAWK PIP Phase 1	10 – 20	J	None
AN/MPQ-64F1 Sentinel	NASAMS II	8 – 12	I – J	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1
AN/VPS-2	M163 VADS	Undefined	Undefined	None	Should operate in the J band (10 - 20 GHz)
Mk 15 Phalanx Block 1B (acquisition)	LPWS (Centurion C-RAM)	12 – 18	J	None
Mk 15 Phalanx Block 1B (track/fire-control)	LPWS (Centurion C-RAM)	Undefined	Undefined	None	Should operate in the J band (10 - 20 GHz)
Germany/FRG:
Domino 3D (track/fire-control))	FlaRakPz 1	8 – 12	I – J	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1	Known as SAM Roland ADS in DCS
Flakpanzer Gepard (track/fire-control)	Flakpanzer Gepard	10 – 20	J	None
MPDR-12 (acquisition)	Flakpanzer Gepard	2 – 3	E	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
MPDR-16 (acquisition)	FlaRakPz 1	1 – 2	D	None	Known as SAM Roland ADS in DCS
MPDR-3002 S	FlaRakPz 1	1 – 2	D	None	Known as SAM Roland EWR in DCS
UK:
Rapier Acquisition Radar	Rapier (initial), Rapier FSA	1 – 4	D – F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50	Possibly operates in the E or F band (2 – 3 or 3 - 4 GHz)? Mk 25 produces tone but no track (unsure if Mk 25 corresponds – G band guidance section)
DN 181 Blindfire FSA	Rapier FSA	10 – 20	J	None

 

For the AI:

• Guidance sections marked in green represent those that track the radar.
• Guidance sections marked in magenta are those that the AI will engage with, but don't track the radar. This might be the result of a bug.
• Guidance sections marked in red are those that the AI won't engage with. This may or may not be a bug.

These tests were done using "search then engage unit", with the AI set to take no reactions to threat, to override attack avoidance decisions and to immortal. With the AI I'd recommend using "search then engage" or "SEAD" (under "start enroute task") and not attack unit/group (under perform task). With attack unit/group, I've noticed that if the AI evaluates that it cannot attack the radar the instant the task is triggered (for instance, due to the radar not illuminating) the AI sometimes drops the task and doesn't engage, even if the same radar illuminates the AI moments later.

Spoiler

Radar	System(s) Associated (in DCS)	Frequency Range /GHz	Radar Band(s) (NATO):	Guidance Sections Corresponding to Frequency Range:	Notes:
USSR/Russia
1L13 Nebo-SV [Box Spring]		0.18 – 0.22	A	None
1RL144 [Hot Shot] (acquisition)	2K22M (2S6M) Tunguska-M [SA-19 Grison]	2 – 3	E	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
1RL144 [Hot Shot] (fire-control)	2K22M (2S6M) Tunguska-M [SA-19 Grison]	10 – 20	J	None
1S11 – 1S91M3 [Straight Flush] (acquisition)	2K12M3 Kub-M3 [SA-6B Gainful]	0.5 – 1	C	Mk 37	Sources contradict (C band or G band), exact version DCS is trying to recreate unknown.
1S31 – 1S91M3 [Straight Flush] (track/illumination)	2K12M3 Kub-M3 [SA-6B Gainful]	8 – 10	I	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1	Sources contradict (H band or I band), exact version DCS is trying to recreate unknown.
1S51M3 SOC/SOTs [Land Roll] (acquisition)	9K33M3 Osa-AKM [SA-8B Gecko Mod 1]	0.5 – 1	C	Mk 37
1S51M3 SSC/SSTs [Land Roll] (track/fire-control)	9K33M3 Osa-AKM [SA-8B Gecko Mod 1]	14.2 – 14.8	J	None	Exact version DCS is trying to recreate unknown
55G6 Nebo [Tall Rack]		0.03 – 0.3	A – B	None
5N59S [Tin Shield-B]	*S-200M Vega-M [SA-5B Gammon], S-300PS [SA-10B Grumble]	2.85 – 3.82	E – F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50	*IRL isn't associated with any version of the SA-5 (EWR or S-300PMU acquisition radar (also seen in use as an acquisition radar for other S-300 variants)).
5N62V RPC [Square Pair]	S-200M Vega-M [SA-5B Gammon]	1.55 – 3.9	D – F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50	Possibly incorrect - most sources state this operates in the H band, centred around 6.66 GHz.
5N63S RPN [Flap Lid-B]	S-300PS [SA-10B Grumble]	8 – 20	I – J	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1
5N64S RLO [Big Bird-B]	S-300PS [SA-10B Grumble]	2.9 – 3.3	E – F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
5N66M NVO [Clam Shell]	S-300PS [SA-10B Grumble]	2.9 – 3.3	E – F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50	Sources contradict each other (either E/F band or I band)
9S18M1 [Snow Drift]	9K37M1 Buk-M1 [SA-11 Gadfly]	3 – 4	F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
9S35M1 [Fire Dome]	9K37M1 Buk-M1 [SA-11 Gadfly]	6 – 10	I	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1
9S80M1 (PPRU-M1) Sborka-M1 [Dog Ear]	Various short-range PVO-SV systems (SA-8, -9, -13, 2S6/SA-19, ZSU-23-4)	3 – 6	F – G	Mk 22, Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 25, Mk 50
9S86 [Snap Shot]	9K35M3 Strela-10M3 [SA-13 Gopher]	Undefined	Undefined	None	Supposedly millimetric band (K band/30 GHz or above)
P-19 Dunay [Flat Face-B]	*S-75V Volhov [SA-2E Guideline Mod 3], S-125M Neva-M [SA-3B Goa], *S-200M Vega-M [SA-5B Gammon]	0.83 – 0.875	C	Mk 37	Unsure why upper end was reduced from 0.882 to 0.875 GHz. *IRL S-75V uses P-12M/P-18, S-200M uses 5N84A/P-14F – P-19 is S-125M acquisition radar or general purpose EWR.
RD-75 Amazonka	S-75V Volhov [SA-2E Guideline Mod 3]	Undefined	Undefined	?
RPK-2 Tobol (1RL33) [Gun Dish]	ZSU-23-4 Shilka	14.6 – 15.6	J	None
[Scrum Half] (Acquisition)	9K330 Tor [SA-15A Gauntlet]	3 – 4	F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
[Scrum Half] (Fire-Control)	9K330 Tor [SA-15A Gauntlet]	4 – 8	G – H	Mk 22, Mk 25, Mk 49 Mod 0, Mk 49 Mod 1, Mk 50	Mk 50 guides on acquisition radar, unable to test if it will guide on the fire-control radar.
SNR-75V (PV) [Fan Song-E]	S-75V Volhov [SA-2E Guideline Mod 3]	4.91 – 5.09	G	Mk 22, Mk 25, Mk 50
SNR-125M (UNV) [Low Blow]	S-125M Neva-M [SA-3B Goa]	9 – 9.4	I	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1
SON-9 Grom-2 [Fire Can]	AZP S-60, KS-19	2.7 – 2.9	E	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
PRC:
Type 345	HQ-7B (FM-90) [CSA-7 Sino-Crotale]	10 – 20	J	None
HQ-7B ACU	HQ-7B (FM-90) [CSA-7 Sino-Crotale]	6 – 10	H – I	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1	Known as HQ-7 Self-Propelled STR in DCS.
US:
AN/FPS-117		1.215 – 1.4	D	None
AN/MPQ-46 IHIPIR	I-HAWK PIP Phase 1	8 – 12	I – J	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1
AN/MPQ-50 IPAR	Patriot PAC-2	0.5 – 1	C	Mk 37
AN/MPQ-53 RS	I-HAWK PIP Phase 1	4.48 – 5.45	G	Mk 22, Mk 25, Mk 50
AN/MPQ-55 ICWAR	I-HAWK PIP Phase 1	10 – 20	J	None
AN/MPQ-64F1 Sentinel	NASAMS II	8 – 12	I – J	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1
AN/VPS-2	M163 VADS	Undefined	Undefined	None	Should operate in the J band (10 - 20 GHz)
Mk 15 Phalanx Block 1B (acquisition)	LPWS (Centurion C-RAM)	12 – 18	J	None
Mk 15 Phalanx Block 1B (track/fire-control)	LPWS (Centurion C-RAM)	Undefined	Undefined	None	Should operate in the J band (10 - 20 GHz)
Germany/FRG:
Domino 3D (track/fire-control)	FlaRakPz 1	8 – 12	I – J	Mk 36, Mk 49 Mod 0, Mk 49 Mod 1	Known as SAM Roland ADS in DCS
Flakpanzer Gepard (track/fire-control)	Flakpanzer Gepard	10 – 20	J	None
MPDR-12 (acquisition)	Flakpanzer Gepard	2 – 3	E	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50
MPDR-16 (acquisition)	FlaRakPz 1	1 – 2	D	None	Known as SAM Roland ADS in DCS
MPDR-3002 S	FlaRakPz 1, Flakpanzer Gepard	1 – 2	D	None	Known as SAM Roland EWR in DCS
UK:
DN 181 Blindfire FSA	Rapier FSA	10 – 20	J	None
Rapier Surveillance Radar (initial/FSA)	Rapier, Rapier FSA	1 – 4	D – F	Mk 23, Mk 24 Mod 5, Mk 24 Mod 34, Mk 50

 

For reference, here's a table of Shrike guidance sections, the frequency range and band(s) they operate in. The guidance sections IRL corresponded to different Shrike versions, a table showing these can be found here.

Spoiler

Guidance Section:	Frequency Range /GHz	Band(s) /NATO	Intended Target Radars:	Notes:
Mk 22	4.8 – 5.2	G	Fan Song-C/E	No angle gating
Mk 23	2 – 4	E – F	Fan Song-A/B/F, Fire Can
Mk 24 Mod 5	2.65 – 3.15	E – F	Fan Song-A/B/F, Bar Lock
Mk 24 Mod 34	2.5 – 3.5	E – F	Fan Song-A/B/F, Bar Lock
Mk 25	4 – 6	G	Fan Song-C/E
Mk 36	7.9 – 9.6	H – I	Low Blow
Mk 37	0.8 – 1	C	Flat Face-A/B
Mk 49 Mod 0	6 – 10	H – I	Low Blow, Straight Flush
Mk 49 Mod 1	6 – 10	H – I	Low Blow, Straight Flush	G-bias
Mk 50	2 – 6	E – G	Various

Edited February 25 by Northstar98
FlaRakRad -> FlaRakPz, added RadarPz TÜR radar name

[Northstar98]

5 hours ago, felixx75 said:

I found that picture:

(this may be correct)

This mostly matches my testing, however:

• SA-13's radar (9S86 [Snap Shot]) is currently inaccurate due to it not being defined (no guidance section should be able to target it). Expect this to change.
• The Mk 23, Mk 24 Mod 5 or Mk 24 Mod 34 probably shouldn't provide a tone or ADI steering for the SA-15TR - that radar operates in the G - H band in DCS, those guidance sections target the E - F band. Possibly expect this to change.
• The Mk 36/49 Mod 0/49 Mod 1 (if they worked), only track the fire-control radar of the SA-6 and the Mk 37 will only track the acquisition radar. If you don't see a 6 on your RWR, the Mk 36/49 Mod 0/49 Mod 1 won't guide.
• SA-5RF - is this the RD-75 Amazonka? If so this belongs to the SA-2 (or at least some versions of it). I'm not sure what guidance sections match the frequency as I'm not sure what frequency(ies) the RD-75 operates at. Possibly expect this to change.
• The Mk 36, Mk 49 Mod 0 and Mk 49 Mod 1 all track the AN/MPQ-46 HIPIR (Hawk TR) albeit without a tone or ADI steering.
• The Mk 49 Mod 0 and Mod 1 probably shouldn't provide a tone & ADI steering for the AN/MPQ-53 RS (Patriot STR) - those target the H - I band in DCS, the AN/MPQ-53 operates in the G band. This is probably a bug, possibly expect this to change.
• The Mk 23 and Mk 50 probably shouldn't provide a tone & ADI steering for the HQ-7B ACU (STR), that radar operates in the I band, the Mk 23 and Mk 50 operate in the E - F and E - G band respectively in DCS. This is probably a bug, possibly expect this to change.
• Rapier surveillance radar isn't on this list (Mk 23, Mk 24 Mod 5, Mk 24 Mod 34 and Mk 50 all track it without a tone or ADI steering), nor is the Roland's track radar (Domino 3D), which the Mk 36 tracks without a tone or ADI steering. The Patriot AMG however is, when it isn't a radar.

Edited February 16 by Northstar98
G - F -> E - F

[Zabuzard]

By the way, the manual is open source. It would be cool if someone puts all the neat stuff into the official manual so every user can benefit from it.
You dont have to wait for a HB employee to do it. The manual is for all of us :)

[felixx75]

2 hours ago, Zabuzard said:

By the way, the manual is open source. It would be cool if someone puts all the neat stuff into the official manual so every user can benefit from it.
You dont have to wait for a HB employee to do it. The manual is for all of us

But if anyone can add something there, how do I know if everything is correct? Shouldn't the manual only contain information and instructions that have been checked and are correct? No offense meant.

[Zabuzard]

But if anyone can add something there, how do I know if everything is correct? Shouldn't the manual only contain information and instructions that have been checked and are correct? No offense meant.

All changes get reviewed and approved by us and SMEs.

The current content is 99% made by us, but it would be really cool if the community contributes and keeps on improving it

[Brigg]

Do the shrikes work in MP now or are they only working in SP still. 

[DSplayer]

On 2/16/2025 at 4:18 PM, Brigg said:

Do the shrikes work in MP now or are they only working in SP still. 

They work in MP. The main problem people have with them in MP is that if the target radar isn't illuminating the rough area where the Shrike is flying, the Shrike won't track it due to lack of sidelobe modeling in DCS. This unfortunately is an issue of all ARM missiles in DCS but it is very easy to see with the Shrike.

Also on another note, it seems my updated Shrike table got pushed so you guys should be able to use an updated manual online.

Edited February 18 by DSplayer

[Solan]

Hey everyone.

Last couple days, I have done some Shrike Training runs on our MP Server and after many unsuccesful attempts with the Mk 49 mod0/1 warheads, i have tried out the Mk 37 on a SA-6  site and that is somehow working. I don't know where the error lies that makes this one work, all i know is i have tone and they are tracking the SA-6 in Loft and Direct. The tone is weaker than with the Mk 49s and Wikipedia says the Radar should have a 2 - 4 GHz band while the seekerhead option in DCS says the Mk 37 is for 0.8 Ghz - 1 GHz.

Also one of the Shrikes hit a Shilka close by (~50 feet), i cannot say whether due to tracking or inaccuracy.

I am going to try out attacking SA-15/3/11 and tell you how that goes. I guess that stuff will all get fixed in the future. but for now:

MK 37 Seeker for SA-6; Tone and tracking.

Mk 24 Mod 5 for SA-15; Very quiet high buzzing noise, tracking

Edited February 19 by Solan

[Northstar98]

2 hours ago, Solan said:

Last couple days, I have done some Shrike Training runs on our MP Server and after many unsuccesful attempts with the Mk 49 mod0/1 warheads, i have tried out the Mk 37 on a SA-6  site and that is somehow working. I don't know where the error lies that makes this one work, all i know is i have tone and they are tracking the SA-6 in Loft and Direct. The tone is weaker than with the Mk 49s and Wikipedia says the Radar should have a 2 - 4 GHz band while the seekerhead option in DCS says the Mk 37 is for 0.8 Ghz - 1 GHz.

The Mk 37 is working because ED defined the acquisition radar (1S11) as operating in the C-band (they've defined it as operating between 0.5 - 1 GHz, which is the complete C-band) - see line 58 here (the frequency is in Hz).

Unfortunately, for this radar IRL sources contradict each other and often use different nomenclature to describe bands, just to provide a few:

• Radartutorial describes the 1S11 as operating in the C-band but doesn't tell us what nomenclature it's using (radartutorial isn't consistent with which one it uses) - though given that the 1S31 is definitely listed using IEEE nomenclature, I'll assume the 1S11 is also listed using IEEE nomenclature. If that is indeed the case, then that would correspond to the NATO G/H-band, or 4 - 8 GHz. Perhaps ED used this, but didn't convert IEEE nomenclature to NATO nomenclature. Most other sources seem to either agree or reference this value.
• Ausairpower conversely describes the 1S11 as operating in the lower X-band (NATO I-band).
• The German language de.wikipedia states the 1S11 operates in the G/H-band but doesn't provide a reference for it.

Given this, this could change (I might make a bug report for it as I've yet to find a source that states NATO C-band for this radar).

The Mk 36 and 49s however produce a tone and ADI steering for the 1S33 (which shows up as a 6 on the radar, the 1S11 shows up as an 'S' requiring your RWR to be in search mode), but don't track - this is almost certainly a bug, especially for the Mk 49s (where the 1S91 is listed as an intended threat radar).

3 hours ago, Solan said:

Also one of the Shrikes hit a Shilka close by (~50 feet), i cannot say whether due to tracking or inaccuracy.

No Shrike should be able to track the Shilka - its radar operates in the J-band which is above what any Shrike guidance section should be able to target. If you do find Shrikes tracking it, that's a bug.

3 hours ago, Solan said:

I am going to try out attacking SA-15/3/11 and tell you how that goes. I guess that stuff will all get fixed in the future. but for now

I've got a table listing every ground-based radar in-game and which guidance section fall within the same frequency band, as defined in DCS. This table can be found here:

[Brigg]

On 2/18/2025 at 7:31 AM, DSplayer said:

They work in MP. The main problem people have with them in MP is that if the target radar isn't illuminating the rough area where the Shrike is flying, the Shrike won't track it due to lack of sidelobe modeling in DCS. This unfortunately is an issue of all ARM missiles in DCS but it is very easy to see with the Shrike.

Also on another note, it seems my updated Shrike table got pushed so you guys should be able to use an updated manual online.

Ok cool. Thanks fella 

[sirrah]

This thread contains some very nice and supportive lists, though for "F4 newcomers" like me, all the info in this thread is quite overwhelming.

Is there a set truth at the moment on which list is 100% accurate?

I've had some good results with this one and I really like how simple and straightforward it is:

Spoiler

I really like the simplicity of this one. Does anyone know if there's a kneeboard version of it? (switching back and forth between VR and pancake is a pita )

[MBot]

I just happened to practice some manual low level loft attacks against SA-6 and SA-8 and made some interesting observations.

I noticed that Mk49 Mod 0 and Mod 1 guide against SA-6 and SA-8 every now and then. Please see the attached track. In the first attack I launch two Mk49 Mod 0 against an SA-6. One of the two missiles guides. In the second attack I launch two Mk-49 Mod 1. Again, one of the two missiles tracks. The seekers were in Loft mode to facilitate a manually executed loft maneuver. Can someone else replicate this?

What is interesting is that when setting up a simple test case (spawn aircraft 5NM above a target, launch Direct Shrikes in active pause and observe tone/tracking), I can 100% replicate the table above. Mk49 Mod 0/1 provide tone against SA-6/8 but do not track. Is the seeker being in direct or loft possible making a difference in its tracking abilities (which would seem like a bug because it shouldn't make a difference)?

Also another observation about the Mk49 Mod 0/1 against SA-6/8. The tone that is produced seems to be related to the search radar (comes on and off at the same rate as the search radar rotates). Shouldn't these seekers be on the tracking radar's frequency though (which should produce a constant tone)?

This whole situation with the Shrikes and the seekers is really unsatisfactory. It is a complex system in the first place, but we can't tell whether something that doesn't work is due to user error or bug. This really needs to be cleaned up and officially documented properly.

SA-6_Shrike.trk

[DSplayer]

On 4/16/2025 at 2:24 PM, MBot said:

I just happened to practice some manual low level loft attacks against SA-6 and SA-8 and made some interesting observations.

I noticed that Mk49 Mod 0 and Mod 1 guide against SA-6 and SA-8 every now and then. Please see the attached track. In the first attack I launch two Mk49 Mod 0 against an SA-6. One of the two missiles guides. In the second attack I launch two Mk-49 Mod 1. Again, one of the two missiles tracks. The seekers were in Loft mode to facilitate a manually executed loft maneuver. Can someone else replicate this?

What is interesting is that when setting up a simple test case (spawn aircraft 5NM above a target, launch Direct Shrikes in active pause and observe tone/tracking), I can 100% replicate the table above. Mk49 Mod 0/1 provide tone against SA-6/8 but do not track. Is the seeker being in direct or loft possible making a difference in its tracking abilities (which would seem like a bug because it shouldn't make a difference)?

Also another observation about the Mk49 Mod 0/1 against SA-6/8. The tone that is produced seems to be related to the search radar (comes on and off at the same rate as the search radar rotates). Shouldn't these seekers be on the tracking radar's frequency though (which should produce a constant tone)?

This whole situation with the Shrikes and the seekers is really unsatisfactory. It is a complex system in the first place, but we can't tell whether something that doesn't work is due to user error or bug. This really needs to be cleaned up and officially documented properly.

SA-6_Shrike.trk 2.22 MB · 2 downloads

I believe the reason why only one of the two Shrikes tracking the SA-6 is due to the 2nd missile being just flying high enough over the target relative to the radar beam of the SA-6 for it to not track.

The reason why the Mk49 Mod 0 and Mod 1 give tone based on the SA-6 search radar (and thus give the associated search pattern period) is because it also gives tone against the search radar even though they don't track the search radar. If you do engage the tracking radar, however, you'll get a constant tone.

 

This incongruence between what tracks and what gives tone is because HB has their own radar frequency values and ED has their own radar frequency values for each radar. Right now some radars, like the SA-6 SR don't have the same frequency/band so you'll get tone against it with the Mk49s even though it won't track. These issues have all been reported already.

Until it gets fixed, the current Shrike table in the manual provides what radars the Shrike tracks against with and without tone.

[Kondor77]

Personally what I've found works best is disregard any of the seeker heads that target Tracking Radars. As already mentioned the radar would have to be illuminating, guiding a missile, and all in the direction of the shrike. Against your likely foes of SA2/3/6/8, I've found the Mk 37 seeker head works much more reliably. For the SA2/3 it will go after the FF search radar. With that out of the way the site becomes much easier to then clean up with some iron bombs. The Mk37 will also guide on a searching SA6 and SA8, no need for either of them to be actively guiding a missile.

[SloppyDog]

On 1/28/2025 at 10:58 PM, tekrc said:

I am also struggling with shrike LOFT deliveries (LABS not WRCS). if I set everything up (telling jester to set the calculations up. but theres no shrike option so substitute mk 82 just to try), and fly to the IP with the mode selector in loft (cockpit settings attached), the missiles launch immediately after holding pickle and does not start the LBAS timer.

In addition there is no option for the shrike in the bombing calculator within LOFT so I'm not sure what Im supposed to pick here that is actually close in drag coefficient.

I found the exactly same problem.

I tried with the bomb computer and no joy. I tried manually inputting the data (release Low Angle; pull-up time; release time) in the WSO station, and no joy.
I believe that the computer didn't accept my inputs, since I was going by trial and error. I really don't know how to manually calculate the latter two parameters.

Anyway, what I'm doing with this mode is to help me engage pre-planned targets. I created this SAM site with an SA-2 and an SA-3 and assorted AAA protecting an airport. The SA-3 is easily defeated with WRGS in loft mode. The problem is the SA-2, with its long range.

The best way to defeat this situation was to use LABS mode, setup an IP and the TGT in the Mission Editor. I get very low, at around 500-1000 feet, pass the IP at 20nm from the target, do not push the pickle, otherwise as stated the missiles will be immediately fired. Jester will automatically change to the next waypoint, the TGT, and will start to call out the distance. Once at 16-15 nm, I pop up nose up 30 degrees, fire the missiles then go mid altitude to provide a target. Usually the Shrikes track the target. Closer, they will overshoot the target.

This way I've been able to use LABS mode to loft missiles, with an indication of distance and not being dependent of the WRGS system.

It is the only way LABS mode has been working for Shrikes. Not even close to what is done with bombs or to what is written in the manual.