Jump to content

Recommended Posts

Posted

And for vertical..

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted (edited)
So if you increase the range scale the contacts will still be packed together just in the middle of the hud instead of the top until you increase the target distance scale to show them as separate contacts?

No. The range scale (on the left) is what determines if the contacts that had been "packed" at the top of the HUD are now displayed within the HUD at the corresponding range. [EDIT] To amplify: If the return is 40 km out and the range scale is set to 25km, the radar return is displayed at the top of the HUD. If the range scale is set to 50 km, instead, the same return appears on the HUD at the 40 km tic mark (on the left side scale) on the HUD. Its right to left orientation depends on its angle off the radar beam's center (not your nose).

 

That last bit is important. It displays in reference to the beam's center, not your nose. That's important to remember when you have the beam slewed to the right or left.[/EDIT]

 

The target distance determines the elevation angle of the radar.

 

 

WildBill,

 

Yes (more or less) on the right/left orientation. The vertical orientation depends on the expected target distance you have set but, in principal, the idea is correct.

Edited by Ironhand

YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg

 

_____

Win 11 Pro x64, Asrock Z790 Steel Legend MoBo, Intel i7-13700K, MSI RKT 4070 Super 12GB, Corsair Dominator DDR5 RAM 32GB.

Posted
No. The range scale (on the left) is what determines if the contacts that had been "packed" at the top of the HUD are now displayed within the HUD at the corresponding range.

 

The target distance determines the elevation angle of the radar

 

That what I thought but what is this TAD karambiatos is talking about?

Posted (edited)
So if you increase the range scale the contacts will still be packed together just in the middle of the hud instead of the top until you increase the target distance scale to show them as separate contacts?

hmmm maybe, i haven't ever thought if its possible to separate them like that.

 

That what I thought but what is this TAD karambiatos is talking about?

 

You change the range scale and the scale (zoom) of the TAD with the same control, I keep forgetting the correct naming conventions of the things on the HUD, sorry

Edited by karambiatos
Posted (edited)
5 was just as an example, i dont ever recall using 5 clicks. What i wanted to know is if there was a better way to scan high targets when flying low. 2 clicks up is apparently not visible on the hud anymore according to the hud view tick marks. I guess more testing in the mission builder is in order.

 

I think you're getting confused, the HUD marks show the visual area by eye not by radar.

 

Edit: sorry ic its already been mentioned, posted after only reading page 1 before catching up with the rest of the thread.

Edited by Frostie

"[51☭] FROSTIE" #55 'Red 5'. Lord Flashheart

51st PVO "Bisons" - 100 KIAP Regiment

Fastest MiG pilot in the world - TCR'10

https://100kiap.org

Posted
I think he means the Head Down Display (HDD), the display which shows datalinks, airbases etc.

 

So if you zoom the HDD in and out it affects the HUD range scale?

Posted
hmmm maybe, i haven't ever thought if its possible to separate them like that.

 

it is not. the bottom of the HUD always represents 0 range. In the TAD, zero range is always at the first division up from the botton, where the marker for your AC is.

Posted (edited)
it is not. the bottom of the HUD always represents 0 range. In the TAD, zero range is always at the first division up from the botton, where the marker for your AC is.

 

There's that abbreviation again.ok I have to ask what does TAD stand for?

 

 

 

And thanks ironhand and everyone who has replied this has been very informative thread for me and maybe will help clarify Some things for others.

Edited by steve65
Posted

Thanks guys, apparently i was mistaken all this time. I even learned something new (about the targets farther then the set range stacking at the top of the hud.) This will surely make me enjoy the Flanker even more!

i5 4590 @ 3.77GHz | GTX 1060 6GB | 16GB 1600MHz DDR3 | 1TB HDD+500GB HDD | Win10 Home X64

[sIGPIC][/sIGPIC]

  • 1 month later...
Posted

Going over the radar mission tutorial - Two questions need to be clarified :

 

