Can you show your math here? Snowplow mode (a fixed camera angle) would make the ocean surface move at the same apparent speed as the jet, not useful for searching.
In the 0.7 seconds where the operator is not slewing, you see that the downward angle goes from -22 to -23 degrees, to me this looks like the INR mode (i.e. ATFLIR is pointed at a fixed azimuth and elevation with respect to earth rather than the plane.) and I agree not 'snowplough' mode.
In Go Fast the ATFLIR is in A/A mode which does not do snowplow as far as I can tell. It does
Inertial LOS, this might be the same as Snowplow mode but it's not called that in the manual.
By the way, this is also a confusion between litening and ATFLIR pods on my part. Worth making clear also that inertial LOS and Snowplough are completely different.


Having a play in DCS I can't tell any difference between the snowplough and INR modes and can't get anything that looks like what's in GoFast so I'm going to assume INR isn't modelled, not sure if that is a valid assumption though?
For reference here is a comparison between the slew in DCS and GoFast, note that the water (barely visible but it's there) is travelling much faster in DCS:
Decided to do the maths properly, assuming that the ATFLIR in gofast is looking at a fixed point, modelling 0.7 FOV and the az/el angles in CAD then projecting the length that a point moves in 0.7 seconds to get the speed:
I'm really unhappy with this because it seems far too fast for it to be wind although If GIMBAL is recorded from the same flight then this number isn't completely ridiculous as they quote a wind speed of 120knots to the west and we know that this isn't the jets' speed as it would be much faster (360 knots).
How does moving the ground texture in the simulation 150knots, 170degrees to the right from the initial velocity vector effect the accuracy to the original?