Search the Community
Showing results for tags 'air defence'.
Found 3 results
-
reported S-300 Missile Flight Path Issues
Shadow KT posted a topic in Ground AI Bugs (Non-Combined Arms)
When defending against HARMs (I suspect the result will be the same against other weapons as well), the SA-10 consistently flies its missiles substantially higher than their target. Meaning the SA-10 missiles arc high, when engaging incoming AGM-88Cs (difference between missiles and target altitude increases with range). The delta can be in the tens of thousands of feet. I've attached two tracks (with stationary and mobile radars), as well as an example Tacview file. SA-10 Miss High #1.trk SA-10 Miss High #2.trk Tacview-20231118-173404-DCS-VX NTTR .zip.acmi
- 20 replies
-
- 1
-
-
- investigating
- s300
- (and 1 more)
-
Hi all, Since I'm creating multiplayer mission content since at least 3 years now in DCS I was always trying to focus on creating as realistic scenarios, as I possiby can. However when it comes to airfield or HWA defence I'm really missing a good point defence sistem from the bluefor arsenal. We have the SA-15 for reds but nothing for bluefor. NASAMS was a great addition though, I hope DCS can implement the phalanx system as well. thanks
-
This issue was first observed multiple times in a multiplayer mission on Syria, Lebanon locale, after which I replicated it in a single player situation, as similar to the multiplayer situation as viable. Version: Latest Open Beta at this time - 2.7.14.23966 The gist of it: HAWK site sees a target (in this case a Havoc) and, if a firing solution is available, fires. Target evades by means of terrain masking HAWK loses target, and goes back to idle search Target unmasks and is reacquired by the SR TR starts tracking target, but the Launchers don't react Target sees no need to further evade, and proceeds to do Havoc stuff, like murdering the HAWK site and everything nearby (Unsure what the conditions for this are, maybe a few cycles of lost targets) - HAWK fails to engage any target until packed and redeployed, or ROE are cycled. In my replication I set the Havocs to do a weapon hold course, to try and achieve point 7, though I suspect it may need multiple cycles over the course of a few hours to rear its ugly head in this situation. Reloading of launchers might be related, though I couldn't conclusively confirm or rule it out with this relatively brief testing. In the multiplayer server, the HAWK sites are built up with CTLD, but are otherwise completely vanilla units. In my single player test I tested it with both my normal mod complement, as well as without any mods active, and it occurred in both situations. Additionally, I highly doubt it was altitude related, as the AI Havocs in their unchallenged attack state want to be above the targets, which is in this case the HAWK site. This is an image taken from the 'SP - without mods' track file, where the launchers did not engage the Havoc (top left of image, 6.3nm, flying at 5k ASL), despite having fully loaded launchers. I confirmed in a different run with 8 or 9 launchers that the HAWK can engage for the entire stretch, up until it's masked by the ridge-line it's positioned on, off-screen to the left of this image, so this situation is well within its capabilities to engage and hit. And this was for the next Havoc that showed up. The previously inactive launchers engaged as normal. Launcher layout in the MP server: HAWK 1 HAWK 2 Area situation in the Multiplayer server, Syria map, Lebanon - HAWK 1 is Northern red circle, HAWK 2 is Southern red circle. The Havocs spawn at Beirut and head South/East, towards the combat area. Orange indicates another HAWK site which I've observed exhibited the same issue: it detected a Havoc entering the valley, opened fire, and lost track. When it next re-acquired the same Havoc, it failed to actually re-engage, and it took a while until the Havoc was shot down by other air defences. The HAWK itself never fired another missile after picking that Havoc up again, despite it being well in range the entire time. I've attached multiple tracks, two of which were shot with mods active, though none directly affect the units and they can be viewed with an unmodded client. The third one is shot without mods. Additionally, I've attached the basic mission I made to test the situation. It's not consistent with how quickly it happens, so I ran it a few times to confirm. It's also possible to increase the amount of havoc spawns (along with the scripting), in order to increase the odds of it occurring in one mission. It probably comes as no surprise that this bug is very annoying here: A SAM site that works for a while, and then casually watches as an attack helo butchers it, isn't much of a use in a dynamic persistent scenario, where the SAM engaging something isn't a 'one wave and it's done'-deal, but an hour upon hour upon hour upon hour endurance thing. SP - With mods - HAWK fail 2.trk SP - Without mods - HAWK fail 1.trk SP - With mods - HAWK fail 1.trk HAWK-Havoc test Beirut.miz
