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.
The AIM-120C-5s are on Typhoon on dev server now
Along with Radar fixes and fm buffs?
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.
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.
Save the ingame replays as well please.
I will do. I’ll save the gamelogs too
Anyway. Any insider information regarding future plans for Aim-120C5 modeling?
or any other Typhoon tweaks coming this major?
Don’t know at the minute. Naturally if I hear anything I’m allowed to share I will do so in the appropriate forum thread.
Okaydokie, but let us know if your poking stick needs sharpening.
A lot of annoying little issues that they still havent resolved yet
Like the Aim-9M boresight being centred if the head is “at rest”
It shifts based upon positive or negative G being applied, its really annoying to have to adjust it down or up all the time
how come tws position reset hasnt been fixed yet
Just flew the EF again after flying american F-15/16/18 for the last month and holy hell… The notch gates don’t seem to be a problem at all but the extreme jumping around of target boxes, showing targets in your radar screen which you can’t select by cycling (even if they’re clearly not ghost targets which still get generated with a really high amount), forgetting target motion vectors the moment a target is lost (box flies into nirvana at an insane speed). It even seems to forget the target vectors sometimes if it has unobstructed view at a target.
The behavior differs extremly from the american radars as these seem to be much more “calm”, not generating as much ghost targets, not forgetting vectors or positions of targets they just scanned (hence the name Goldfish-M), etc. when following targets and getting the motion vectors correct on the first try without forgetting them.
Sometimes the Goldfish-M scans a target for the first time and detects a motion vector with a speed of around Mach 20 pulling your scan area to the border of the screen forcing you to reset it manually and let it scan again in hopes it gets it right this time. This also happens sometimes if a target gets just updated.
The american radars tend to update targets significantly faster than the CAPTOR-M, in all but the narrow scan, where the CAPTOR-M doesn’t actually really have a narrow scan so much as having quasi-STT mode pretending to be a narrow scan. Couple that with gaijins radar modelling not accounting for acceleration or flight vector at all and you end up with the radar constantly guessing wrong as to where its target is supposed to be.
The slower updates wouldn’t even be a problem if the radar would just get the motion vectors and positions of detected targets right. The american radars (and every other radar I played) don’t have these problems with wrong motion vectors and positions. The Goldfish-M especially likes to jump between positions even if the target was already scanned multiple times. The best parts are the ones where the AIM-120 locks onto the correct target in range kilometers away from where the radar displays them (in narrow scan I might say) and the moment the position gets corrected it gets the motion vector wrong and the target box drifts kilometers away again. Sometimes more than one scan is required to even update the target (notching not being an issue here).
You don’t even need bug reports or specified replays to experience this behavior. You just need to play it in 16v16 on a big map. Then you can experience the reason why this radar is called “Goldfish-M” in all its glory and with all its (nonexistent) might.
There are planned radar fixes and fm buffs?
