YoloWingPixie

Was this ever fixed or looked at? Raw getSensors result for Unit ID 20 ( S-300PS 40B6MD sr { [1] = { [1] = { ["detectionDistanceAir"] = { ["upperHemisphere"] = { ["tailOn"] = 106998.453125, ["headOn"] = 106998.453125 }, ["lowerHemisphere"] = { ["tailOn"] = 106998.453125, ["headOn"] = 106998.453125 } }, ["type"] = 1, ["typeName"] = "S-300PS 40B6M tr" } } } I'm still getting the same issue as reported in 2021, where the surveillance radar unit returns the track radar unit's radar as its sensor in an example SA-10 group.

I have noticed the exact same issue on my end. It also seems to be the HARM may be tracking the SA-15 even after the SA-15's radar stops rotating

When the SA-10 is presented with targets along multiple axes, such as what is presented in the attached miz file, the SA-10 will engage no targets. What appears to be happening is the controller's targeting logic is getting thrashed and the track radar is constantly moving to acquire a different target. This ultimately means that, although the SA-10 should be capable of detecting, locking, and engaging every target in the miz file, it targets none and simply dies. I've included 2 tracks in two different locations to show this is a logic issue and not likely terrain. This is new behavior as of this patch and was not present before the update DCS 2.9.6.57650 When the SA-10 is presented with targets along a single axis, it behaves as expected. This only occurs when there are targets that are beyond the azimuth limit of the SA-10 TR, which requires the Flap Lid to rotate. SA-10TR.mov SA-10_Bug_Report.trk SA-10ThrashingIssue.miz SA-10_Bug_Report2.trk

We're aware of the issue and have had a pull request in that fixes it, however the actual update is awaiting some changes from others as well.

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