Search the Community
Showing results for tags 'sa-10'.
-
The new SA-10 unit set has an inconsistent deployment behavior that can ruin radar and TEL placements near or on static objects/revetments. Seemingly randomly (possibly depending on which unit type is unit #1?), the Flap Lid-B and/or TELs will move before deploying, putting the units out of position. Using a Hold task with the SA-10 template selected, or setting ALARM STATE Red in Wypt 0 does not resolve this issue. Expected behavior here is like how the old SA-10 unit acted: It didn't move to deploy. I have attached a miz and trk file that demonstrate this behavior SA-10_Bug_Report.trk SA-10_Movement_Issue.miz
-
Since the update the SA-10 missiles seem to be larger than their launch tubes and misaligned, see picture
-
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!
-
I found that the SA-10 is not able to shoot down an AGM-88C missile if it is fired in PB mode. SA-10 (S-300PS) is a system that undoubtedly has the ability to fire anti-radar missiles. If the HARM is fired with TOO (SP) mode, it is almost always shot down. I am aware that PB mode HARM creates a different trajectory missile. The missile descends to the emitter at an angle of about 23 to 25 degrees. Which is not out of range of elevation angle tracking radar (30N6). The elevation angle at which the TR 30N6 antenna is able to scan is +/- 60 ° degrees. One AGM-88C HARM missile was fired from the F/A-18 aircraft in PB mode (the missile was set to perform a loft (pullup HARM). The target that was chosen was SR 5N66M (Clam Shell). The mission had a set function. Harm was detected by SA-10 at a distance of about 31 nm. However, the rotation of the antenna in the direction of arrival of the target missile TR 30N6 occurred only a few moments before the missile hit. The TR 30N6 antenna was oriented in the direction of arrival for some time because it had previously detected an aircraft that fired a HARM. Then, although the SA-10 sensors detected an approaching anti-radar missile, the antenna was rotated to the default position. The rotation of the antenna in the direction of the arrival of the Missile HARM did not occur until a few moments before the radar hit. The test mission includes one F/A-18C aircraft, and 1x SA-10 (S-300 PS) in the following composition: 1x CP 54K6, 1 x SR 5N66M (Clam Shell), 1x SR 64H6E (Big Bird), 1 x TR 30N6 (Flap Lid A), 4x LN 5P85C. Map: Caucasus. Skill SA-10: Excellent I consider described behavior under very strange. I think that the parameters of the missile's arrival are not beyond the capabilities of the SA-10. SA-10 AGM-88C PB mode.trk DCS-SA-10 PB mode AGM-88C.zip.acmi