So if there is more than 1 target. you cant use the radar?
no, what it means is that the radar may lose track of targets (at certain angles (in certain radar modes)) if you switch off from said target and then try to another switch back to said target (if the target remains at the same angle)(and only if you are attempting to use tws to reacquire the target).
So. The CAPTOR-M cannot be used if the target is flying perpindicular to you +/- about 15° from what I have observed. That is a massive blind spot.
It also doesnt explain why the radar sometimes doesnt see targets that are flying straight at you. Unless you are still claiming those targets are “notching” the radar.
I think @Dontkev-psn had a clip of it doing that to him and I know i’ve had that.
Also. It shouldnt matter if I swap targets because Priority track should maintain the track/lock just fine. But of course. That isnt modeled even slightly on the Typhoon, but is on the Rafale and other AESA radars
what? like actually what are you talking about? this is just not at all the case maybe if you had played more than what four games in the plane during the past month you would have noticed that this isn’t the case and maybe you wouldn’t just say things that are completely untrue.
i would love to see a clip of this on the most recent patch in sensor view
Why play an unfinished buggy mess?
When they actually add the CAPTOR-M I might consider picking the Typhoon up again, but at hte moment I just dont see the point. You cannot fight Rafale or Su-30SMs. So why play the aircraft. When I do play Air. I just have more fun in the Tornado F3 or Tornado Gr4.
Though seeing as you have played 1 match. and gotten 0 kills with the Typhoon in ASB. Im not really sure why you are criticizing me for not playing the Typhoon.
those 4 games are air rb and sb combined i have played 20 games in the plane in air rb in the same time frame you have played 4
I dont really play ARB…
I might play the odd match in the GR4 if I fancy a short fast match. But otherwise ARB is god-aweful gamemode and of course you dont have issue with the CAPTOR-M you can just ACM/HMD hard lock anything without even using the TWS to find targets.
Go and play a couple of hours in ASB, where you dont have the crutch of markers telling you where enemies are or to IFF for you or to without third person view to look aroumd and then you will be allowed to provide ciricism.
And recently i’ve just been playing naval anyway. You know, there are other gamemodes and BRs in war thunder. You arent required to only play the top tier jets
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.
Though if im not mistaken. CAPTOR-M’s TWS mode has all 3 modes. LPRF, MPRF and HPRF and is meant to swap between them.
I have long suspected the core issue of the CAPTOR-M’s troubles lie in the radar not automatically swapping between the modes as it should be or defaulting to the wrong mode
1 Like
AFAIK interleaved PRF is not implemented for any radar in the game (yet) …
I assume it was.
Radar changes from January
Granted, it doesnt say that it swaps mode, but that is how I read the changes, but no one has ever corrected me before that that isnt how it works.
I also thought that was a core part of the Automatic mode swapping that they added to radars and such to maintain the lock. I thought that was also applied to TWS so you no longer had to swap TWS modes to maintain a track (at least I think i remember having to do that on the Tornado before that was added anyway) and was rather miffed when they removed automatic ACM mode from the F3 because its “not an all-aspect radar” despite it having that feature IRL.
Tornado F3 then I think swaps automatically between LPRF and HPRF.
At least I assumed some of this applied to TWS modes as well
But if it doesn’t. Then the answer is clear. CAPTOR-M is underperforming even more than I originally thought
That is to be expected, Pulse radars are not affected by notching in real life. But the trade off is that they are far more susceptible to ground clutter than Pulse Doppler radars.
No radar in the game has ever switched between different PRFs during TWS mode. Lots of them should, but Gaijin have only ever added automatic mode switching for STT and ACM modes.
1 Like
The AIM-120C-5s are on Typhoon on dev server now
1 Like
Along with Radar fixes and fm buffs?
1 Like
Doesn’t look like it unfortunately
This exactly.
Auto switch only happens when you have a lock (and the IRST issue we had where FOX3 could not be fired before hot fix comes from there).
TWS is just crudely modeled for most modern aircafts, from the gimped captor M to the RBE2 AESA. I understand people complaining about the Captor M currently being complete ASS, but trying to attribute global mis modeling to the Captor only is not the way to go
Haha come on now Morvran, thought you’d know better. You can notch any MPRF or HPRF radar.
I have never had any issues prior to the Typhoon where I was pointing my radar directly at something I could visually see, even in narrow scan and it not be detected.
I have also had a number of times where the target was 100% not in the notch and still not detected. (unless something flying basically straight at you is notching)
Notch gates on BV and CAPTOR-M are identical iirc. Also to your other comment on PRF management that only applies in STT in game. No radar is doing PRF management in TWS.
1 Like
So its really wierd I never had such issues in the Sea Harrier FA2 or Gripen.
Though notching doesnt explain why the radar doesnt detect things sometimes which very much arent notching. I will keep an eye out and get some clips.
I thought it did. Which sucks given we have no SRC mode to fall back upon for finding targets that TWS cannot see.