Yes, but it cannot continuously track the targets whilst searching the emtire field of search. It can only update the bearing of the targets every few seconds.
Nobody said it could continuously track the entire field of search.
I think you did, bud:
Quote precisely where I said the track was continuous.
No, “Simultaneous” does not count. That means it can simultaneously store the track data of 200 targets. If it were not simultaneous it would be a standard search.
1 Like
That’s not a 6 second update delay. that’s a 6 second delay before being added as a track from initial detection.
8 second latency to update the bearings of targets whilst searching the field of regard. Which is my original point.
2s scan time.
6s declaration, not update.
target should be declared within three detecions.
Thing is detected 3 times, then it is declared as a target.
One scan takes 2s. 3 scans take 6s. Latency of delcaration is 6s.
So where is the problem?
2 Likes
The Rafale thread is picking dust, the Rafale bros MUST come here 😂
2 Likes
Declaration = update. The detections has to undergo a filtering algorithm to make sure it’s not a false positive.
*Bro, there’s only really one lmao
Yes as I said it functions like a TWS radar. Besides like every other IRST it is already implemented the way you describe in game: the game models IRST’s like radars the “beam” passes over the target and it appears as a plot on the c-scope display, that plot is then only updated the next time the “beam” passes over it. So what exactly are you reporting?
That means it takes 2 seconds to complete the entire an entire scan pattern and 6 seconds from first detection to track initialisation. Once a track is initialised it will be updated every 2 seconds (once per scan).
PIRATE initiates a track on the 3rd-4th detection of the target.
6 Likes
Declaration is not update. Declaration is initial addition as a track. The reason it needs three scans is because that’s how TWS works.
Scan 1: detection
Scan 2: velocity confirmation
Scan 3: for safety, I suppose.
Declaration is used here in the definition it would be in e.g programming.
Radars in TWS do the exact same thing as modelled in game right now.
1 Like
You are not wrong, but you are wrong in your thinking.
Declaration is indeed and target update. However the original declaration indeed takes 6s, in order to, as you yourself said, to make sure the target is not a clutter. Once algorythm is sure that the target is there, it is not going to start the whole procedure again, or at least not in the same way. It will display it as a target, and it will keep checking if it is still there, but its not going to wait 6s to put anoter update to the pilot.
If it is already declared as a target, it will continue to update it, while constantly checking data around it. It is not going to keep it in the dark, as it is already declared as a possible target that passed the inital clutter check, so it will be treated as something that can be dangerous.
1 Like
As I said that’s not the case it takes 3-4 scans to initially form the track then the track get’s updated with each subsequent scan.
You can literally see targets getting updated every 1-2 seconds on the IRST output:
4 Likes
They have nothing to complain about the Rafale keeps getting buffed
Man has a hate boner for the EFT.
6 Likes
I mean man, with the amount of times the rafale thread turns into an Euro discussion, it’s only fair this is happening
3 Likes
This is search volume not FOV, the fov you present is broadly accurate based on photo’s of the FLIR. Except the fov is scanned over a wide area, in search or TWS forms. I don’t get what you want here.
3 Likes