FCR Ground Radar Refreshrate not realy clear for me to get higher refreshrate

[Steff Bourne]

Hello Guys.

I´ve started playing around with the Ground Radar, but something about the refreshrate isn´t clear for me. I allready watched some tutorials and searched through the internet and now im here.

I started in a F16 at 24.000 feet. Pushed the A-G Button and let the FCR Ground Radar bring up on my left MFD. I have already set a Steerpoint on a specific Airfield and wanted to begin a little reconnaissance. I switch on OSB 2 to Man and scale it down to 10nm. Then i hit OSB 3 to get the DBS 2 program to gain a better/clearer picture. I fly a little offset at about 30-40°. Everything good. So now when i want to get a higher refreshrate, Wags said in his vid, i have to tighten down the Azimuth to 10°, to increase the refreshrate, but when i do that, the refreshrat is by far not so fast as in his vid. It is maximum a 5th of the speed wich you can see in his vid. I´ve no plan what i´m missing. When i´m not in the DBS 2 mode, for example in the Norm mode, the refreshrate is very fast like in his vid, but when i go through the modes and reach DBS 2 the refreshrate slows down with each better program. Finaly DBS 2 is the slowest refreshrate. Can someone explain it to me please?

 

thx in advance

[CoconutCockpit]

I asked the same question here: 

It still feels weird and wrong to me tbh. I don't understand how this is the correct behavior and would still love to hear from someone who knows what the radar actually does in these modes.

I can understand that the radar needs much longer to scan in EXP, DBS1 and DBS2 modes compared to NORM. After all, it's providing a more detailed picture. What doesn't make much sense to me is that scanning a smaller area isn't faster than scanning a larger area. It's basically the same as saying that sprinting 100 meters takes 10 seconds. But sprinting 50 meters also takes 10 seconds; and sprinting 20 meters also takes 10 seconds. 

Edited February 4, 2022 by applepiefrost

[Steff Bourne]

vor 13 Minuten schrieb applepiefrost:

I asked the same question here: 

It still feels weird and wrong to me tbh. I don't understand how this is the correct behavior and would still love to hear from someone who knows what the radar actually does in these modes.

I can understand that the radar needs much longer to scan in EXP, DBS1 and DBS2 modes compared to NORM. After all, it's providing a more detailed picture. What doesn't make much sense to me is that scanning a smaller area isn't faster than scanning a larger area. It's basically the same as saying that sprinting 100 meters takes 10 seconds. But sprinting 50 meters also takes 10 seconds; and sprinting 20 meters also takes 10 seconds. 

 

Maybe that was a bug or a wrong implementation at the beginning as well as when they record that video and now they fixed it. Cause i´m 100% with you, it doesn´t make sense, when i want to produce a much deeper and clearer picture and have the same speed like when i only make a blury picture. So the function now is logic to me, but when i look at Wags video, i get cunfused like you . So then, let´s wait and hope for good answer´s !

[Harker]

The initial implementation was wrong, it works better now. When entering DBS1 and DBS2, the azimuth setting doesn't matter, since the radar is focused on a much smaller area and spends extra computational time in order to create the displayed picture from DBS processing. DBS should be slow for the radar we have.

[Frederf]

Norm and expand are the same. It's just a display change. DBS is variable patch size and slower due to processing. DBS is the smaller of Az setting or patch size which should only matter for A1 and large DBS1 patches.