Quick preliminary very very unprofessional test to see what I can find out about it:
Launch 1: R-27ER, 12km directly abeam
Threat detected at 8km. Angle difference from radar to threat 2-3 degrees. Triggered response 5, swapped to response 4 after one burst as angle difference increased.
Launch 2: R-27ER, 3km like roughly nose on.
Threat detected at 2km. Angle difference of roughly 4-5 degrees. Triggered response 4 exclusively.
Launch 3: R-27ER, 8km rear aspect.
Threat detected at 7km. Angle difference negligible (like 1 degree)
This launch is the most interesting one and i’m going to have to check this a lot further (see below), because despite a
constant missile alert from 7km to impact, the countermeasures were intermittent (and only flares when they did work). This suggests it’s swapping between identifying the incoming missile as SACLOS and IR, but
failing to identify it as SARH even once.
This is incredibly weird, as as shown here:

an Su-30 launch signal should flag up as SARH. RWR SACLOS flags are only triggered from certain launchers such as 2S6 or Pantsir, and a SACLOS launch with a track should result in chaff being deployed.
My current running theory is this, and the following is speculation:

This may be what decides whether the threat is SACLOS, radar, or IR when combined with a radar track (or whether the track is totally unrelated). From these three launches alone, it’s visible that the “0-2” band appears to be treated as SACLOS (Which would make sense, as SACLOS missiles will follow a line between the launcher and target), while the 2-3 band is treated as SARH and the 3-10 band as IR.

This then likely sets the maximum for correlation to 3 degrees, which would make the IR+radar redundant. I cannot test this as it is literally just treated as IR, so its totally pointless in the first place (see below)

This would explain why the matchAngleByTimeDiff array has four values, instead of only having one maximum. It would also explain the behaviours in this initial test, and why the SARH response is so abysmally rare even when the missile is within the necessary angle, as this may just trigger it to not respond at all.
The concern is that if this is true, that means the angle gates, which are much less reliable than the sensor fusion, are overriding the actual sensor fusion.
An alternative would be that the threat flags have an unintentional heirarchy in their order, which would also explain SACLOS overriding under certain conditions as it is at the top of the list.
I don’t think additional testing will actually help here. There are no additional conditions which would provide valuable info (unless someone has suggestions lol). This reads as spaghetti code messing with the DASS behaviour. Will put together a report when its not 4am. (done) → Community Bug Reporting System tada
Quick further one I thought of: Tested against SA-2 (S-75). This is a true SACLOS weapon, and therefore triggers the actual SACLOS responses. Two tests were done: one headon to the threat (providing a consistent angle) and one while almost abeam (not notching, but making the angle between radar and missile inconsistent.). When headon, there was no response whatsoever. This matches the result with the Su-30 - when angle between launcher and missile is negligible it appears to not respond at all. When at an angle, the response was flares only. This is again consistent, as the threat is not SARH and therefore the response was simply IR, even though I was being locked.
TL;DR it works brilliantly vs IR/ARH and is near useless at correctly responding to anything else.