Whiskey11

I'll be adding some additional details in the future. Looking at the week of 21 January for an update since I took the week off from work. As far as doing it for ALL SAMs in DCS, it'll be challenging because certain SAMs don't behave like they do IRL. Patriot. PAC 1 is a TVM system IRL (like TWS but SARH to impact vs ARH) while in game it is basically SARH. S-300, depending on variant is either SARH, TVM, or ARH/TWS... etc. I'd love for DCS to better represent SAM threats... for people like me who obsess over SEAD/DEAD, I've grown very accustom to the quirks of our current SAMs to where I'm nearly bored of the mission set because it is so easy!!!

It is, however, a track radar. It provides track file information for ground based TWS shots using the AIM-120 and is used for target cueing when AIM-9's are used. You wont get a track warning because it operates exactly like an aircraft radar in TWS. At least, that is how it acts in DCS World. While the range of the system is very low as we have it, you can absolutely see mid course guidance updates, like in TWS, before the missile goes active at ~10nmi. It's about a 2-4 mile window to see the behavior, but it is definitely there.

Considering they've said they both would like to build one of they can get sufficient documentation for it AND said they are in the process of gathering information for one, I don't think it's too unlikely they'll build one eventually. With the IRST being classified, the best we can hope for is an approximation of its capabilities. HB would have to move from needing absolute documentation to "Suspension of Disbelief" on the capabilities. Between statements made on the F14 Tomcast, and the info which is currently available on it, you may be able to do exactly that. I think it is far far far more likely we see a B Upgrade with PTID/EGI before any D though.

DEAD is the best job to have in the Viper! :P. Only reason I fly it! No reason to do SEAD anymore when you can DEAD that site into oblivion!

I hadn't, but I'll look into adding it!

The SA-10 has a blindspot below 50 feet AGL relative to the height of the Flap Lid radar. Low, nap of the earth run ins with a popup attack around 10nmi with CBU-105's will nearly always guarantee an SA-10 kill and survival of the Viper. Doing it right: 1.) Find the SA-10 on the TGP using the HTS 2.) Create a mark point for it 3.) Set the mark point as the waypoint 4.) Run in with TGP up, CBU-105's warmed up. 5.) Around 12-10nmi (depending on terrain) start a 25 degree pop up attack 6.) Point track the Flap Lid when you can see the base of it 7.) Release when in zone, turn and burn for the ground 7.) Exit the threat area low and fast This is so boringly effective, especially with terrain masking, that it's almost the least fun way to do it. Even with SA-15's defending the site, it's VERY consistent. It even works against the High Digit SAM Mod and S-300 Pack's various S-300's and S-400's. It works over water as well. It basically always works. If the SA-15's are more.... aggressively placed, you may have to blaze a trail in to the SA-10 by taking them out FIRST. Once you are used to these pop up attacks using the CBU-105, the SA-10 and SA-5 become some of the easiest to kill SAM sites... well... they are all easy to kill this way, but the shorter range stuff ends up being VERY spicy because of how quickly the missiles get to you relative to the longer range SAMs. I've attached a Tacview of this tactic being used on TWO nearly co-located SA-10 sites during a Liberation Campaign. Enjoy! Liberation2xSA10Kill.acmi

I'm guessing the solution is to just make the Grill Screen and Grill Pan the same radar on the back end? From memory, the tracking type (TVM, SACLOS, etc) is all set in the weapon file and not the sensor file. Of course the REAL solution is for ED to finish the HARM tables and allow outside mods to reference an emitter... that would be like pulling teeth though....

No worries, is there a place I can help with the solution in the coding? I've poked around the files to see if I could figure it out on my own, but if you know where ED's HARM stuff ties into HDSM, I'll gladly take a look.

I gave some thought to that and decided to mark the HDSM kneeboards with HDSM in the upper left hand corner. It'd be easy enough to go through and delete the HDSM SAMs from the folder as a stop gap. The correct folder should be "A-10C_2" without the quotes. Check the folder name first. It should also be the Save Games Kneeboard folder.

No Problem! You too! No Problem! If you guys have comments on how to improve let me know! Some suggestions from here and userfiles which I'll try and implement for next "release:" -PDF of kneeboards -ZIP file instead of RAR file -Country of Origin/Faction -SA-21 and SA-22 Cards (From S-300 Pack, not to be confused with HDSM, I suppose! :P)

