Jump to content

Recommended Posts

Posted

When in GM mode in the AG radar and you try to change range the radar always go to NORM mode. Be it either EXP or DBS modes when you change the range it always go back to NORM. It didn't use to do this so i wonder if it's a bug or now works as intended.

And a second question about the azimuth setting when in DBS modes as you lower the setting from 6 to 3 and 1 the sweeping instead of going faster it actually takes longer to do one full sweep. i believe that can't be right either 

Posted

Nothing in the book suggests that changing scale changes FOV option but nothing says it doesn't either. The other sim (tm) also reverts to NORM on manual range scale change. I dunno.

Azimuth settings (A1, A3, A6) are limits to scan azimuth in all scanning modes. DBS has a custom patch size (squares, X miles by X miles) which is automatic and range-dependent. The sweep will be the entire DBS patch or the "A" setting, whichever is smaller. The processing of DBS sweeps should not change with different "A" settings except if the "A" setting limits the sweep width to less than the DBS patch size.

  • Thanks 1
Posted

I noticed this today as well and it seems to be contrary to what wags showed in this video here:

 

The behavior is clearly different and Wags even posted in a Spudknocker video (https://youtu.be/t3uAuYijeug) that when you are in DBS mode, changing the range scale changes the scale of the DBS image, not the scale of the radar scan area. You can also see in both videos how when azimuth scan limits are changed, the picture narrows but is also refreshed faster, which makes logical sense.

This all leads me to believe this behavior is incorrect and is something which was broken in the most recent patch.

 

  • Like 2
Posted

here is something else I noticed while using DBS modes

https://youtu.be/Aq5HXTGUHGI

time stamp 6:28 and you can also see the radar slew is different, in the video it allow you to move the cursor while the image display is constantly updated in the background. The DCS version when moved has to build a whole new image under cursor before displaying the new image location, this causes the screen to go black every time it’s moved.

  • Like 2
Posted (edited)

In DBS1 the patch size is a function of scale. In DBS2 patch size is a function of cursor range. Designating giving a frozen image only remains temporarily (max 10s) entering FTT and its FTT should track things like ships provided the drift detection doesn't return to search.

Edited by Frederf
Posted

So narrowing azimuth doesn’t give a faster scan rate when using DBS? If true when would you use a narrower scan pattern using the GM modes? 
 

Possibly for GMT or SEA modes where you are tracking a moving target?

Posted

You might want to prevent radar energy from exceeding a certain width to avoid being detected by the enemy. Or you simply don't need that width so you can enjoy the faster updates in NORM/EXP. Reduction of azimuth absolutely improves scan rates in NORM/EXP. When actually tracking a target with GMTT or FTT it doesn't matter the "A" setting.

Posted
On 7/27/2022 at 11:23 AM, Frederf said:

In DBS1 the patch size is a function of scale. In DBS2 patch size is a function of cursor range.

 

Then this is also broken in the Viper. Tested today in DBS1 and DBS2 and in both modes, osb 19 and osb 20 only change range, not image scale.

  • 2 weeks later...
Posted (edited)
On 7/29/2022 at 1:31 AM, lethal205 said:

Then this is also broken in the Viper. Tested today in DBS1 and DBS2 and in both modes, osb 19 and osb 20 only change range, not image scale.

This hasn’t  been fixed with the latest patch 2.7.16.28157.

Also noticing when using any of the narrower azimuth settings, when panning the cursor left to right the image under cursor gets dragged around the screen until it refreshes.
 

This is easy to produce, enter GM set azimuth and pan the cursor…

 

 

 

Edited by RuskyV
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...