Unless none of them were targetting you and you were outside the FoV of the seeker. which to me it looked like you were. Would need to see the clip again in sensor view
I’m gonna be honest if it’s close enough that i cant wriggle the radar on it i can usually see it with the eyes, if it’s above and can’t see it to get the track i continuously elevate and depress the radar and usually it will show up as a single stationary contact(no time for the second pass), and i just insta lock it, then check it on NCTR.
Very rarely will i get a target on radar that’s not already looking at me(or my direction) anyway, so i learned to look for them more efficiently.
Also if you can, play against Full America team in SB, it’s easier because they have a roughly equivalent radar(and all their planes are worse).
with how gaijin models rwr and radars you dont need to actually be target by the missile for it to set your rwr off as just being near it will do it due to side and rear lobes
you can see this in these clips where my rwr briefly goes off due to being close enough to a missile despite not being tracked in either
I’ve had it too many times where I had to go on the full defensive because my radar never found whatever was locking me, no matter what I try. I’ve even had it a few times not find the dot or contrail I can see with my own eyes without taking 5+ seconds of radar beating.
Also, I play the FGR4, so im against Su-30SMs and Rafales most of the time. Im at a total and complete radar disadvantage.
The second clip shows you clearly being targetted by a missile and the first you got a single beep
This is a fairly typical day in the Typhoon
I could not make heads or tails of what was going on to my left when taking off
i was not in a notch and i dropped zero chaff, i find it very unlikely that it would have harmlessly flown past if it was tracking me
and in the second clip yeah it was a single blip, its just an example and in the clip i previously posted there were zero blips
Yeah that is hard, my advice there is to try and play snow maps, it makes it so if a plane has even 200 meters of alt they have a trail, which means you can see them more easily/people don’t go high and reduces the radar disparity.
Guys, guys. I don’t care what your graphs really say. The truth is that pre-patch Typhoon was fun to play, at least in GRB. Now it’s just not. In ARB it’s fine, I guess, problem being that it doesn’t excel in anything but dogfighting performance + current low visibility meta being boring as hell. You can make it work, sure. But they sucked all the fun out of it.
1 Like
That would work, but if the only way to use the Typhoon in SB is to rely upon contrails to find targets instead of using the radar, I might as well just play ARB.
Either way Goldfish-M really needs fixing
Yeah but SB gives that sweet sweet event score.
What’s going on there is that contacts get lost because the radar doesn’t scan fast enough to account for how different the contacts position is+tws can’t really see a target that’s notching so there’s a chance it can’t see some objects and they just get lost, and with the TWS+ shenanigans the contacts update on a full pass, not when the beam goes over the contact.
Eh… Unless its something im actually interested in, I dont really bother, and im still annoyed they nerfed the SB score gains a lot
Yeah, except even when switched the radar into a narrow scan mode and hooked it onto a contact. it couldnt keep the target even half-updated. There is defiently something totally broken with CAPTOR-M
If they added p-track it would fix most issues like that, as the contact would get updated every 2 seconds so it couldn’t get lost as easily (unless they notch).
And it would help a bit with discovering targets because as soon as you’d get a contact you’d get the next pass sooner(2 sec instead of 4), which would reduce the likelihood of losing the contact after first pass.
I think that would fix one major issue.
I still beleive the radar isnt switching between LPRF, MPRF and HPRF properly and so isnt finding contacts when the scan beam passes over it.
It should ideally be the first scan locates the target and the second or third scan updates information like direction of travel and IFF. In my experience, its taken 2 or 3 scans just to get that initial scan contact. At least Ive never had such issues with finding targets in the FA2 with the Blue Vixen.
also notable is the closure speed of the things its tracking,
compared to
This just looks to be fairly standard TWS+ issues that everyone in everything has been reporting since the last major update.
im genuinely struggling to find the issue here, is it that its jumping between targets towards the end? because i have also had things like that happen in the rafale
Sometimes the radar correlates planes to missiles funnily enough, and i think it takes the closure data with it.
It wont find targets properly enough for me to latch the radar onto them, it wont update them fast enough to give a clear picture of whats going on and even when i swtich the radar to a narrow mode it just wont locate the targets within the FoV of the radar properly.
In this situation, if i had tried to join that furball, it would have been pure WVR combat with the no radar
Like in contrast, this was too much effort and micro managing to make it work, but this is what it should be like all the time but with a fraction of the effort
1 Like