I'll look into including a PDF in the future. Will have to do some research into how first, but it shouldn't be too hard. Do you want each one individually as a PDF or all of them in one as a PDF? As for Ordnance for aircraft in DCS, the largest list of DCS ordnance I've ever seen is on Air Goons: https://www.airgoons.com/w/DCS_Reference/Stores_List A lot of people use HARMs for SEAD in the Viper, or CBU-105's and GBU-38's for DEAD to take out the site and track radars. Pretty much any air to ground weapon can be made to work for taking out SAM sites. Some are significantly better than others. My go to weapon of choice is the CBU-105. It's GPS guided, has decent glide capability, and takes out a large chunk, if not all, of most SAM sites. The GBU-38 is a little more precise in that it can only effectively engage one part of the site at a time (hopefully the track radar first! :P).

No problem! You too! Let me know if you have any suggestions for future updates! Have a couple already from comments over on the User File side.

I realize the S-300 Pack is it's own work, but is there any plan on incorporating it directly into the High Digit Sam Modpack? It seems like HDSM and the S-300 pack would make more sense as one package than as two separate packages. EDIT: Any luck getting a HARM onto the SA-23 Grill Screen/Grill Pan Track Radar? HDSM has an issue where the HARM code for the Grill Screen/Grill Pan doesn't work for the SA-23 but does for the SA-12.

Howdy Folks, just finished uploading a new version of my SAM Threat Guide for DCS to the User Files and thought I should share it with you all. This is a kneeboard with all the information you could need to successfully SEAD/DEAD any SAM site. It includes the obvious stuff like names, ranges, altitudes, and HARM codes. More importantly, it includes pictures of the important bits of the SAM site, including the track radar and which one you should prioritize. There is also a small section which shows the common layout of a SAM site based upon their real world layouts. Example Kneeboard Card: DOWNLOAD LINK: https://www.digitalcombatsimulator.com/en/files/3331424/ ===================================== INSTALL ===================================== Install into your desired aircraft's kneeboard. Generally your kneeboards are in C:\"Your User Name"\Saved Games\DCS.openbeta\Kneeboard\"Aircraft Type". If the folder doesn't exist, create it! Example: C:\Whiskey11\Saved Games\DCS.openbeta\Kneeboard\F-16C_50 for the F-16C kneeboard location. Enjoy! ===================================== Known Issues & Roadmap ===================================== Version 2.1's TPOD pictures got distorted somehow. Hope to address this at a later date. Still need to get around to doing the Avenger/VADS/Linebacker and other BLUFOR SHORAD... I'll probably end up throwing the MANPADS into a single page, but haven't decided yet. ===================================== Credits ===================================== Information about range, and altitude for the various SAM's came from four sources. Hoggit's Threat Database (mostly stuff pulled from in game files), the Air Goon's website, and directly from the DCS LUA Datamine files and the High Digit SAM Mod LUA Files. Unless ED comes outright and gives us these numbers, this is "as good as it gets" for numbers in game. The amount of testing required to confirm these numbers is out of my ability, time wise. ===================================== Version History ===================================== V1.0 - 18 October 2022 -Basic SAM Threat Information Kneeboard. Missing Rapier SAM system, Roland, and all MANPADS. Also missing the SPAA which don't have missiles. V2.0 - 14 December 2022 -Added High Digit SAM Mod (HDSM) SAMs (S-300PS, S-300PMU, S-300PMU-1, S-300PMU-2, S-300V, S-300VM, and 9K317 Buk-M1-2) to guide -All HDSM SAMs will have "HDSM" in the upper left corner of the page -SA-23 Gladiator/Giant's Grill Screen Track Radar does NOT have a HARM Code due to DCS Limitations (please help pester ED about this!) -All HARM Codes and RWR symbology has been checked in F-16C and are accurate. SA-10 and SA-20 variants show up on HTS Pod. -Added Countermeasure Type -Added Common Site Layout -Added Rapier System -Added MIM-115 Roland ADS -Added track and search radar RWR codes -Added Russian Names to the NATO reporting names. NATO names are on the left, Russian names on the right. V2.1 - 16 June 2023 -Added NATO Threat Table Numbers -Added SA-17 Point Defense Message -Fixed SAM Ranges for DCS Core SAMs from the LUA Datamine -Fixed Certain SAM layouts (SA-5, HAWK, SA-11, and SA-17) -Fixed SA-17 Radar Name (Changed from Fire Dome to Chair Back) Feedback always appreciated!

Halloween Continues: Ghostly pilot is ghostly! So far, loving the pilot body!

So I was messing around with the SA-23 and HARM codes since I'd like to run this in a Liberation campaign... the previously stated HARM codes for the SA-23's Grill Pan Track Radar are not working. I have written down: Bill Board: 105 (Correct) High Screen: 106 (Correct) Grill Pan: 112 I can't seem to get a Prebriefed HARM with that code to track onto the Grill Pan. I'm also not able to get a HARM onto either the Tombstone or Gravestone track radars using the Flap Lid code. Same with the one listed as "SA20 Track Radar"

