too early for cruise missiles
Yeah IIRC the Devs don’t model interleaving.
It has ground target MTI currently. That seems to work for ships if they are moving.
It’s called SRC PD in game.
If you can get some footage of it dropping tracks for no obvious reason then submit a report and hopefully it can be fixed. I’m focussing on reporting issues which can be proved with documentation at the moment, so haven’t had time to play with it and see how it feels in game.
ECR-90 / CAPTOR -M is basically a scaled up and improved Blue Vixen, so unfortunately it makes sense that it is based on Blue Vixen in game.
1 Like
Yep will do.
But you’d hope at the very least they would use that as a hint at the scan rate is much higher than most M-scan radars
I’ll need to double check that, gimme a sec
Yep, it will track moving ships, though I get the impression perhaps it should also track static ships
1 Like
This is just the usual bug/feature in this game with slow update scans. It seems like if you have a slow scan rate and the target you want to update is a bit too far from where the radar expects it to be, it will not update the track, while also not showing that contact as a new track (so you kind of have to wait for it to fade away before the radar notices). Welcome to Soviet top tier radar experience, lol.
Some bug reports on this
Community Bug Reporting System
Community Bug Reporting System
Though never noticed this before when using something like the Gripen or SHar FA2 which have at the moment, essentially the same radar as the Typhoon
It happens sometimes more, sometimes less. Or maybe there is a new bug that makes it even worse on the dev (I have not flown that much this dev, was mainly just testing out the bugs with the IRST).
As I said above, It feels like the intertial tracking isnt working on the Typhoons radar, but its gunna be really hard to test
By this, do you mean that the pipper will randomly go away from the target and reset the scan zone back to center?
Yeah, this:
4 Likes
Had the exact same thing happening with me too, I thought it was the radar, but not really, the f4 ice doesn’t do that, if I’m right, the captor-M is better than the an/apg-65y, so it shouldn’t be like that, hopefully its a bug, i don’t want gaijin ruining such a fancy jet with a absolute garbage of a radar.
Yep, this is the Blue Vixen radar on the FA2
Doesnt even do it slightly. If Typhoon has essentially a Blue Vixen Placeholder then something isnt quite right
9 Likes
Ok, this one seems a bit new (or not, maybe it just feels new because the track is not fading away).
This feels like the time threshold after which the radar stops inertially tracking a target is lowered. So if before you could not see the target and your radar continued tracking based on last know parameters for a certain period, now that period is shorter.
Worth reporting, imo.
Yep, I shall work on a report. But in any case. I do hope the devs have some buffs planned for the radar, even if they just increase blue vixens scan rate by 50% and call it a day. Anything would be nice
Scan rate seems around 60-70 degrees/second, about as much as the F-15. It is just that the scan area is larger, so each scan takes longer.
There is one source which probably isn’t likely good enough to report it, that suggests ECR-90 can do 333° / sec
I might try a mass secondary source report and see what happens
1 Like
Are you sure that number is correct?
Even if it is, are you sure that the number represents scan rate and not just the maximum possible speed for the servo that rotates the dish (it does not matter how quick you can sweep around your radar dish if it does not get enough time to illuminate a target to spot it)?
For example, MiG-29’s radar can move at least up to 70 degrees/second, but the scan mode we have in game is only 50.
It’s this doc
“10° elevation steps in 30 milliseconds” so depending on what it means by that, that translates to 333° per second (if my maths is right)
It might be the max speed and under normal conditions it’s slower, but it’s probably still quicker than what it is now. With it able to basically do A2A and A2G modes at the same time
1 Like
I think I found the problem. The radar only extrapolates (intertially tracks) up to only 4 seconds in TWS.
Here is the TWS block for Captor-M:
Here is the one for N001VEP:
Here is the one for APG-68V7
As you can see, the Captor-M clears the target only after 4 seconds, while the N001 does so after 12, and the APG-68 does so after 8.
The centering of scan zone is normal behaviour for when a track is lost, it is just the track is lost/cleared too quickly.
@Morvran, can you check if it takes 4 seconds for the target to disappear after the radar stops updating it?
I’ll have to check later now, but will see if that is the issue, can you check the source code for blue vixen?