Razgriz383

I haven't played much DCS and especially helo ops since this issue has become pretty much unavoidable on most servers but it oddly doesn't seem to happen nearly as much when the AI are engaging players, mostly AI vs AI. It seems like other people have provided similar videos with actual tracks but I would like to stress that this isn't just NASAMS this is happening to, it is happening to everything from AAA to LR SAMs.

NASAMS and by extension all AI SAMs are still having tracking and engagement issues in MP because of what seems to be desync. I now have two examples of this in a multiplayer environment from a close perspective. In the first video you can see that NASAMS and Gepards are engaging two Kh-58U missiles incoming and the NASAMS scores several hits while the Gepards likely score some as well and the missiles still keep coming (dots are clearly visible in the uncompressed version), the missile dots derender for a time before suddenly reappearing as actual models and hitting the systems. I have observed this behavior with the Roland system as well. In the second video you can see NASAMS AIM-120s just despawning shortly after coming out of the launcher. A Roland missile flies THROUGH the incoming missile before curving suddenly and then the Gepard and/or NASAMs appears to score a hit which does not destroy it. The Gepard continues to track and fire but the missile again derenders for some reason. As I zoom out it hits a HAWK tracking radar while another hits the search radar. I have never observed this behavior on player weaponry from the AI as on the same server and same session HARMS were being consistently destroyed by Tor, 2S6, and Sa-10 systems with single hits so I have no idea why it is such a problem in a AI to AI engagement. The server appeared to be running relatively smoothly during that session so I'm not sure what the issue was here but it looks the server is registering certain things in the incorrect position. I have seen a Roland missile explode 75m from the missile I can see incoming and destroy it so this seems to be the inverse of that situation. Is this a known issue in multiplayer even on servers that look to be stable at the time? Update 1: I have now seen a AI Red MiG-29 eat 3 120s out of a NASAMS battery with no damage to then be immediately splashed by a R-77 from a Blue Player MiG that impacted shortly after the 3rd hit.

@Flappie I'm starting to heavily lean towards it being something to do with Multiplayer servers. I feel like it has trouble acquiring smaller missiles in general even though a Gepard nearby is tracking it. In the editor a battery can usually deal with 3 incoming KH-25s at once but it does seem to get confused and/or delayed when the firing aircraft enters the threat range at the same time. However, on this particular MP server the battery rarely if ever reacts to KH-25s even when nearby Rolands and Gepards have started tracking them. I've even watched the launchers physically track a Su-25 well within its engagement range and just let it buzz towards then around itself with no response beyond the launchers turning.

I noticed on a MP server using NASAMS via CTLD that it almost never engages targets well within its envelope and the accuracy is terrible even when it does with AMRAAMs flying in a straight but slight arc far behind and/or over the target. On top of that it seems completely incapable of defending nearby assets from missiles and borderline incapable of defending itself from even large and slow ARMs. This is a far cry from the absolute wall of AMRAAMs it could put out to intercept missiles previously making defending HAWK sites extremely difficult as Rolands and Gepards are not great at the protection role. I fired up the editor to see if this is a MP server issue and found that the NASAMs system would ignore incoming KH-58U missiles that are slowing down to subsonic at time of impact, to instead fling AMRAAMs at the launch platform outside of the envelope for the missile. So it would seem the lack of launching may be MP specific but the self-protection may be global. It would be great to have somebody verify this. NASAMS.trk