Search the Community

Hi everyone, A long standing request of mine and one I hope you'll all agree with - please include empty air defence sites, suitable for placing units in. Ideally, we'd get a close to 1:1 recreation of the real sites, in their real locations. The closest example I can name in DCS is this example of an Egyptian S-75 site, which is an almost 1:1 recreation of the real thing and is the exact thing I'm talking about. However, even if Ugra were to pick a generic HAWK layout, an S-75/SA-2 site layout, an S-125/SA-3 site layout and an S-200/SA-5 site layout, then copy and paste them in the right locations across the map, that would definitely be better than nothing and would absolutely suffice. There's plenty of resources out there for finding where each one goes and most are still clearly extant in modern satellite imagery (many of the sites have however been converted, but historical imagery is still readily available). Just for some examples: Here's a HAWK site near Fulda, circa 2009. Everything about the site is clearly visible, including launcher and radar positions, revetments etc. In present day imagery it seems to be some chemical/POL facility. Here's a NIKE Hercules launch site near Arnshöfen. In present day imagery all but the western launch position has been dug up, but in historical imagery (such as this from 2008), everything is clearly visible (though note only the western launch position has its storage shelter visible, they're removed from the other positions, though where they would've been is clearly visible). The IFC site is located on top of a hill, in a forest to the north-west (and is empty save for a tower) - there's even a shot of the IFC site from a drone. Here's an S-75/SA-2 site just south of the large Wittstock Bombing Range. Unlike most imagery, these site shows everything (the central revetments for the FCR and associated equipment, the 6 launcher revetments arranged in a circle centred on the FCR, as well as other reveted positions for the acquisition radar and other equipment). If this was copied and pasted at every SA-2 site, this is would be perfect. Here's an S-125/SA-3 site adjacent to Storkow, close to Templin airbase, here's another historical image, again clearly showing the layout. Everything is clearly visible. Here's another near Möckern, again everything visible. This site appears to be defending an S-200 site in the forest to the east. Here's an S-200/SA-5 site just south-east of Gransee, to the north of Berlin. Everything about the site is clearly visible - the 2 launch battalions (with central launch control centre (which would have generators and power distribution), with 6 launch positions each. The technical batallion to the east, and to the north, the guidance area (with positions for fire-control and acquisition radars). Here is where an S-300PMU/SA-10B sie would've been, immediately to the west is an S-75/SA-2 site. Here's a 2K12/SA-6 site to the south of Erfut. This site is mostly just roads, but there are a couple of reveted positions (you can see the 4 positions for launchers in a rectangular shape, with a 5th inside the rectangle for the Straight Flush. In the development screenshots, there's this image: I'm almost certain that this is Damgarten (an airbase the MiG-29S has a livery for). This airbase has an S-125 site immediately adjacent to it. It's most visible in this image (the grey object is where the FCR and associated equipment would've been located and there are 4 circular revetments for the launchers to the west, though the southern one is only just visible, but nonetheless there are 4), EDIT: here's an image showing the site (3). There's also another site near Saal to the north-east, which this site has historical imagery of. Unfortunately however, the former site seems to be absent in this screenshot. Previously, on the Syria map, Ugra did take a crack at doing some air defence sites, though only really so with the SA-2/S-75 and while the revetment models were perfectly accurate, the site however wasn't (only 5 launcher revetments - should be 6, no revetments for radars or other equipment). I've attached SAMSiteOverview.kmz by Sean O'Connor of IMINT & Analysis below, which can be used to find just about all sites (though is missing British Bloodhound and Rapier sites). SAM Site Overview.kmz

So, I'm doing some SAM testing. General stuff like evaluating ranges of different systems, hit probability, rocket motor burn times and so on. I'm still collecting data, but I am having trouble getting the HAWK (Currently using the Iranian Hawk Template) to change engagement ranges. When I set the engagement range to 100 (default) the system launches on my target aircraft at almost exactly 24 nautical miles. When set at 90%... it engages at 24 nautical miles... I'm working to optimize the system to get higher probability of hits. Currently I'm testing with targets at 40,000 asl. (Battery located at 215 asl), however the system is engaging targets at the same range as when my target drones were flying at 20,000 asl. The SAM has "excellent" skill level and I'm doing the testing on a big flat part of South America so there won't be any mountains to block the radar signals. Anyway, it would be helpful to know if I'm doing something wrong, or the restrict range order doesn't work, or what. Thanks.

Hi everyone, Something that's bugged me is that the variant of the I-HAWK seems to be quite inconsistent: We have a missile designated MIM-23K (i.e. the Enhanced Lethality Missile), from the mid 1990s and belonging to I-HAWK PIP Phase 3 systems. We have a HIPIR that's designated AN/MPQ-46 (IHIPIR) - this is from the I-HAWK PIP Phase I from the late 1970s (which fires the MIM-23B missile). However, the 3D model actually depicts a HEOS-equipped AN/MPQ-57, which is from the I-HAWK PIP Phase 2 from the early-to-mid 1980s (which fires the MIM-23C/D missile), as operated by Norway, the Netherlands and Germany. We have a CWAR designated AN/MPQ-55 (ICWAR), which is from the I-HAWK PIP Phase I and II. The remaining radar, the AN/MPQ-50 IPAR is accurate to Phase 1, 2 and 3 systems, so it's accurate regardless. So, from that, we either have: An I-HAWK PIP Phase I, with the correct designation for all the radars, but the HIPIR has the wrong model and the missile has the wrong designation (but otherwise, aside from issues with its flight model, appears to be aligned with Phase I capabilities). An I-HAWK PIP Phase II, with the correct designation for 2 of the radars and the right model for the 3rd (but which has the wrong designation) as well as a missile that's also designated incorrectly. An I-HAWK PIP Phase III, with the correct missile designation and the right PAR, but the HIPIR has the wrong model and lacks the low-altitude multi-target engagement capability, while also lacking anti-TBM capability and lacking the radar used for said anti-TBM capability (AN/TPS-59(V)3). For the PIP Phase I, all that would need correcting is to rename the missile to MIM-23B and to remove HEOS from the AN/MPQ-46 and we'd have an accurate PIP Phase I (see here for what an AN/MPQ-46 should look like, compared to a HEOS-equipped AN/MPQ-57 (what we have in-game). a TAS-equipped AN/MPQ-57 is externally identical to the AN/MPQ-61 (see below) but withouth the boxy LASHE antenna seen on the left of the image (adjacent on the right of the transmitting antenna)). For the PIP Phase II, we would need the missile renamed to MIM-23C (or D) and the HIPIR renamed to AN/MPQ-57 IHIPIR or AN/MPQ-57 IHIPIR [HEOS] or something. The only thing here is that the main upgrades of the system were in ECCM capability - not only does the missile have improved resistance to jamming, but the HEOS (or alternatively the OD-179/TVY TAS, which is day-only) allows for passive angle tracking, defeating angle deception jamming (both the Phase I and II feature range-only radars to provide ranging when the HPIR cannot measure it). Right now, HEOS isn't defined as a sensor and ECCM capabilities (especially relating to angle deception jamming) isn't really relevant to DCS as it currently stands, without a substantial EW overhaul. For the PIP Phase 3, the HIPIR and CWAR would need to be redesignated. The HIPIR should also have the LASHE antenna added and HEOS replaced with I-TAS (see here for an image of the AN/MPQ-61) and given the ability to engage multiple targets (up to 12) at low altitude wthin a certain area. Though I'm not sure what the parameters of that "certain area" is. If ED were to give the MIM-23K the anti-TBM capability it should have, then the AN/TPS-59(V)3 radar should also be implemented. This though was only a thing for the USMC (at least as far as US operators are concerned).

Here are a very few of the photos I took at the Battle of Britain Air Show at Duxford over a weekend in 2018. It rained on the Saturday but Sunday the sun turned up. I hope you like them?

I just made a super rough AIM-23 Hawk mod for the F-14 Tomcat. Link to mod: https://www.digitalcombatsimulator.com/en/files/3323002/ Changelog: V1.0 - Initial Release V1.1 - Fixed missile pylon positioning (Huge thanks to Redounet for some help in initially fixing the issue), Missile accuracy increased (I had previously used the values from the SAM missile files but it made the missile miss pretty badly. V1.2 - Increased CCM ability and removed the need for a separate AIM-23 EDM file. V1.2A - Updated luas to OB 2.7.15.26783 V1.3 - Updated luas to OB 2.7.16.27869 (includes latest AIM-54 updates), added PN to the AIM-23, and added an appropriate white and red AIM-23 texture courtesy of bennyboy9800. V1.4 - New file structure that no longer requires an update after new patch drops which changes Weapons.lua (less work for me yay) V1.5 - Updated for OB 2.7.17.29493. V1.5.1 - Zipped with OvGME so you can just drag and drop the zipped mod into your DCS mod repo (zipped folder no longer has the version number in filename). V1.5.2 - Updated for OB 2.8.3.37556. V1.5.3 - Drag increased on the AIM-23, HB weapon loadout limitations added. V1.5.4 - Updated for TARPS and other changes made in previous OBs. V1.5.5 - Hotfix to actually make the TARPS usable. V1.5.6 - Updated for latest DCS patch (as of 2024-03-05) V1.5.7 - Updated for 2.9.6.57650 V1.5.8 - Updated for 2.9.9.2406 V1.5.9 - Updated for 2.9.14.8222 | Updated AIM-23 FM to match new MIM-23 FM.