Northstar98

Yep:

Not really sure the HARM should be able to engage those radars. Both the 1L13 and 55G6 are VHF radars, in DCS the 1L13 is defined as operating between 180 - 220 MHz and the 55G6 between 30 - 300 MHz According to this, the AGM-88 (or at least the AGM-88B) has a conical spiral antenna (spirals are fairly common in ARM designs). The lowest frequency a conical spiral antenna can targhet is related to its base (outer) radius. The same source states that the HARM can target the C to J bands - those radars operate in the A band and A-B band (just) respectively. I'm not entirely sure of the equations that determine the minimum frequency of a conical spiral antenna, but for a planar spiral antenna it's fmin = c/2πr2 where r2 is the outer radius: In order to target 220 MHz, r2 would have to be at least 0.434 m and to target 300 MHz, it would need to be at least 0.318 m (and bear in mind, that's the upper limit of where these radars operate, at least as defined in DCS). Those outer radii correspond to a diameter of 0.868 and 0.636 m respectively - the HARM has a fuselage diameter of only 0.254 m (and the seeker is even smaller still) - it simply isn't big enough to fit a conical spiral antenna big enough such that it can operate at the range these radars do.

Just an addendum to this now that the fusing update is in. Can we get a selection for the green thermally protected Mk 82, Mk 82 Snake Eye, Mk 83, GBU-10, GBU-12, GBU-16 and GBU-31(V)2/B? The textures are already there, we just can’t select them. Right now we can only select between USAF non-thermally protected and USN BLU-11x series, we cannot select USN green thermally protected Mk 8x series bombs/warheads. As for the GBU-32(V)2/B, it seems to have began low-rate initial production circa 2002, the green may have still been in circulation according to the OP (and the green texture does exist for the Mk 83) the GBU-38(V)2/B IOC'd in 2005, so the green is probably inaccurate for it.

You're right that the GBU-32(V)2/B is exclusive to the USN and USMC, but there is a green thermally protective coating, which was in use before being superceded by the grey. AFAIK the olive-green coating was used with Mk 8x series warheads and the grey coating (with 3 yellow stripes) is used for the BLU-111, BLU-110 and BLU-117 (500 lb, 1000 lb and 2000 lb respectively - all essentially identical to the Mk 82/83/84, but are filled with PBXN-109 insensitive explosive as opposed to trinotal). A JDAM with a green coating and a Mk 8x series warhead can be seen in this image.

Hi everyone, In the new (albeit non-functional) payload selection for the Arleigh Burke, the RGM-109C is called BGM_109B: The BGM-109B is the legacy designation (apart from the BGM-109G Gryphon, all BGM designations were designated to RGM (surface ship-launched) and UGM (submarine-launched) after 1986) for the TASM or Tomahawk Anti-Ship Missile. What we actually have in DCS is the RGM-109C Tomahawk Block II/III (should be III) TLAM-C, which is the conventional land-attack version. As such, this should be renamed to "RGM-109C Tomahawk Block III TLAM-C" as this is what the missile actually is/should be. See this for further reading.

Hi everyone, The 5N62 RPC [Square Pair] FCR for the S-200M system seems to be defined with incorrect frequencies. It's currently defined as having a frequency range of 1.55 - 3.9 GHz, which is in the D - E band. See line 80 of the .lua. Online sources state that this radar actually operates in the 6.0 GHz band/H band, possibly centred around 6.66 GHz / 4.5 cm. Source 1, source 2, source 3, source 4

Reproduced with multiple radars and multiple guidance sections - the only thing that seems to be working are the Shrikes themselves when launched and the AoA indexer lights when using the Shrike's WRCS mode distance readouts on the HSI. EDIT: At least some radars and guidance sections are unaffected - for instance the Mk 23, Mk 24 Mod 5, Mk 24 Mod 34 and Mk 50 against the SON-9 produce the aural tone and have the flight director function more-or-less as expected. The tracks below however show that the Mk 22, Mk 25 and Mk 50 against the SNR-75V has the flight director only showing waypoint steering and no aural tone (the only thing being the distance readout) and similar for the Mk 36, Mk 49 Mod 0 and Mk 49 Mod 1 against the SNR-125M. AGM-45A_SNR-75V_Mk22_WRCS.trk AGM-45A_SNR-75V_Mk25_WRCS.trk AGM-45A_SNR-75V_Mk50_WRCS.trk AGM-45A_SNR-125M_Mk36_WRCS.trk AGM-45A_SNR-125M_Mk49-0_WRCS.trk AGM-45A_SNR-125M_Mk49-1_WRCS.trk

As of DCS 2.9.9.2280 new helipads have been implemented. However, at least some of them seem to be fictional. In this case it's somewhat disappointing as the actual helipad at Fox Bay is still unusable:

Yeah, the lack of Iranian airbases is a deal-breaker for me.

Yes to all of the above. It doesn't appear in the mission editor It doesn't appear on AI aircraft It doesn't appear on player aircraft when starting with them already equipped It doesn't appear on player aircraft when rearmed via the ground crew AI_F-4E_AVQ-23FT_rack.trk AI_F-4E_ALQ-131_rack.trk AI_F-4E_AVQ-23_rack.trk F-4E_AVQ-23_ALQ-131_rearm.trk F-4E_AVQ-23_ALQ-131_rack_rearm.trk F-4E_AVQ-23FT_rack.trk F-4E_ALQ-131_rack.trk F-4E_AVQ-23_rack.trk

Hi everyone, Super minor bug - the new models for the RIM-66M SM-2MR Block IIIA and RIM-156A SM-2ER Block IV have inverted animations for their control surfaces (e.g. when the missile pitches down, the control surfaces deflect so as to pitch the missile up). Incidentally, the nozzles Mk 72 booster for the RIM-156A doesn't appear to be animated (IRL this booster features thrust vectoring) and unlike the SM-2s, the SM-1's control surfaces don't appear to be animated in-game (the missile doesn't even appear on the launcher before it's fired). RIM-66M_controlsurfaces.trk RIM-156A_controlsurfaces.trk

Doesn't look like it - the missions I used to create the tracks here now consistently produce "marked by laser" callouts with lasers being fired.

I have indeed rechecked recently, all the issues in that particular post have now been resolved and have been for several months. The only issue now present (at least from my testing) is the AGM-45 against the SON-9 and AN/MPQ-64F1 - the AI makes no attempt whatsoever to even engage either radar. Please see this post for tracks, further up this thread. Note that this problem is not that the Shrikes don't track - the problem is the AI refuses to engage in the first place. Heatblur have implemented a workaround which appears to have resolved the issue with the GBU-8 not dropping without Pave Spike, so that can be considered resolved.

Hi everyone, Could we get the newly implemented RIM-156A SM-2ER Block IV implemented on the Ticonderoga (preferably alongside the loadout editor)? There's much more historical precedent for adding the SM-2ER to the Ticonderoga than there was for the Arleigh Burke.

That would be nice, but unless there's plans to give the Arleigh Burke RIM-162D ESSM Block 1 (which, they should be - the liveries they have depict ships that are definitely new enough to receive it) the single missile per cell is accurate.

Reproduced

The changelog was updated on the forum (though looks like it hasn't been updated on the main website) to include the Heatblur changes. The instant action missions listed in the OP are definitely in, as is the CBU-99 (the rest I haven't tested yet).

That option isn't available for the Forrestal (or any other vessel), only CVNs 71-75. Though I'm guessing that's the issue as that setting seems to default to off (i.e. disallowed).

Nice changelog, though one thing I was hoping would be fixed by now is the AIM-7E and E-2 Sparrow models, which was first reported just over 5 months ago - it's a fairly trivial change to CoreMods\aircraft\F-4E\Entry\Weapons.lua to fix both missiles (the AIM-7E-2 appears as an E before launch and both missiles turn into AIM-7Ms post-launch).

It looks like a couple updates back broke the LSO position - it's no longer accessible despite still being defined in the .lua.

This doesn't seem to have made it in, I'm unable to place any of the weapons with TARPS - for both the F-14A and B.

One of the problems here is that the launchers the Condells have is for MM40 Exocet Block I - not Harpoon. Exocet launchers are less inclined than the Mk 140/141 launchers of the Harpoon, which may impact its ability to climb. Unless of course the booster isn't developing as much thrust as it should be.

I mean, so long as the radar can track the target and the missile (or alternatively, the operators can track the target manually with the 9Sh38) it can engage anything that's within the missile's capability to hit (though in any case, engaging low-observable weapons, even those with a low LOS rate is quite the ask for the operators to acquire). FWIW, and it really is a pedantic hang up as I guess it doesn't make much practical difference (after all, the sensors and FCS are the same AFAIK, the missiles are the main change), but the SA-8 variant from the early 70s looked like this: Our one has a missile with 9M33M3 written on the side of it, meaning we should have the 9K33M3 Osa-AKM [SA-8B Gecko Mod 1], which is from 1980. This also tracks with the IFF interrogation antenna atop the SOC antenna, which is a more frequent configuration compared to previous versions.

Just as an addendum, you no longer need to jump amphibious vehicles onto the decks of ships as will now (well, not sure when it was added) spawn up on deck as expected. However, the placement restrcitions still mean we're limited to amphibious units - we cannot for instance, place MANPADS onto ships, or infantry. If this was extended to aircraft, we could hypothetically place client/player aircraft wherever, instead of being limited to the current system, which offers little to no control over where aircraft spawn (unless spawning from a catapult) and IMO is overly restrictive and limited.