Tasmanian

Hello, There seems to be an issue with SA-5 guidance. Missiles overshoot targets and pass too high. The attached track features a target flying at 20500m, ~2000 km/h towards the SA-5 site. The target is flying in a straight line, jamming forced off. The first missile launched at max range passed about 10km higher, at about 30km altitude. The second missile was launched at about 140km distance and missed by about 5 km over the target. Could you please investigate? Regards, Yury SA-5_Overshoots.trk

Hi, I would like to share some of my findings. According to the documentation, the antenna is receive-only. It is not used to arm the warhead. The warhead is armed by the missile program in two stages. The first one is timer-based. The second one is triggered by the angular velocity of the missile's line of sight. I couldn't find any description or procedure to terminate the missile. At this point, it seems like sending a self-destruct command is not possible. If you find something, please let me know, I'm also very curious. I only found that self-termination is triggered when the on-board power source is depleted. This is partially true. There are two main operating modes, and only one can provide the range. The RWR can likely differentiate the two modes but neither of them indicates a launch. Below is the table that shows the recommended modes for a single target. Targets above 1km altitude are engaged in the monochromatic mode, the one that doesn't provide the range. Lock-after-launch is possible only in this mode. The Phase-modulated mode is typically used for low-flying targets or targets within a group. There is a whole section on which mode to use depending on the conditions, and I can't post it here. The range can be entered manually using other data sources or briefly using the phase-modulated mode. If the range is unknown, two missiles can be launched in different modes, one in P-nav, and another in a long-range mode with loft, etc. This is achieved by manually entering different ranges before each launch. The B-880 missile transponder doesn't emit unless the missile loses lock. It is mentioned that this is specifically done to conceal the launch. B-860 missiles do emit but I don't know which RWR can detect it and at what range. The document mentions that the pattern is within ±45 degrees along the missile axis. However, it doesn't mention whether it is true for the frontal hemisphere. I attached another S-200 manual. I hope it helps. Regards, Yury учебник по с200.djvu

Hi, Please see the attached documents. I couldn't find any mention of emissions change upon launch. Phase modulation is used explicitly to determine the target range. Missles can (in some scenarios must) be launched even in monochromatic emission mode. The only extra emissions may come from the missile transponder, but it should be directional (why not), and shouldn't trigger RWR. Regards, Yury общие сведения о с-200.djvu зрк с-200.djvu стрельба зур 200.djvu лекции по рпц с200.djvu правила стрельбы с-200.djvu

SA-5 doesn't change emissions upon launch. There should be no RWR warning in the first place.

Same thing with SA-5. Apparently, that's how most SAMs are simulated in DCS. SA-5_Weird_Launch.trk

Actually, SA-5 does fire at targets beyond 200km. However, the target altitude must be high enough because of the Earth's curvature and terrain, I guess. (I didn't do the math to confirm.) There are other issues with SA-5: 1. The firing solution is computed based on the instant missile velocity. As a result, the missiles take too much lead after launch because the initial velocity is relatively low. This may cause them to lose the target and self-terminate. Track attached. 2. As I know, SA-5 emissions don't change after the missile launch, therefore the launch shouldn't trigger RWR. However, it does. SA-5_Weird_Launch.trk

Hello, I observed the following issue: When SA-5 fires on high-parameter targets at long range, the missiles self-destruct. The track shows an SA-5 engaging a target at 21km altitude, ~45km parameter. The target uses no ECM or chaff and doesn't maneuver. (Reaction to threat = none, ECM=off) Missiles are fired at a distance of about 200km. Missiles do a sharp turn towards the calculated intercept point and explode shortly after. I assume, they lose the target as it goes outside of their field of view. Regards, Yury SA-5_Weird.trk

Hello, I observed the following bug: AI flies into terrain while landing at Mesquite airport in Nevada due to a very shallow final. Checked with an F-15 and an AJS37, tracks are attached. Regards, Yury ViggenCrash.trk F15_Crash.trk

Hello, Thank you for the response. In the original track (F117_Invincible.trk), I was controlling a single SA-15 with Combined Arms to demonstrate that this SAM can technically hit an F-117. There were multiple AI controlled SAMs nearby (SA-10, SA-11, another SA-15, and AAA, all in separate groups). They didn't engage. From your snapshot, it looks like only my SA-15 was firing. I am attaching another track (F117_NoEngage.trk) where I didn't control anything, only forced one of the SA-15 to status "red" just to make sure it's working. Regards, Yury F117_NoEngage.trk

Hello, I observed the following issue: Air defense doesn't engage F-117 under any circumstances. Even optical AAA does nothing during daytime. It is easy to lock on with an SA-15 but the F-117 survives 8 hits. However, I managed to shoot it down with Air-to-air missiles. (The invincibility has been reported before.) Please see the track attached. Regards, Yury F117_Invincible.trk

Hello, I observed the following issue: SSM SS-1C Scud-B is overcorrecting for wind. The attached track shows the missiles hit 27 km off the target. If wind is set to zero the missiles go the right direction but land several km far anyway. Regards, Yury ScudWind.trk

Hi, I am flying A-10A armed with 6 Mavericks (LAU-88, AGM-65*3 on pylons 3 and 9). The problem is that only the Maverick, which is attached to the center of the launcher performs the loft maneuver correctly. The ones which are attached to the left and to the right of the pylon turn aside and miss target in most scenarios. This happens with both "D" and "H" versions. I suppose that the reason is that Mavericks to the left and to the right of the pylon are rotated but the "navigation code" does not take this into account, so instead of pitching up the missiles go sideways. Looks like a bug. I am attaching a track which demonstrates the issue. P.S. The topic was originally created in Flaming Cliffs thread, but I was suggested to post here, probably, because the issue is related to AGM-65, not A-10A aircraft. Track is attached there and I can't re-upload it: https://forums.eagle.ru/showthread.php?t=231144

Unfortunately, current SAMs are bugged =( Proximity fuses not working, SA-2 missing even subsonic straight flying targets at 10km, etc... Shilkas were a joke forever in DCS, BMPs are better)))

And seems like this faulty behavior applies to many, maybe all SAMs...

You can't even pick a huge factory in a plain field from ~17 km range until it suddenly spawns under your nose. This is fine for generic statics, as it reduces load. But in my case it is a manually placed factory, it is a mission objective, so it is very frustrating to have such a small visibility range. :mad: P.S. Even some map generic buildings are visible much farther in the same mission.