* From the discussion here it seems that by default the Su-27 radar is always on full extension/power - it doesn't have the feature/ability like the Eagle to change the range of the radar cone 10-20-40-80-160.

 

Is this how it works with the real Su-27 radar or it's simply how it's modeled in DCS?

 

* Expected target range indication - how do you use it and can it's full feature and advantages be explained?

 

Thanks

[sIGPIC][/sIGPIC]

 

 

Intel i5 4690K | ASUS Z-97PRO Gaming Mobo | Nvidia Gigabyte GTX970 3.5/0.5 GB Windforce3 | G.Skill Ripjaws-X 2x8GB DDR3 1600Mhz | Samsung Evo 120GB SSD | Win10 Pro | Antec 750w 80 Bronze Modular

Posted
Going over the radar mission tutorial - Two questions need to be clarified :

 

* From the discussion here it seems that by default the Su-27 radar is always on full extension/power - it doesn't have the feature/ability like the Eagle to change the range of the radar cone 10-20-40-80-160.

The Eagle radar is the same. Changing the F-15 range setting changes the radar screen, but does nothing to the radar.

 

The Su-27 can also change its screen scale. The two radars are basically the same in this aspect.

 

* Expected target range indication - how do you use it and can it's full feature and advantages be explained?

 

Thanks

Use in combination with GCI/AWACS to point radar at a specific target. This way radar does not need to be on to search, giving itself away.

Awaiting: DCS F-15C

Win 10 i5-9600KF 4.6 GHz 64 GB RAM RTX2080Ti 11GB -- Win 7 64 i5-6600K 3.6 GHz 32 GB RAM GTX970 4GB -- A-10C, F-5E, Su-27, F-15C, F-14B, F-16C missions in User Files

 

Posted
The Eagle radar is the same. Changing the F-15 range setting changes the radar screen, but does nothing to the radar.

 

The Su-27 can also change its screen scale. The two radars are basically the same in this aspect.

 

 

Wow - than it is truly the first time that I understand the meaning of "scaling" the radar - it actually means that I'm scaling the display and not the range that the radar beam is traveling? ? ?

 

 

Use in combination with GCI/AWACS to point radar at a specific target. This way radar does not need to be on to search, giving itself away.

 

MMM....than what do the numbers represent?

 

Thanks

[sIGPIC][/sIGPIC]

 

 

Intel i5 4690K | ASUS Z-97PRO Gaming Mobo | Nvidia Gigabyte GTX970 3.5/0.5 GB Windforce3 | G.Skill Ripjaws-X 2x8GB DDR3 1600Mhz | Samsung Evo 120GB SSD | Win10 Pro | Antec 750w 80 Bronze Modular

Posted (edited)
...

MMM....than what do the numbers represent?

 

Thanks

The Expected Target Range is the range in kilometers to the target. You set it manually, if you have reason to with [RCtrl-+] and [RCtrl--]. The expected relative target altitude is on the right side of the HUD. You tell the radar how far above or below your present altitude at the set Expected Target Range you want the center of radar cone to be focused. This number is also given in kilometers and is changed with the [RShift-;] and [RShift-.] keys.

 

So, if AWACs tells you that the target's range is 50km at an altitude of 10,000 meters and you are flying at 5000 meters, you would set the expected target range at 50 and the expected relative altitude at 5. The would place the center of the beam squarely on the target.

 

As a practical matter in the sim, however, I never touch the expected target range if I am simply scanning on my own. Changing the range doesn't change the beam's shape. So you don't miss anything in that regard.

Edited by Ironhand

YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg

 

_____

Win 11 Pro x64, Asrock Z790 Steel Legend MoBo, Intel i7-13700K, MSI RKT 4070 Super 12GB, Corsair Dominator DDR5 RAM 32GB.

Posted (edited)

Exorcet , Ironhand - Thanks for the info:thumbup:

 

 

new to the Flanker so guys bare with me: did some radar practice locking up different bandits - where can I see the identification of the bandit I locked? Eagle? Viper? Tomcat? how can I know the type of enemy I'm against?

