AG radar with wrong target coordinates?

[Orsi]

Hey, I've created a misson to test the new AG radar at the F16, but somethin seens to be wrong.

I'm allways missing the targets.

See attached mission editor target coordinates and AG radar coordinates.

I don't know if AG radar has something worng or I'm doing somethin wrong.

F-16 AG RAdar bombs miss.trk

[pimp]

I was just about to create a post about the AG Radar. I also am having issues hitting targets. I don't know what I'm doing wrong. Can anyone pinpoint(pun intended) why I missed the target in this track attached?

Thanks in advance!

Viper_AG_Radar_Practice_GBUs_Miss.trk

[Frederf]

First track I cannot play because I don't have "Military Aircraft Mod". Mods can have unexpected effects. I can replicate the issue though and it's related to the "snapback" display behavior between DBS frames. Basically if you slew, release so it snapback, and then hit FZ BEFORE the image has a chance to refresh then the radar image under the cursor is meaninglessly shifted from it's actual position. This shouldn't be possible because the snapback behavior is unrealistic.

From 2nd track:

Your L/L readout on release was 37*38.833 115*47.416 (elevation?) and bomb at impact was .837 .419 4807'. So that's 4 thousandths too far north and 3 thousands too far west. That's pretty good.

Edited October 30, 2021 by Frederf

[pimp]

@Frederf How is the GBU that close to the target when you're viewing my track? My original attempt was no where near that close. Also, when I replay the track the GBU misses far from my SPI. See the screenshot below. Something weird is going on. The OP and I can't be the only ones having this issue.

[Frederf]

Could be. Yes I replayed your track twice and it was as shown.

[Orsi]

On 10/30/2021 at 2:54 AM, pimp said:

@Frederf How is the GBU that close to the target when you're viewing my track? My original attempt was no where near that close. Also, when I replay the track the GBU misses far from my SPI. See the screenshot below. Something weird is going on. The OP and I can't be the only ones having this issue.

do you freeze the image to try to lock the target? I think the problem is with the freeze mode. I've flyed again the same mission without using freeze, it`s very harder to lock taget, but seens to hit.

[pimp]

2 minutes ago, Orsi said:

do you freeze the image to try to lock the target? I think the problem is with the freeze mode. I've flyed again the same mission without using freeze, it`s very harder to lock taget, but seens to hit.

Yes I do use freeze mode. I'll try without using it, but as you said it's hard to move the cursor. It's snaps back to the steerpoint automatically and it also moves really slow.

[Orsi]

I've made 2 more tracks, one with freeze and another one without freeze.

 

F-16 AG RAdar whit freeze GBU miss.trk F-16 AG RAdar no freeze GBU hit.trk

[Frederf]

I simply played back the track so there is zero difference in technique between our two experiences. There is an issue where if you move the cursor and then freeze or designate before the radar makes a new image then the image won't be correct to the cursor position. If you slew from point A to point B and then freeze immediately after releasing the cursor switch you will see the imagery of point A under the cursor but the cursor is actually (numerically) over point B.

[Orsi]

4 hours ago, Frederf said:

I simply played back the track so there is zero difference in technique between our two experiences. There is an issue where if you move the cursor and then freeze or designate before the radar makes a new image then the image won't be correct to the cursor position. If you slew from point A to point B and then freeze immediately after releasing the cursor switch you will see the imagery of point A under the cursor but the cursor is actually (numerically) over point B.

but when you freeze and then move the cursor, target coordinates should match.

[Frederf]

Right, the imagery and the numerical grid should always align no matter where in the image updating process. Freeze itself was working fine before the last update as long as the radar did an image refresh since the last slewing. But currently freeze has some other possibly unrelated issue where slewing in freeze displaces the SPI by a factor of 2 compared to the imagery.