You have three types of PD radar modelling in the game, which varies by radar and even by various modes on each radar.
One has ground clutter simulation enabled without forced exact notch width specified, which allows it to keep tracking stuff through the notch in look-up scenarios, the other has ground clutter simulation disabled with a forced exact notch width specified, and third type has both ground clutter simulation and exact notch width specified.
Now, to my understanding, currently the radar automatically tries other signals / modes in STT mode, if it loses the target in the currently used signal / mode.
But it doesn’t have combined waveform / interleaved PRF in search modes.
If you for example compare the HPRF search of the AWG-9 with MPRF search of the CAPTOR-M:
"hprfSearch": {
"dynamicRange": [
40.0,
15.0
],
"groundClutter": true,
"aircraftAsTarget": true,
"friendFoeId": true,
"absDopplerSpeed": false,
"mainBeamDopplerSpeed": false,
"distance": {
"presents": true,
"minValue": 5000.0,
"maxValue": 370000.0,
"width": 500.0
},
"dopplerSpeed": {
"presents": true,
"minValue": -410.0,
"maxValue": 2500.0,
"signalWidthMin": 5.0,
"width": 120.0
}
},
You can see that AWG-9’s HPRF search has ground clutter simulation without a forced exact notch width, which means it can find notching targets in a perfect look-up scenario.
"mprfSearch": {
"groundClutter": false,
"aircraftAsTarget": true,
"friendFoeId": true,
"targetId": true,
"mainBeamNotchWidth": 60.0,
"distance": {
"presents": true,
"minValue": 500.0,
"maxValue": 180000.0,
"width": 500.0
},
"dopplerSpeed": {
"presents": true,
"minValue": -2500.0,
"maxValue": 2500.0,
"signalWidthMin": 2.0,
"width": 30.0
}
},
But CAPTOR-M’s MPRF search has ground clutter simulation turned off and instead uses a forced exact notch width, which means it can’t find notching targets regardless of the look-down/look-up scenario.