Whiskey11

If your goal is realism, adding a Russian Army unit (SA-19) to a Russian Air Defense unit (S-300PS/SA-10B) is highly unrealistic. I have never seen a point defense unit parked at an S-300/S-400 battery in real life. Pantsir is allegedly deployed with S-400 batteries... I say allegedly, because once again, I have yet to see one deployed in such a manner... for sure Army units (any point defense unit which isn't Pantsir) would be unrealistic. Of course, none of that matters if you are doing it for fun! Depending on realism choices, the SA-11 may not actually be supported by other defense units. Part of the reason for the development for the advanced Buk variants being able to engage incoming weapons is because they aren't always supported... IRL, in the current conflict, we've seen a lot of videos of Buk's operating entirely independent of other AD assets. The primary thing which makes the Buk dangerous is that it is a tactical SAM which can rapidly pack up and move. Such capability is NOT possible in DCS by default and must be done using third party scripting. There is a branch of Skynet (baron branch) which includes the ability for tactical SAM's like the SA-6 and SA-11 (among all the others) to move after emitting or shooting. It adds an extra layer and puts the teeth in tactical SAM sites.

It's not a perfect solution due to the RWR limitations and lack of Skynet integration (although I was able to make it work through some LUA editing of the Skynet Compiled file), but it is a great temporary fix until ED gives us a P-14 and PRV-13/17 Nothing like seeing an SA-5 launch at 80nmi!

I'll have to look into what the conflicts are between the two packs and then decide, if it's a duplicate unit issue, if there is a way to address it and keep both options, or pick one over the other. The hybridized High Digit SAM's already has a GitHub repository, but I'm at work and can't get to it right now.

I may be switching over to a hybrid version of HDSM due to lack of development. I know people are busy, so that's not a slight at anyone, but I've gone deep enough into the Lua shenanigans now to be somewhat dangerous! After speaking with Auranis on the HB discord, there were a few changes I wanted to make, specifically the S-300PS using the 5V55R missile having worse performance now than the in game 5V55R... same with the RUD but the RUD has no core version. The version I have is now using a Tin Shield (optionally) and the in game 5V55R but with ERO's models. With the help of Recoil, we also fixed the SA-23 issue, although it displays as a 12 on ED RWR, that's at least.... something... and the HARM code works again. At some point I'm going to end up combining HDSM and your pack so I can use it all in missions. Maybe I'll work on that this weekend. The models are pretty legit too, thanks ERO! Love using them while ED ignores assets which are almost as old as DCS untouched. Maybe we'll see updated models soon enough.

Greetings ED devs, while working on a different project to clone the SA-5 and give it some longer range search radars, another individual and I discovered the Tin Shield search radar does not presently function with the in game SA-10B (S-300PS). The ST-68U Tin Shield was originally intended as a temporary search radar for the early S-300P systems and as a general Early Warning Radar. I was able to modify the High Digit SAM Mod S-300PS to utilize the Tin Shield in its coding, and after discovering how easy it is (literally one line gets changed), I was wondering if this change could be pushed to the default DCS S-300PS as an option for countries which didn't receive the Big Bird search radar and as an option for those which did. The specific line in High Digit SAMs is: GT.WS[ws].LN[1].depends_on_unit = {{{"S-300PS SA-10B 40B6MD MAST sr"}},{{"S-300PS 64H6E TRAILER sr"}},{{"RLS_19J6"}}}; where the RLS_19J6 is the in game ST-68U Tin Shield. In S-300PS 54K6 cp.lua, would need to have the depends_on_unit line changed to something like: GT.WS[ws].LN[1].depends_on_unit = {{{"S-300PS 40B6MD sr"}},{{"S-300PS 64H6E sr"}},{{"RLS_19J6"}}}; A fairly small amount of time would be required to add a whole new level of "realism" to the in game S-300PS for nations which didn't have access to the Big Bird search radar or for "dated" scenarios involving pre-64N6 Big Bird deployment by the Soviet Union. Thanks for your time!

Let Me Pick That has his own S-300 pack which includes an S-300PS. My understanding is, and the Lua confirms, they are not the same lua but are the same 3D model. I already made the change in my local copy of HDSM and put in a request on the github page for HDSM to make the change. It seems unlikely it'll happen since HDSM is hasn't seen changes in years.

For those who don't want to open LUA files, here is the "fixed" LUA file for the P-14 to work correctly: sensors.lua Just replace in your Sensors folder to get it to work as a radar: C:\Users\XXX\Saved Games\DCS.openbeta\Mods\tech\P-14 Tall King\Database\Sensors And if you want to use it in something other than just as an EWR, here is a modified SA-5 which can use it as its search radar!:

Greetings all! One of the biggest issues DCS has with the implementation of the SA-5 is the lack of possible search radars available to it resulting in it having much shorter range than it would in real life. @Recoil16 and I (almost entirely Recoil) sat down and hacked together an SA-5 Mod to utilize until ED adds the P-14 and PVR-13/PVR-17 height finding radars to the game and SA-5. The end result is an SA-5 with some teeth. As a test, I flew an F-16 at Mach 0.9, at 25k feet, on Syria, and was locked at 94miles and engaged at 80 miles. This is significantly better than the about 50 miles of the default SA-5 in the same conditions. Download at the GitHub Page: https://github.com/Recoil016/DCS-107th_SA-5 You'll be able to use the following Radars: -ST-68U Tin Shield (Default DCS) -P-19 Flat Face (Default DCS) -55G6 Nebo-U/Tall Rack (Default DCS, Added for those who don't want to use other mods) -P-37 Bar Lock (SAM Site Asset Pack/2SAP) -P-14 Tall King (P-14 Tall King Mod) **See Known Issues** Known Issues: -Comes up as an "Unknown" on RWR. Because of the way ED changed how RWR indications work, we cannot hijack the default SA-5's RWR indications like we could if it was an "older" SAM site like the SA-10. Therefore, on NATO RWR's, it will come up as a "U" for Unknown. -The P-14 Tall King Mod has an error in it's Sensor.lua which needs fixed in order to work. On their mod page (https://forum.dcs.world/topic/328269-p-14-tall-king-radar-v-10/#comment-5257238), at the bottom, you can see the fix. Easy enough! -You CANNOT mix the default SA-5 launchers or track radars with this mod and have them work. -Skynet Compatibility hasn't been tested. Install: Installs into your DCS Saved Game's Folder. File structure should allow for a direct drop into the Saved Game Folder or use of a mod manager. Bugs, etc: If you find any bugs, let us know here or on the GitHub and we'll try and work through them! Thanks!

Hey @LetMePickThat, I have a suggestion as a feature update for your next S-300 Pack release which adds some "depth" to them. As it stands right now, the S-300PS can only use the Big Bird as a search radar... but in real life the S-300PT and PS commonly used Tin Shields as well. In fact, the Tin Shield is incorrectly associated with the SA-5 in DCS which is similarly incorrect. So what's the fix? EZ PZ!!! Line 51 of S-300PS_54K6.lua says: GT.WS[ws].LN[1].depends_on_unit = {{{"S-300PS SA-10B 76N6E sr",},},{{"S-300PS 64H6E MOD sr",},},}; Change it to: GT.WS[ws].LN[1].depends_on_unit = {{{"S-300PS SA-10B 76N6E sr"}},{{"S-300PS 64H6E MOD sr"}},{{"RLS_19J6"}}}; The additional "RLS_19J6" is the in game Tin Shield name and this adds the Tin Shield as an optional search radar to the group. This works perfectly with the High Digit SAM S-300PS and should work with yours as well. It doesn't change anything beyond just keeping people from being complacent with their search radars indicating what SAM is actually in an area if they start seeing TS show up and it's a 10 locking and launching on them instead of the SA-5!

Don't be too hopeful... we have the assets in game and can be viewed independently of each other, but the minute they are put together, DCS crashes without anything in the crash log or an event viewer event beyond "DCS.exe encountered a problem and closed." Still in the early stages of investigating the shenanigans required... but work will continue as I'm tired of seeing an SA-5 engage at 60 miles when it can easily reach twice that! I'd also love to enable the use of this P-14 Tall King as it's search radar... but baby steps! Now we just need an Odd Pair to go with it!

So what's great about that, is you can create a modded version of an SA-5, in theory, to use the in game assets, but with the modified LUA's.... there is a DCS Datamine available with all the requisite files. Myself and another are working on doing exactly that, but testing is required. We were able to "fix" the SA-10B in High Digit SAMs to use the Tin Shield, and it worked exactly as intended.

V2.1 is out! You can download it from the ED User Files here: https://www.digitalcombatsimulator.com/en/files/3331424/ Updates in V2.1: 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)

FWIW, I have a 3090Ti and my this issue causes my Reverb G2 to crash... the tracking still works, but it stops displaying in the headset. I know the tracking works still because of the Mirror running on the monitor... I get this most frequently on Sinai (really the only map I've played since this patch came out) and it's particularly noticeable in the Viggen and F-14. Didn't have any issues in the F-16, and haven't flown the Mirage 2000 or AV-8B to see if it's specifically a Heatblur module related issue... The Log file says the headset displays are disconnecting... 2023-06-14 04:04:19.658 INFO VIGGEN (46244): FOLDERID_SavedGames: C 2023-06-14 04:04:19.658 INFO VIGGEN (46244): Custom cartridge file found! C 2023-06-14 04:04:19.659 INFO VIGGEN (46244): FOLDERID_SavedGames: C 2023-06-14 04:04:19.659 INFO VIGGEN (46244): Custom cartridge file found! C 2023-06-14 04:04:19.659 INFO VIGGEN (46244): FOLDERID_SavedGames: C 2023-06-14 04:04:19.660 INFO VIGGEN (46244): Custom cartridge file found! C 2023-06-14 04:04:19.660 INFO VIGGEN (46244): FOLDERID_SavedGames: C 2023-06-14 04:04:19.660 INFO VIGGEN (46244): Custom cartridge file found! C 2023-06-14 04:04:19.661 INFO VIGGEN (46244): FOLDERID_SavedGames: C 2023-06-14 04:04:19.661 INFO VIGGEN (46244): Custom cartridge file found! C 2023-06-14 04:04:20.589 INFO ED_SOUND (Main): Opening audio device "{0.0.0.00000000}.{80a56e80-0027-4253-b15f-2e0d39347ef4}" 2023-06-14 04:04:20.589 INFO ED_SOUND (Main): Speaker layout: auto 2023-06-14 04:04:20.590 INFO ED_SOUND (Main): Driver reports 2 channels with mask 0x3 2023-06-14 04:04:20.590 INFO ED_SOUND (Main): Using 2 channels at 48000 Hz 2023-06-14 04:04:20.590 INFO ED_SOUND (Main): Channel layout: Headphones/Stereo 2023-06-14 04:04:20.612 INFO ED_SOUND (Main): Opening default audio device. 2023-06-14 04:04:20.615 INFO ED_SOUND (Main): Speaker layout: forced_stereo 2023-06-14 04:04:20.616 INFO ED_SOUND (Main): Driver reports 2 channels with mask 0x3 2023-06-14 04:04:20.616 INFO ED_SOUND (Main): Using 2 channels at 48000 Hz 2023-06-14 04:04:20.616 INFO ED_SOUND (Main): Channel layout: Headphones/Stereo 2023-06-14 04:04:20.656 INFO APP (Main): Device unplugged: \\?\SWD#MMDEVAPI#{0.0.0.00000000}.{136181b8-714f-452a-8755-ed55399c9616}#{e6327cad-dcec-4949-ae8a-991e976a79d2} 2023-06-14 04:04:20.738 INFO APP (Main): Device plugged: \\?\DISPLAY#HPN36C1#5&30f0f42b&0&UID4355#{866519b5-3f07-4c97-b7df-24c5d8a8ccb8} 2023-06-14 04:04:20.849 INFO APP (Main): Device plugged: \\?\DISPLAY#HPN36C1#5&30f0f42b&0&UID4355#{10910c20-0c64-4172-9409-add3064c0cad}\color 2023-06-14 04:04:20.969 INFO APP (Main): Device plugged: \\?\DISPLAY#HPN36C1#5&30f0f42b&0&UID4355#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} 2023-06-14 04:04:21.078 INFO APP (Main): Device plugged: \\?\SWD#MMDEVAPI#{0.0.1.00000000}.{78b44337-7447-477c-a858-b16e588bd51d}#{2eef81be-33fa-4800-9670-1cd474972c3f} 2023-06-14 04:04:21.188 INFO APP (Main): Device plugged: \\?\SWD#MMDEVAPI#{0.0.0.00000000}.{136181b8-714f-452a-8755-ed55399c9616}#{e6327cad-dcec-4949-ae8a-991e976a79d2} 2023-06-14 04:04:21.315 INFO Dispatcher (Main): Stop 2023-06-14 04:04:25.374 ERROR ED_SOUND (24752): IAudioClient::GetCurrentPadding failed: 0x88890004 (AUDCLNT_E_DEVICE_INVALIDATED) 2023-06-14 04:04:53.424 WARNING LOG (16976): 1 duplicate message(s) skipped. 2023-06-14 04:04:53.424 INFO TACVIEW.DLL (Main): Closing current flight data recording... 2023-06-14 04:04:53.478 INFO TACVIEW.DLL (Main): Successfully saved [C:\Users\chris\Documents\Tacview\Tacview-20230613-203206-DCS-Through_The_Inferno_SINAI_v1.0.0.zip.acmi] 2023-06-14 04:04:53.478 INFO TACVIEW.DLL (Main): End of flight data recorder. 2023-06-14 04:04:53.481 INFO ED_SOUND (Main): Opening audio device "{0.0.0.00000000}.{80a56e80-0027-4253-b15f-2e0d39347ef4}" 2023-06-14 04:04:53.481 INFO ED_SOUND (Main): Speaker layout: auto 2023-06-14 04:04:53.481 INFO ED_SOUND (Main): Driver reports 2 channels with mask 0x3 2023-06-14 04:04:53.481 INFO ED_SOUND (Main): Using 2 channels at 48000 Hz 2023-06-14 04:04:53.481 INFO ED_SOUND (Main): Channel layout: Headphones/Stereo 2023-06-14 04:04:53.504 INFO ED_SOUND (Main): Opening default audio device. 2023-06-14 04:04:53.506 INFO ED_SOUND (Main): Speaker layout: forced_stereo 2023-06-14 04:04:53.507 INFO ED_SOUND (Main): Driver reports 2 channels with mask 0x3 2023-06-14 04:04:53.507 INFO ED_SOUND (Main): Using 2 channels at 48000 Hz 2023-06-14 04:04:53.507 INFO ED_SOUND (Main): Channel layout: Headphones/Stereo 2023-06-14 04:04:53.534 INFO WWT (Main): Export stop! 2023-06-14 04:04:53.581 WARNING SCENE (50700): Scene was removed with 3 alive objects 2023-06-14 04:04:53.582 WARNING SCENE (50700): Scene was removed with 14 alive lights 2023-06-14 04:04:54.320 INFO TERRAIN (Main): lSystem::CleanScenes() 2023-06-14 04:04:54.369 INFO ASYNCNET (Main): messages tracked: 9366037 2023-06-14 04:04:54.402 INFO VISUALIZER (50700): Stopped collection of statistic. 2023-06-14 04:04:54.402 WARNING SCENE (Main): Scene was removed with 6230 alive objects 2023-06-14 04:04:54.540 WARNING SCENE (Main): Scene was removed with 665 alive lights 2023-06-14 04:04:54.561 INFO VISUALIZER (Main): DCSScene initialized 2023-06-14 01:26:43.000 ERROR_ONCE (): 2023-06-14 04:04:57.366 INFO VISUALIZER (50700): DCSSceneRenderer initialized 2023-06-14 04:04:57.367 INFO EDCORE (Main): Create boot pool. 2023-06-14 04:04:57.384 INFO EDCORE (Main): Created boot pool: n:16 2023-06-14 04:04:57.398 INFO EDCORE (Main): (dDispatcher)enterToState_:3 2023-06-14 04:04:57.933 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1418, 1390] 2023-06-14 04:04:57.933 INFO APP (Main): Device unplugged: \\?\SWD#MMDEVAPI#{0.0.1.00000000}.{78b44337-7447-477c-a858-b16e588bd51d}#{2eef81be-33fa-4800-9670-1cd474972c3f} 2023-06-14 04:04:58.001 INFO APP (Main): Device unplugged: \\?\SWD#MMDEVAPI#{0.0.0.00000000}.{136181b8-714f-452a-8755-ed55399c9616}#{e6327cad-dcec-4949-ae8a-991e976a79d2} 2023-06-14 04:04:58.070 INFO APP (Main): Device plugged: \\?\SWD#MMDEVAPI#{0.0.1.00000000}.{78b44337-7447-477c-a858-b16e588bd51d}#{2eef81be-33fa-4800-9670-1cd474972c3f} 2023-06-14 04:04:58.164 INFO APP (Main): Device plugged: \\?\SWD#MMDEVAPI#{0.0.0.00000000}.{136181b8-714f-452a-8755-ed55399c9616}#{e6327cad-dcec-4949-ae8a-991e976a79d2} 2023-06-14 04:04:58.278 INFO ASYNCNET (Main): Current ping: 63.5ms 2023-06-14 04:04:58.278 INFO EDCORE (Main): (dDispatcher)enterToState_:5 2023-06-14 04:04:58.283 INFO APP (Main): application shutdown 2023-06-14 04:04:59.667 INFO ASYNCNET (Main): disconnected: 0 2023-06-14 04:04:59.667 INFO ASYNCNET (Main): disconnected from server 2023-06-14 04:04:59.830 INFO ASYNCNET (Main): client has stopped

NDB stands for "Non-Directional Radio Beacon" and you'd fly it like an ADF beacon. In the RIO pit, set the radio to the appropriate frequency, switch the radio to "ADF" or "DF" (can't remember which it is) then fly off of the BDHI in the cockpit. It's the small arrow. It should also show up in the main HSI as well, but I rarely find myself in that mode. I'm also not sure what is proposed here actually works... either... and without a course line it'd be nearly useless... a TACAN approach would be MORE accurate if the airfield has a TACAN.

Ohh, on the TTI Sinai Server, the Handy Wind is handily parked exactly like this too!

Man, I can't thank OnReTech enough for making the SA-2 positions so beautiful! LOVE it! I hope we get to see some variation in them in the future, but for now, I'm REALLY happy with how well done they are. If any other terrain developers are paying attention, this is the standard to strive for now! Thanks OnReTech for making this SAM Nerd happy!

Ahhh... a Through the Inferno Player, I see!

Are you asking about what altitude we set the burst altitude for? Or are you asking about what altitude we drop them from the jet? In general, for CBU-105 burst altitudes, I prefer 1000ft. If it's particularly windy, 750 works too. As for release altitude of the weapon itself from the jet, that depends on what I'm dropping on. Generally, with CBU-105, I'm attacking a SAM site, because DEAD is life! That means doing pop up attacks from about 7.5-9nmi and release altitudes between 5k-9k AGL with a 25 degree loft... Hopefully ED gets the IAM loft cue fixed so we can go back to yeeting CBU-105's 12nmi again.

I downloaded the C-RAM this morning to play around with and it works fine on mine end... doesn't engage some rockets (like the 300mm ones from the BM-21), but I'm guessing that's DCS being DCS. Love the work put into these, just wish they were put together in packs instead of individually. As someone who does missions for the group I fly with, it's a huge ask to download a bunch of individual files if I wanted to include a bunch of them in a mission, but overall, enjoying it! Thanks for the hard work!

Greetings! The Bug: The SA-10's first shots (about 3-6, inconsistent) fire straight up and explode without ever tracking. DCS Version: 2.8.5.40170 Multi Threading ON Computer: 9900k, OC'd to 5GHz 3090ti 32gb of 3400MHz Memory DCS Installed on NVME SSD Steps to Reproduce: Step 1: Create a mission with a default SA-10 Template. I added six additional launchers to actually fill out the SA-10, but it's irrelevant. Add a flight of MiG-29S at 33k feet of altitude and Mach .9 set to directly overfly the SA-10. I set them at the outer edge of the threat ring for the SA-10. Step 2: Run the mission and observe SA-10's launch behaviors. Expected Result: All SA-10 missiles launched should track to their intended targets and only detonate if the radar loses tracking or the missile times out. Observed Result: The first 3-6 shots from the SA-10 travel straight up and before they execute their gravity turn to intercept the target, they explode in what can only be described as a VERY expensive Fireworks show. I FIRST observed this with the High Digit SAMs Mod but the bug persists in a non-modded DCS as well. Other: Attached files are with all mods disabled... I think! dcs.log SA10Bug.trk Tacview-20230525-173853-DCS.zip.acmi

I'd be happy with ED maps being updated to just include these positions directly into the map for the real world positions... or the ability to draw fences and berms using the draw tool with segments or similar. Same with roads. But really, there needs to be more stuff like the SAM Site Asset Pack to make it a reality. It'd be nice if they'd focus on the known SAM emplacement types... like a dedicated SA-2 "Star" or those SA-5 berms, bunkers, and elevated radar positions.

I generally use 1000ft in windy conditions.

I would say this issue, among many of the Surface to Air missiles, need some serious attention from the developers. Not just the current crop of missiles and how they are represented, but also adding in additional missiles and types. I realize the more modern systems are classified, but certain, more modern Russian SAM's are plenty old enough, yet more modern than the S-300PS we have in game. Having additional Sea to Air Missile systems would be great too!

It is my understanding the GE F110's had different intake ramp scheduling to accommodate the air intake requirements of the engine. In doing so they optimized airflow for better transonic performance. I'm not sure why they couldn't do "it all" given they were programable. Maybe lack of space for the code to accomplish it. The claim is the Mach 1.88 "top speed" of the B and D is because of safety issues with an engine failure. My guess is the risk of engine flameout increased drastically due to airflow in the intake not slowing down enough at high Mach.

I can't speak much to the HARM's usage in default DCS, but I will speak to using HARMs against targets with point defense capabilities (SA-10, SA-12, SA-15, SA-17, SA-19, SA-20, SA-21, SA-22, and SA-23... not all of which are in game), the general tactic is "Don't". There are other tactics which are far more useful to deal with those SAMs. That's not to say you wont eventually get one through, but you'll be spending a lot of time weaseling to get a HARM through. Your only real hope is to work as pairs to engage the SA-10. Get the Flap Lid track radar pointed in one direction and HARM it from another. Not workable in singleplayer, really. This goes to the broader discussion of how SAM sites work in DCS and the need for proper IADS to really replicate how these systems work IRL, or at least, in a more plausible way. While it is true the Big Bird search radar and Tin Shield (both used with the S-300 system IRL) are used as EW sites, it really depends on the area and what the site is defending and how the site is deployed. Forward S-300 bases will use it more than the static S-300 sites would... for instance.