SU33 bogey not on radar??

[majapahit]

close SU33 bogey not on radar??

 

just started to fly SU33

in missions sensor practice and takeoff and landing

 

I takeoff

put BVR (1) on

radar On (I)

set radar to 8-16km

switch to a weapon (D)

have a bogey right in front of me

 

does NOT show up on my radar screen, neither can I Lock target on it via the HUD recticle

 

I do see bogeys like 16-30km away on the radar!

I can switch to gun and shoot the close bogey

I can switch to Vertical Scan, lock and shoot the close bogey with a missile

 

so what am I missing?

(wrong weapon load?)

(wrong mode?)

 

??

 

thx,mt

[S77th-konkussion]

Probably need to raise or lower your scan cone.

[asparagin]

does NOT show up on my radar screen, neither can I Lock target on it via the HUD recticle

 

I do see bogeys like 16-30km away on the radar!

 

I don't get it, you see something on radar or not?

 

And also, I think it's just a typing mistake, but BVR is "2"?

 

Edit: Ahh.. I think I know.. In the russian planes the radar signals are shown on HUD. I have the impression you were searching targets on your right MFD (were the navpoints are).

Edited April 9, 2010 by asparagin

[Cougar]

Post up a track :)

[majapahit]

I don't get it, you see something on radar or not?

I think I found it, it's the "Expected target range" in the HUD

 

when I have the bogey in front of me, I would make the target range read <10> and start looking for a blimp on the HUD / move the plane inside the HUD

 

which was the minimum readout through the axis binding to "Radar Horitzontal"

or

the key <- - RCtrl> "Radar Scan Zone Decrease" for adjusting to less then 10 by small increments

or

the key <- - RAlt> "Target Specified Size Decrease" to do exactly the same, but in increments of <10>

(hullo?:huh::huh:)

 

but

after testing, a bogey just in front of me (>1km?<) requires a readout of (minimum ~60+) <72> :D

 

picture:

 

also I had to figure out that the "Display Zoom" In/Out buttons do nothing to help the radar, it's - indeed - just the screen map size :cry:

 

leaves this little issue of rather confusing

"Radar Horitzontal"

"Radar Scan Zone Decrease"

"Target Specified Size Decrease"

that do the same thing

(errrr, use the same name?, hint)

and

what's with this readout? :mad: (maintenance needs to calibrate? :))

 

needs a little getting used to compared to the F15, this SU33 is like flying a tank :D

 

anyway, now I can kill the bogey via the target designation cursor (TDC) on the HUD

because I know now to make it show it's radar blimp

 

am I missing something?, mt

Edited April 9, 2010 by majapahit

[Frostie]

I think I found it, it's the "Expected target range" in the HUD

 

when I have the bogey in front of me, I would make the target range read <10> and start looking for a blimp on the HUD / move the plane inside the HUD

 

which was the minimum readout through the axis binding to "Radar Horitzontal"

or

the key <- - RCtrl> "Radar Scan Zone Decrease" for adjusting to less then 10 by small increments

or

the key <- - RAlt> "Target Specified Size Decrease" to do exactly the same, but in increments of <10>

(hullo?:huh::huh:)

 

but

after testing, a bogey just in front of me (>1km?<) requires a readout of (minimum ~60+) <72> :D

 

picture:

 

You have your scan elevation (middle right of HUD) set at -1 (-1000m), so your radar cone will be looking down at 2000m altitude, 10km (tgt range=10) in front of you, by extending the target range and changing it to 72km and still looking at 2000m altitude you have unwittingly lifted you scan cone up to see the bandit.

An elevation of 0 and target range of 10 would have seen this bandit just the same, but you must remember there is a delay before the radar displays the contacts.