Hey BIGNEWY, there hasn't been any replies to any of the new evidence presented here. Understand, we are not talking about DTOSS, but lofting GBU-38's and GBU-31's and the DLZ showing in range, but not actually being in range. Can you please reexamine the new posts? Thanks!

The CBU-105 responds correctly to the staple. Launches at the top of the staple achieve consistent hits, although I generally wait until I'm well within on the CBU-105. I generally DO with the GBU-38 as well, but that's not the point of this thread! I've attached a Tacview of the CBU-105 launched at the top of the staple on the same test miz. I didn't save the track file unfortunately. I guess I could go and get one if one is really necessary for the CBU-105 working correctly and the GBU-38 not. Tacview-20220920-142214-DCS-testSEAD.zip.acmi

The assumption isn't that a JDAM can be lofted to the same range as a dumb bomb. The assumption is the computer knows the impact point, it knows the flight profile (otherwise how would we have a LAR to begin with?) and it knows your own aircraft's metrics... it absolutely can calculate the max acceptable launch range given the parameters available to it at the time of release. That's the point of CCRP bombing. JDAM and other GPS guided weapons have an advantage in that you can launch those at a much wider array of ranges due to having the ability to guide, but the Staple being flat incorrect on the HUD is the issue. It's not even giving the correct LAR AT ALL, to the point of being over 1.5nmi wrong, in a loft situation. In reality though, the issue is that the staple is so wrong, that even drops well within the staple (such as the second released JDAM) still fall well short in spite of being well within the staple... An issue which IS NOT present when lofting a CBU-105, another GPS guided weapon... for some reason.

I'm not trying to force this into a dive toss mode... I'm merely pointing out the in range staple is incorrect when lofting JDAMs in popup attacks in PRE mode. I find it really difficult to believe the Fire Control Computer in the F-16 can calculate the correct loft geometry for a dumb bomb but suddenly loses that ability with a guided munition using the same bomb body and guidance fins. Ironically enough, the CBU-105 does not suffer from this issue and the staple on the HUD is correct when lofting in nearly the same exact scenarios in spite of being significantly more draggy.

Greetings ED and team, I come to you with a bug which may or may not have been reported. Didn't see a post for it. One of my favorite routines for addressing high threat SAM's like the SA-10 are pop up attacks using GBU-38's. Nothing like a high adrenaline low altitude rush, followed by a pop up attack to get the SAM operator's asleep at their stations!! The problem comes from lofting GBU-38's and GBU-31's. The JDAM launch zone indicators do not accurately represent the weapon energy potential. Specifically, when performing these bomb tosses, the weapon release staple shows you are within parameters for a weapon release and the weapon will come off the station, however it will fall VERY short if launched at the upper end of the staple. These weapons are being launched with the default profiles in the SMS page and in PRE mode. CBU-105's don't seem impacted by this. Track files and Tacviews attached. In both the GBU-38 and GBU-31 cases, the first bomb is released just under the top of the staple. The next bomb is released with 2,000 feet more altitude. Aircraft speed is around Mach .9 to Mach 1 at release. Altitude is usually around 6k feet on first release and about 25 degrees nose up pitch. Range is between 12nmi and 14nmi. Computer Specs: 9900k OC'd to 5GHz 32gb DDR4 3400MHz 3090Ti DCS Installed on NVME SSD Reverb G2 TM Warthog TM TPR Running the latest OpenBeta GBU-31Toss.acmi GBU-38Toss.acmi GBU-31Toss.trk GBU-38Toss.trk

Clear. Did the track I send you show a specific set of circumstances which caused the crash?

Hey BIGNEWY, was there anything in the track file which showed a set of circumstances we can test on our end to get shorter tracks? Or any other way we can help reproduce this and narrow it down?

I'll PM you with a Google Drive link!

Greeting ED and the F-16 team! Today, 06 September 2022, I was playing a Liberation Campaign with the 107th JAS. There were EIGHT F-16's in the mission. Four were on CAP, the remaining four were tasked with SEAD/DEAD. During the Mission, SEVEN of the F-16's had hard crash to desktop with ED Error Reporting popup. The seven crashed at EXACTLY the same moment during the mission. The eighth was able to finish the mission and land. I've attached the DCS Crash logs... myself and another F-16 pilot had the same crash after F-16C.dll was accessed. The track file is 43mb and can't be attached.... =\ I'll gladly send the track file via a Google Drive link upon request. The only thing we can think of is the surviving F-16 tried sending a datalink mark point to the other SEAD/DEAD F-16. As for my PC Specs: -9900k OC'd to 5GHz -3090ti -32gb of DDR4 PC3400 memory -DCS is installed on an SSD I'm playing in VR (HP Reverb G2). We tried "repeating" this with just two Vipers, but were unable to, at least with the whole thing being suspected datalink mark point transmission. dcs.log-20220907-015311.zip