Is the HDD size clocked to factor 7?

I was testing the range key on the lower left of the HDD (not HUD), it appears that the range across top to bottom is multiplied by 7 km.

e.g. if the range scale reads 5 then it is 35 km total visible screen top to bottom...

I was testing the range key on the lower left of the HDD (not HUD), it appears that the range across top to bottom is multiplied by 7 km.

 

 

e.g. if the range scale reads 5 then it is 35 km total visible screen top to bottom...

I tend to think of it as: the range from your icon's wings to the top of the display is roughly 70% of the range scale. So 10(0)km=70km. 5(0)=35km, etc. But I reserve the right to be wrong.

I tend to think of it as: the range from your icon's wings to the top of the display is roughly 70% of the range scale. So 10(0)km=70km. 5(0)=35km, etc. But I reserve the right to be wrong.

I wouldnt say wrong. Thing is, the scale is useless when doing direct masurements..

I wouldnt say wrong. Thing is, the scale is useless when doing direct masurements..

I wouldn't say the scale is useless, it's just that the entire HDD display isn't a whole multiple of the range scale, which makes accurate estimations somewhat more complicated. In any case, the HDD is at its most useful when you have AWACS or EWR support, in which case you can always get an accurate BRA from them.

I wouldn't say the scale is useless, it's just that the entire HDD display isn't a whole multiple of the range scale, which makes accurate estimations somewhat more complicated. In any case, the HDD is at its most useful when you have AWACS or EWR support, in which case you can always get an accurate BRA from them.

Which is the way the aircraft was designed to be used...

I wouldnt say wrong. Thing is, the scale is useless when doing direct masurements..

OK. I'll ask the stupid question. In what scenario would you need an exact measurement from the HDD? And you can already get a close estimate of range within a couple of km from HDD.

Which is the way the aircraft was designed to be used...

Absolutely, I agree.

when you're being in BVR-WVR transition, where you're trying to capitalise on the deficient R-27ER by getting the published (user manual) max range on target without having ranging information from AWACS or actually trying to dodge the C/B spamraams by doing a crank/notch, to better your situational awareness. It might seem that I am attacking the product but honestly certain things are not published like this 7 factor gauging, the IRST max detection range, etc..

when you're being in BVR-WVR transition, where you're trying to capitalise on the deficient R-27ER by getting the published (user manual) max range on target without having ranging information from AWACS or actually trying to dodge the C/B spamraams by doing a crank/notch, to better your situational awareness. It might seem that I am attacking the product but honestly certain things are not published like this 7 factor gauging, the IRST max detection range, etc..

:) There is a lot left for the user to discover. When it comes to the HDD, the entire thing is set up only for approximations in the absence of transmitted hard data from either ground or airborne support. The absence of digital data outputs in the HUD/HDD system sort of demands it. Line length, etc. rather than hard numbers. I guess it's never bothered me. Whenever I even glance at the HDD, the word "approximately" is what first comes to mind.

As Weta pointed out, the entire philosophy behind the design of the Su-27 systems was that under most conditions it should be flying with AWACS or EWR support. In this case the primary purpose of the HDD is not to provide accurately measurable data but to provide a 360-degree view of the airspace around you, with emphasis on the front aspect.

This is something that I feel many many Flanker drivers seem to miss: if you have AWACS or EWR support, your situational awareness is better than that available to pilots of all the current Western types available in DCS, precisely due to the fact that you have a display of all surrounding air contacts on your HDD. In reality western aircraft with Link-16 capability would have the same thing, but that isn't implemented in DCS.

For the Flanker pilot with the appropriate AWACS or EWR support, your SA comes from the HDD and SPo-15 RWR and your own radar should be off unless you're attacking a target with SARH missiles.

...

 

This is something that I feel many many Flanker drivers seem to miss: if you have AWACS or EWR support, your situational awareness is better than that available to pilots of all the current Western types available in DCS, precisely due to the fact that you have a display of all surrounding air contacts on your HDD...

I think you're right about many drivers missing the fact that, with datalink support, you can see behind you as well. One thing I always do before taking off online is to set the HDD to max range and get a feel for what's going on in the sky all around me.

 

For the Flanker pilot with the appropriate AWACS or EWR support, your SA comes from the HDD and SPo-15 RWR and your own radar should be off unless you're attacking a target with SARH missiles.

The Flanker is an air superiority fighter not an interceptor, flying without radar seems like a crazy way to achieve that especially as EWR etc. are not all seeing eyes.

I think the main benefit of the Flankers datalink is seeing your own flight and what their radars see, this is the ultimate SA tool for flying as a flight of two or four and that requires radar on.

The Flanker is an air superiority fighter not an interceptor, flying without radar seems like a crazy way to achieve that especially as EWR etc. are not all seeing eyes.

I think the main benefit of the Flankers datalink is seeing your own flight and what their radars see, this is the ultimate SA tool for flying as a flight of two or four and that requires radar on.

In both the air superiority and long-range escort roles it would indeed make complete sense to operate the radar. In the interceptor role Soviet doctrine was absolutely to use GCI control and to use aircraft radar only for final lock-on & missile guidance. PVO got the baseline Su-27 before the VVS got the Su-27S.

Thinking about the data link I was more considering the position of a lone aircraft as opposed to a flight of 2-4. Operating as a team it would make sense for each flight member to operate their radars for maximum coverage, though I can envisage scenarios under which it might be sensible to rely on AWACS or EWR for positioning prior to an engagement with radar silence to maintain the element of surprise.

As far as i'm aware the first production Flankers were the Su27S and Su27P which the PVO intially received 20 followed by deliveries to the VVS air force. Later in 1989 only Su27P (same as 27S but with A2G capability removed) aircraft were built and only delivered to the PVO ADF. Both are referred to as just Su27.

:) There is a lot left for the user to discover. When it comes to the HDD, the entire thing is set up only for approximations in the absence of transmitted hard data from either ground or airborne support. The absence of digital data outputs in the HUD/HDD system sort of demands it. Line length, etc. rather than hard numbers. I guess it's never bothered me. Whenever I even glance at the HDD, the word "approximately" is what first comes to mind.

trust me the worst part is having a bandit on your six with that rear hemisphere undercovered..

Sent from my iPhone using Tapatalk