Jump to content

Recommended Posts

Posted (edited)

The F-15 radar will not slew up/down +/- 60°, like described in the manual, but rather +/- 35°.

 

With the TDC set at 10nm (60761.154856 ft) the top boundary, when slewed up, will only go 40000 feet above you. And the same when slewed down (bottom boundary 40K below).

 

So: 40000/60000 = 2/3, now put that line in a coordinatesystem and you should end up around 35°.

 

In STT it will track a target +/- 60° vertical.

Edited by Svend_Dellepude

[sIGPIC][/sIGPIC]

Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.

Posted (edited)

Radar cone also always covers 16k feet in vertical at 15nm distance regardless of elevation, ie. it gets more narrow at upper and lower elevations.

Edited by Bushmanni

DCS Finland: Suomalainen DCS yhteisö -- Finnish DCS community

--------------------------------------------------

SF Squadron

Posted (edited)

You might be right, but you wouldn't be able to see much of a change at +/- 35° of elevation.

The cone height is according to my calculations about 7-8° high and that seems pretty consistent.

The manual says bar height is 2,5°, and then you would expect some overlap.

Edited by Svend_Dellepude

[sIGPIC][/sIGPIC]

Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.

Posted

When the elevation setting is centered to zero degrees, scan cone is 10 degrees high. I have calculated that the max elevation gives a +-35 degree limit to the cone edge. At max elevation the scan cone is only little over 7 degrees while it should be still 10 degrees. At 15nm this makes 7000 feet difference in covered altitude (16k feet vs 23k feet).

DCS Finland: Suomalainen DCS yhteisö -- Finnish DCS community

--------------------------------------------------

SF Squadron

Posted

oh wow ----- very interesting

 

also, in VACQ, it appears it doesn't scan from 0-deg in front of you (true boresight) and upward 55-deg, it appears from the elev coverage indicators on the left side of the VSD that the lower limit is actually inclined upward somewhat ----- does anybody know about that?

i7-4790K | Asus Sabertooth Z97 MkI | 16Gb DDR3 | EVGA GTX 980 | TM Warthog | MFG Crosswind | Panasonic TC-58AX800U

 

[sIGPIC][/sIGPIC]

Posted (edited)
oh wow ----- very interesting

 

also, in VACQ, it appears it doesn't scan from 0-deg in front of you (true boresight) and upward 55-deg, it appears from the elev coverage indicators on the left side of the VSD that the lower limit is actually inclined upward somewhat ----- does anybody know about that?

 

Numbers are wrong. I tested that too. It will lock on to a target right on your nose, but I'm not sure if it scans the entire 60° up.

 

Something weird happens to the lower boundary when you bank the aircraft too, but the radar seems to do what it's supposed to.

Edited by Svend_Dellepude

[sIGPIC][/sIGPIC]

Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.

Posted

I should add that the narrowing beam at extreme elevations has most relevance on horizontal coverage which gets very narrow even if properly modeled. With this bug it's even more narrow.

DCS Finland: Suomalainen DCS yhteisö -- Finnish DCS community

--------------------------------------------------

SF Squadron

  • Recently Browsing   0 members

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