[FIXED] A-G radar SPI placement troubles when in narrow (30 or 60 deg) FOV

[Pack Rat]

I'm narrowing down FOV to reduce radar pass time and trying to target some distinctive landmarks. Fails every time. With full FOV (120 deg) everything works fine. With narrow FOV (30 or 60 deg - no matter) I'm getting this. It has been broken a while ago, but seems to be not reported yet.

Also, cursor sensitivity is suddenly increased when switching to DBS2 mode.

Edited October 10 by uboats

[BigBorner]

Additionally to that, sometimes if you use  A-G Radar with a scan cone lower than 60 Degree, the scan cone will stop following the Radar Cursor. This is in Mapping and GMTI Moder. I have to check for SEA 1&2 

[Pack Rat]

Bump. Still broken in 2.9.

[Napillo]

You would think it would freeze the data where its at as you move the thing around, but instead the whole scan moves as you move the radar scan volume. You should think of it like a 120 degree full image, with only a certain portion that is filled out, and displayed on the screen. Instead, it is a screen, that rotates as you move the scan volume and is correct only when it finishes a scan after you finish moving the scan volume.

[Pack Rat]

@Napillo  In narrow (30 deg) FOV the pass is very fast (less than a second). And still, SPI placement error many times bigger than my plane changes it's position while radar does a single pass. Also, I'm not moving the cursor long enough to let my radar do several passes before putting SPI.

Watch closely at 0:14 - SPI is placed outside the designated cone, too far away to the right. Miles away. There is no way I can drift that far to the left that fast.

[uboats]

I missed this, will check it

@JG54_NF2

Edited October 24, 2023 by uboats

[JG54_NF2]

2023/10/24 AM1点56分，uboats说：

I missed this, will check it

@JG54_NF2

 

[Pack Rat]

This bug is still there. Perhaps it was not addressed yet...

[uboats]

On 2/25/2024 at 2:07 AM, Pack Rat said:

This bug is still there. Perhaps it was not addressed yet...

yup, so far i was focusing other bugs and there was a long holiday break.

will try to fix this in the next 1-2 update

[uboats]

should be fixed in next patch

[Pack Rat]

Not fixed. Checked on recent update (DCS 2.9.9.2280). Problem in question is still there. Behavior changed slightly, but actually became worse. Currently narrowed-down FOV does not always follow lateral cursor movement (even if SPI is not placed), and I cannot figure a pattern yet. And when I place SPI, it is always placed off-target when FOV is 30 or 60 deg.

[uboats]

@JG54_NF2

[JG54_NF2]

2024/10/31 PM4点33分，Pack Rat说：

Not fixed. Checked on recent update (DCS 2.9.9.2280). Problem in question is still there. Behavior changed slightly, but actually became worse. Currently narrowed-down FOV does not always follow lateral cursor movement (even if SPI is not placed), and I cannot figure a pattern yet. And when I place SPI, it is always placed off-target when FOV is 30 or 60 deg.

I need a TRK file to fully restore your operation, I did not reproduce this state on my own computer. 

[supersylph]

On 11/2/2024 at 9:29 PM, JG54_NF2 said:

I need a TRK file to fully restore your operation, I did not reproduce this state on my own computer. 

When the radar angle is 30° and 60°, the scanning range does not follow the cursor movement. And in the current version, my air-to-ground radar cannot manually adjust the pitch angle.In addition, when entering freeze, there is a probability that the image will not be displayed at all.

AGR BUG.trk