Edited by Mowgli

[sIGPIC][/sIGPIC]

 

 

Intel i5 4690K | ASUS Z-97PRO Gaming Mobo | Nvidia Gigabyte GTX970 3.5/0.5 GB Windforce3 | G.Skill Ripjaws-X 2x8GB DDR3 1600Mhz | Samsung Evo 120GB SSD | Win10 Pro | Antec 750w 80 Bronze Modular

Posted

in the flanker, there is no ID system on the radar.

 

That said, it is possible with experience to estimate the bandit type based on speed, altitude, and flight profiles.

Posted
in the flanker, there is no ID system on the radar.

 

That said, it is possible with experience to estimate the bandit type based on speed, altitude, and flight profiles.

 

well?

[sIGPIC][/sIGPIC]

 

 

Intel i5 4690K | ASUS Z-97PRO Gaming Mobo | Nvidia Gigabyte GTX970 3.5/0.5 GB Windforce3 | G.Skill Ripjaws-X 2x8GB DDR3 1600Mhz | Samsung Evo 120GB SSD | Win10 Pro | Antec 750w 80 Bronze Modular

Posted

The size of the marker on the HUD tells you how big the returning object is - & 'size' impacts detection range too - say if it's coming towards you, High PRF, and you detect it at > 110 km it's probably a bomber, or an F-14.

If you detect it at around 100km maybe an F-15, and at less than 100km - something smaller.

 

If it shows as a jamming strobe - it's 'somthing over there', watch your RWR

Cheers.

Posted (edited)
The size of the marker on the HUD tells you how big the returning object is - & 'size' impacts detection range too - say if it's coming towards you, High PRF, and you detect it at > 110 km it's probably a bomber, or an F-14.

If you detect it at around 100km maybe an F-15, and at less than 100km - something smaller.

 

If it shows as a jamming strobe - it's 'somthing over there', watch your RWR

 

This. Though the Su-27 radar does not offer the same NCTR feature that the F-15 radar does, the distance at which the Flanker radar produces a contact, combined with the contact size information, intelligence on the current situation and likely adversaries will give you the ability to do some amazingly accurate guess work in relation to what your radar contact actually is.

 

Once you've made your educated guess this can be very revealing once your SPO-15 starts beeping at you: the quite detailed information on signal strength it offers, combined with knowledge of the likely type of enemy aircraft will give you a surprisingly accurate picture of the distance to the emitter. I know you'll have this from your radar anyway, but the SPO-15 isn't quite as horrible at providing situational awareness as most would have you believe. Sorry, I've got a bit off-topic here...

Edited by DarkFire

System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit.

 

Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.

Posted (edited)

Thanks for the info - gonna practice tonight with the Flanker's radar and I will see how the new knowledge come's in handy...:joystick:

 

 

* why is it that when I lock a target I get the LA text on the hud but I don't hear the audio repeating "launch authorized"?

Edited by Mowgli

[sIGPIC][/sIGPIC]

 

 

Intel i5 4690K | ASUS Z-97PRO Gaming Mobo | Nvidia Gigabyte GTX970 3.5/0.5 GB Windforce3 | G.Skill Ripjaws-X 2x8GB DDR3 1600Mhz | Samsung Evo 120GB SSD | Win10 Pro | Antec 750w 80 Bronze Modular

Posted
Thanks for the info - gonna practice tonight with the Flanker's radar and I will see how the new knowledge come's in handy...:joystick:

 

 

* why is it that when I lock a target I get the LA text on the hud but I don't hear the audio repeating "launch authorized"?

 

Not sure about the audio tone. Apparently there are a couple of audio cues missing from the current implementation of the Flanker, for example when using the R-73 the missile is supposed to provide an audio tone indicating the quality of the thermal lock in a similar way to the AIM-9 on western aircraft. Possibly the launch cue should also be there...?

System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit.

 

Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.

  • Recently Browsing   0 members

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