The RADAR doesn't have to correlate a track, a track is a just a record in your flight computer that has a position or angle.
If there's an angle only track on a line from the plane, the planes computer can extrapolate all points along that LOS and see if any existing tracks match that LOS...
You see something out the window, its not on RADAR
You point ATFLIR at it with a joystick on your controls
It shows up on the screen as a black/white blob as its colder/hotter than it's surroundings
Because it contrasts it's surroundings enough, you can ask the computer in the system to track...
L+S is a designation for "the most important" track, a global track setting it applies to all weapons and sensors. It means Launch and Steer. It means I want to follow this target and I want to potentially launch missiles at it.
All sensors are defaulted to look at L+S for this reason, in...
I think all the other points are equally valid questions. I don't think you or I can get 100% to the bottom of them with the documents and information we have available, like anything else it probably needs some Raytheon engineer to tell us.
But feel free to update that thread.
Yup hence the thread on this that was started to try and address Lehto's statements.
The line inquiry goes like this
TTSA say Go Fast is low to the surface of the ocean.
However the figures on screen (after math) how Go Fast is high, Metabunk calls this out, tracks height and speed of object...
A track file can just be LOS ie an "angle only track", thus range is not required for it to be a track.
https://forums.vrsimulations.com/support/index.php/Air-To-Air_Systems#Angle-Only_Tracks_.28AOT.29
Here's the more detailed thread we had on GO FAST and ranging.
https://www.metabunk.org/threads/atflir-and-range-information-radar-laser-passive-range.11809/
Yes ATFLIR can acquire an angle track, by tracking a contrast area optically, this is known and accepted we see this in Gimbal and Go Fast
However there is a claim (Graves/Alpha Check etc) that the ATFLIR in GIMBAL was SLAVED to a RADAR track of that object.
This is not shown on the overlay...
ATFLIR is mostly a camera, a camera is a passive sensor, cameras do not have hard range limits any limit is entirely based on both strength of the light source and sensitivity of the camera.
RADAR is an active sensor it (in any specific implementation) has a hard limit to how much energy it can...
Do you not read what I say?
If the ATLFIR is slaved then the words L+S or SLAVE are boxed on the overlays as in a little box is shown around the words.
In Gimbal the words L+S and SLAVE are NOT boxed
Thus in the gimbal video the ATFLIR is not SLAVED
At no point in GO FAST or GIMBAL are they...
It's not SLAVED because L+S not SLAVE are not boxed, this setting is clear in all the simulators and manuals we have.
As far as I know it is Lehtos claim about it being passive ranging in GO FAST and as far as I know it has never been backed up by any documentation. He was the first person to...
Despite what Graves says there's no evidence in the video that the gimbal object is on RADAR at all.
If it were I find it odd that they would not SLAVE ATFLIR to it, especially if it were a real situation. If we accept that the GO FAST video is from the same aircraft and flight (based on voices...
Almost all lenses even the high end ones have vignetting to some degree especially wide open, vignette correction is often applied by default by cameras/editing software. So really it would depend on the camera system and settings in use.